When I login to the live console of my server and go to the console, I am getting the below message
This message is coming over and over again in the Console logs.
And in the system Events I have got this entry coming frequently.
Hello.
System is a HP Visualize C3600 running X11 and after a power failure machine will not boot (see error messages below)
From what I've read, this may be caused by a corrupted etc/inittab file. Solution suggested on other websites is to boot in single user mode and edit file inittab... (2 Replies)
Hi all
I used a dual boot operating system and it works fine for me. Now , i install a Ati radeon 9250 Agp card on my system and this results in boot failure of fedora 6. The graphics card is working fine with windows XP , i.e i have no compatibility issues.The system also refuses to boot when i... (2 Replies)
I installed solaris virtually and tried to format the partitions .. I dont know what went wrong, It got rebooted and hangs in the screen "No partitions" and after pressing Enter button it goes to "INT18 boot failure" and hangs there once again . Could any one of you suggest why this has happened... (3 Replies)
I have installed Solaris 10 OS in Sun Virtual Box that uses x86 32 bit system. After an abnormal shutdown i'm getting the following message on the console when i try to boot.
SunOS Release 5.10 Version Generic_127128_11 32-bit
Copyright 1983-200 Sun Microsystems, Inc. All rights reserrved.
Use... (3 Replies)
hi
SCO Unix 5.0.6 doesn't boot due to this problem:
not a directory
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot
Knows someone howto solve it? (16 Replies)
I'm trying to run clusterKnoppix live cd from a couple machines but it only works from one computer. The other three, my toshiba laptop, emachine, and hp machine can't find the filesystem.. the live cd stops booting and gives me a error saying it couldn't find knoppix filesystem and then gives me a... (0 Replies)
HPUX running in D-Class (L1000), pretty old HPUX version - hpux 11.00
Attempt 1 -- To boot from normal (primary)
Unable to boot - system complains failure
SYSTEM ALERT System Name : uninitialized DATE : 10/22/2011 Time : 03/41:12 Alert Level 15 = Fatal hardware or configuration... (12 Replies)
Hi Guys,
I have a small problem with a v445 which I have been informed will only boot with the reconfigure option enabled.
It is attached to HP SAN storage using qla2300 FCA's with a Veritas encapsulated rootvoldg (No Laughing here please) when I try a reboot I get the following error.
... (5 Replies)
hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
LEARN ABOUT SUNOS
init.wbem
init.wbem(1M) System Administration Commands init.wbem(1M)NAME
init.wbem - start and stop the CIM Boot Manager
SYNOPSIS
/etc/init.d/init.wbem start | stop | status
DESCRIPTION
The init.wbem utility is run automatically during installation and each time the system is rebooted. This utility manipulates the CIM
Object Manager (CIMOM) and the Solaris Management Console server, both of which run combined in a single process. init.wbem can be used to
start, stop, or retrieve status from the server.
CIM Object Manager
The CIM Object Manager manages CIM objects on a WBEM-enabled system. A CIM object is a computer representation, or model, of a managed
resource, such as a printer, disk drive, or CPU. CIM objects are stored internally as Java classes.
When a WBEM client application accesses information about a CIM object, the CIM Object Manager contacts either the appropriate provider for
that object or the CIM Object Manager Repository. Providers are classes that communicate with managed objects to access data.
When a WBEM client application requests data from a managed resource that is not available from the CIM Object Manager Repository, the CIM
Object Manager forwards the request to the provider for that managed resource. The provider dynamically retrieves the information.
At startup, the CIM Object Manager performs the following functions:
o Listens for RMI connections on RMI port 5987 and for XML/HTTP connections on HTTP port 5988.
o Sets up a connection to the CIM Object Manager Repository.
o Waits for incoming requests.
During normal operations, the CIM Object Manager performs the following functions:
o Performs security checks to authenticate user login and authorization to access namespaces.
o Performs syntactical and semantic checking of CIM data operations to ensure that they comply with the latest CIM Specification.
o Routes requests to the appropriate provider or to the CIM Object Manager Repository.
o Delivers data from providers and from the CIM Object Manager Repository to WBEM client applications.
A WBEM client application contacts the CIM Object Manager to establish a connection when it needs to perform WBEM operations, such as cre-
ating a CIM class or updating a CIM instance. When a WBEM client application connects to a CIM Object Manager, it gets a reference to the
CIM Object Manager, which it then uses to request services and operations.
Solaris Management Console Server
The Solaris Management Console server is the back end to the front end console, smc(1M). It provides tools for the console to download and
performs common services for the console and its tools to use, such as authentication, authorization, logging, messaging, and persistence.
System Booting
The init.wbem script is installed in the /etc/init.d directory.
OPTIONS
The following options are supported:
start Starts the CIMOM and Solaris Management Console server on the local host.
stop Stops the CIMOM and Solaris Management Console server on the local host.
status Gets the status of the CIMOM and Solaris Management Console server on the local host.
NOTES
When the init.wbem script is run, it does not run the CIMOM and Solaris Management Console server directly. The server process is in Java
and is too heavyweight to be run immediately at system boot time. Instead, three lightweight processes listen on three different ports that
the CIMOM and the Solaris Management Console server normally use. This acts similarly to inetd(1M).
Because Java programs cannot inherit file descriptors as other programs can, there is a small time period from when the first connection is
made until the server is fully operational where client connections may be dropped. WBEM clients are immune to this, as they will retry
until the server comes online. Solaris Management Console clients are not immune, and it may be necessary to manually reconnect, though
this should not happen in the common case.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWwbcor |
+-----------------------------+-----------------------------+
SEE ALSO inetd(1M), mofcomp(1M), smc(1M), smcconf(1M), wbemadmin(1M), wbemlogviewer(1M), attributes(5)SunOS 5.10 2 Jan 2002 init.wbem(1M)