Re: /etc/init.d/tog-pegasus restart, now always work.
Ashok K Pathak <[email protected]> Thu, 20 Jun 2013 11:55:29 +0530
| Newsgroups | gmane.network.open-pegasus.general |
|---|---|
| Message-ID | <OF5F73B370.217ECF6F-ON65257B90.0023078A-65257B90.002364AC@in.ibm.com> |
The issue seems to be cropped up if privilege separation for the CIM Server
is enabled (PEGASUS_ENABLE_PRIVILEGE_SEPARATION). To ensure you need to
check whether PEGASUS_ENABLE_PRIVILEGE_SEPARATION is enabled . If the
flag is enabled cimserver process is split into two processes, cimserver
and cimservermain.
>>>>
Starting up CIM server: /usr/sbin/cimserver: cimserver is already running
(the PID found in the file "/var/run/tog-pegasus/cimserver.pid" corresponds
to an existing process named "cimservermain"
<<<<
The above message is logged by pegasus/Executor/main.c which will be
instrumented if privilege separation is enabled.
Regards
Ashok
ff-bahamut
<[email protected]
om> To
[email protected],
06/20/2013 10:36 cc
AM
Subject
/etc/init.d/tog-pegasus restart,
now always work.
Hello All,
I found that "/etc/init.d/tog-Pegasus restart" not always work, here is an
example that it failed to work:
[root@bl460c-g8-8 ~]# /etc/init.d/tog-pegasus restart
Shutting down CIM server: cimserver stop [ OK ]
Starting up CIM server: /usr/sbin/cimserver: cimserver is already running
(the PID found in the file "/var/run/tog-pegasus/cimserver.pid" corresponds
to an existing process named "cimservermain").
cimserver start [FAILED]
I found that if I run "stop" and wait about 3 seconds, the tog-Pegasus will
always be able to start. I also found that if I use "cimserver -s" and
"cimserver" to restart the tog-Pegasus, it will always OK. But it will
spend more time.
Does Anyone have the same experience before? Does it have relationship with
"forceProviderProcesses=true"?
My tog-Pegasus is tog-pegasus-2.12.1-1.x86_64.
Thanks and Regards,
Bai, Bin.