A signal 11 is an access violation internal to the program and there is usually
little you can do about it. And it usually produces a core file. So you
should run /usr/OV/service/readcore on yours to produce a core.report and call
Support.
Only they can help you.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
Clarence Hart <clhart@ups.com> on 07/12/2000 01:00:57 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: IBM NetView Discussion <nv-l@tkg.com>, Gareth Holl/Tivoli Systems@Tivoli
Systems
cc: (bcc: James Shanks/Tivoli Systems)
Subject: Re: [NV-L] snmpCollect daemon keeps dying
I have checked all of the areas listed below.
Exit status fron ovstart
object manager name: snmpCollect
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: 13495
last message: Initialization complete.
exit status: exited on signal 11
there is a core file in /usr/OV/PD/cores/snmpCollect
No information was logged about the service stopping in the
/usr/log/snmpCol.trace file. Only startup information.
No entries were made to the nv6000.log either.
No socket file in /usr/OV/sockets
Any ideas?
Clarence Hart
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 6/29/00, 6:48:18 PM, <Gareth_Holl@tivoli.com> wrote regarding Re: [NV-L]
snmpCollect daemon keeps dying:
> What is the "exit status" and "last message" entries for snmpCollect
daemon in
> the ovstatus output ? Are all its dependencies running (nvsecd, trapd,
ovwdb,
> ovtopmd) ? Check for core files in /usr/OV/PD and the root, home
directories.
> Anything in the nv6000.log give you a clue ?
> If snmpCollect is not starting at all, make sure no socket file exist for
> snmpCollect in the /usr/OV/sockets/ directory as this may be preventing
startup
> of that daemon (long shot).
> Sounds like a problem for NetView support to help you with.
> Gareth Holl
> Software Engineer
> Olympics NetView Advocate
> gholl@tivoli.com
> Tivoli Systems / IBM Corporation
> Research Triangle Park, NC 27703. 1-800-TIVOLI-8
> Clarence Hart <rti1clh@ismd.ups.com> on 06/29/2000 05:03:50 PM
> Please respond to IBM NetView Discussion <nv-l@tkg.com>
> To: nv-l@tkg.com
> cc: (bcc: Gareth Holl/Tivoli Systems)
> Subject: [NV-L] snmpCollect daemon keeps dying
> Framework 3.6.1
> NetView 5.1.1
> I had to reinstall both the TME Framework and netview software packages
> and after the reinstall the snmpCollect daemon doesnt want to keep
running.
> I keep getting a box that displays "please run ovstart snmpCollect to
start
> snmpCollect". Before I reinstalled the Netview I saved the migration
info
> so I would keep all of my settings. Has anyone had problems with keeping
> the snmpCollector daemon up and running??
> CoolC
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
I have checked all of the areas listed below.
Exit status fron ovstart
object manager name: snmpCollect
behavior: OVs_WELL_BEHAVED
state: NOT_RUNNING
PID: 13495
last message: Initialization complete.
exit status: exited on signal 11
there is a core file in /usr/OV/PD/cores/snmpCollect
No information was logged about the service stopping in the
/usr/log/snmpCol.trace file. Only startup information.
No entries were made to the nv6000.log either.
No socket file in /usr/OV/sockets
Any ideas?
Clarence Hart
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 6/29/00, 6:48:18 PM, <Gareth_Holl@tivoli.com> wrote regarding Re:
[NV-L] snmpCollect daemon keeps dying:
> What is the "exit status" and "last message" entries for snmpCollect
daemon in
> the ovstatus output ? Are all its dependencies running (nvsecd,
trapd, ovwdb,
> ovtopmd) ? Check for core files in /usr/OV/PD and the root, home
directories.
> Anything in the nv6000.log give you a clue ?
> If snmpCollect is not starting at all, make sure no socket file exist
for
> snmpCollect in the /usr/OV/sockets/ directory as this may be
preventing startup
> of that daemon (long shot).
> Sounds like a problem for NetView support to help you with.
> Gareth Holl
> Software Engineer
> Olympics NetView Advocate
> gholl@tivoli.com
> Tivoli Systems / IBM Corporation
> Research Triangle Park, NC 27703. 1-800-TIVOLI-8
> Clarence Hart <rti1clh@ismd.ups.com> on 06/29/2000 05:03:50 PM
> Please respond to IBM NetView Discussion <nv-l@tkg.com>
> To: nv-l@tkg.com
> cc: (bcc: Gareth Holl/Tivoli Systems)
> Subject: [NV-L] snmpCollect daemon keeps dying
> Framework 3.6.1
> NetView 5.1.1
> I had to reinstall both the TME Framework and netview software
packages
> and after the reinstall the snmpCollect daemon doesnt want to keep
running.
> I keep getting a box that displays "please run ovstart snmpCollect to
start
> snmpCollect". Before I reinstalled the Netview I saved the migration
info
> so I would keep all of my settings. Has anyone had problems with
keeping
> the snmpCollector daemon up and running??
> CoolC
>
_________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
>
_________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
|