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.
|