I've seen this error when I've run out of swap space...are you possibly
low on memory?
-Rich
-----Original Message-----
From: Michael Engel [SMTP:engel@NMS1.CC.HUJI.AC.IL]
Sent: Sunday, November 15, 1998 8:03 AM
To: NV-L@UCSBVM.UCSB.EDU
Subject: trouble shooting - ovstart not working
To whom it may concern:
I was trying to run nv6000, requested to use "ovstart" but I
receive
the following error. Please consult.
Thanks,
michael (engel@cc.huji.ac.il)
object manager name: nvsecd
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: 22522
last message: Received signal 33, exiting
exit status: exit(1)
object manager name: trapd
behavior: OVs_WELL_BEHAVED
state: DONE
PID: 19458
last message: killing trapd on signal 33
exit status: -
object manager name: ovactiond
behavior: OVs_WELL_BEHAVED
state: DONE
PID: 22538
last message: ovactiond lost contact with trapd.
exit status: -
object manager name: ovwdb
behavior: OVs_WELL_BEHAVED
state: FAILED
PID: 23812
last message: Received signal 33, exiting
exit status: -
object manager name: ovtopmd
behavior: OVs_WELL_BEHAVED
state: UNSTARTABLE
PID: -
last message: Received signal 33, exiting
exit status: -
object manager name: ems_sieve_agent
behavior: OVs_WELL_BEHAVED
state: UNSTARTABLE
PID: (never run)
last message:
exit status: -
object manager name: ems_log_agent
behavior: OVs_WELL_BEHAVED
state: UNSTARTABLE
PID: (never run)
last message:
exit status: -
object manager name: nvcold
behavior: OVs_WELL_BEHAVED
state: UNSTARTABLE
PID: 12620
last message: Received signal 33, exiting
exit status: -
object manager name: snmpCollect
behavior: OVs_WELL_BEHAVED
state: UNSTARTABLE
PID: (never run)
last message:
exit status: -
object manager name: netmon
behavior: OVs_WELL_BEHAVED
state: UNSTARTABLE
PID: (never run)
last message:
exit status: -
|