|
I had this problem a few times before. Most of the issues comes from deamons still running. Try ovstop then ps -ef | grep -i '/usr/OV/' and kill everything that pops up in there. Then try ovstart again. Its a dirty way of doing it, also rebooting the server fixes the issue too.
On 10/24/05, Ajay Tewari <tewari.ajay@gmail.com> wrote:
Please check you /etc/services file and check some tcp port must be conflicting with other .Have you intall any patch and ML before few day back .if it done by you then ports conflicting must be there Check it carefully /etc/services file line by line basically check your deamon port number either they are conflicting with other services port .
Ajay Tewari
DCM Data System
On 10/22/05, James Shanks <jshanks@us.ibm.com
> wrote:
This is not good and not normal.
"never run" status indicates that the daemon was not started because some
other daemon which it depended on had not initialized. You can tell what
others must be running before each daemon can be started by looking in the
ovsuf file, or the lrf files for each daemon.
This is decidedly not a normal occurrence and you should call support about
it immediately.
It is possible that some daemon is not starting because an old copy of it
never terminated. So ovstop nvsecd and use ps -ef to make sure the only
process from /usr/OV that is running is the one that start with "ntl"
(nettl).
If you insist on troubleshooting it yourself, then print out ovsuf, ovstop
nvsecd, and use "ps -ef | grep OV " to see what is still there. When you
get down to just ntl (nettl) , source the NVenvironment script and try
starting the daemons one at a time, using ovsuf as a guide. Remember that
only the ones which start with zero are active.
You might also review the section in the Diagnosis guide about daemon
problems.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
Mario Behring
<mariobehring@yah
oo.com> To
Sent by:
owner-nv-l@lists. NetView List
us.ibm.com < nv-l@lists.us.ibm.com>
cc
10/21/05 06:04 PM
Please respond to
nv-l Subject
[nv-l] some daemons not running
with a "never run"
Hi list,
My NV server was running normally, the discovery went alright, everything
seemed normal. The netmon daemon stoped for some reason and is not running
anymore.....along with some other daemons. The ovstatus command returns
this:
object manager name: OVsPMD
behavior: OVs_PMD
state: RUNNING
PID: 421902
exit status: -
object manager name: ovwdb
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 282730
last message: Initialization complete.
exit status: -
object manager name: nvsecd
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 274604
last message: Initialization complete.
exit status: -
object manager name: pmd
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 360580
last message: pmd completed initialization
exit status: -
object manager name: OVORS_M
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 303316
last message: orsd completed initialization
exit status: -
object manager name: trapd
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 376852
last message: Initialization complete.
exit status: -
object manager name: ovtopmd
behavior: OVs_WELL_BEHAVED
state: STARTED
PID: 573532
last message:
exit status: -
object manager name: ems_sieve_agent
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
last message:
exit status: -
object manager name: ems_log_agent
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
last message:
exit status: -
object manager name: webserver
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 295124
last message: Initialization complete
exit status: -
object manager name: snmpserver
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 299220
last message: Initialization complete
exit status: -
object manager name: trapgend
behavior: OVs_NON_WELL_BEHAVED
state: RUNNING
PID: 413700
exit status: -
object manager name: mgragentd
behavior: OVs_NON_WELL_BEHAVED
state: RUNNING
PID: 495786
exit status: -
object manager name: ovactiond
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 434388
last message: Initialization complete.
exit status: -
object manager name: nvcorrd
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 278594
last message: Initialization complete
exit status: -
object manager name: nvpagerd
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 466976
last message: PMD initialization complete
exit status: -
object manager name: actionsvr
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 307306
last message: Initialization complete
exit status: -
object manager name: nvserverd
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 200832
last message: Initialization complete.
exit status: -
object manager name: nvcold
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 348264
last message: Initialization complete.
exit status: -
object manager name: snmpCollect
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
last message:
exit status: -
object manager name: servmon
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
last message:
exit status: -
object manager name: nvlockd
behavior: OVs_WELL_BEHAVED
state: RUNNING
PID: 491564
last message: Initialization complete.
exit status: -
object manager name: netmon
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: (never run)
last message:
exit status: -
As you can see, some daemons are running ok and some are not running and
with this "never run" string at the PID field. When I stop everything using
ovstop nvsecd and then try to bring them up again using /etc/netnmrc, the
command never completes and the status is like this one above.
Any help is appreciated.
Thanks.
Mario
Yahoo! FareChase - Search multiple travel sites in one click.
|