To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | Re: [nv-l] nvpagerd dies |
From: | James Shanks <jshanks@us.ibm.com> |
Date: | Tue, 21 Oct 2003 13:08:21 -0400 |
Delivery-date: | Tue, 21 Oct 2003 18:16:42 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l-digest@lists.us.ibm.com |
Look at errpt ( run errpt -a > myfile ) and see what else is happening around that time. There is no error level in nvapgerd. That's an OS level message complaining about the errors. I have only two guesses. Is it possible that you have paging enabled but your modem or tty device is inactive? That's the only "file" (all UNIX I/O is to a "file") that might be an issue here that I can think of. If there is no nvpager.warm file it should work fine, unless perhaps you deleted it while the daemon was active and expecting to write to it. James Shanks Level 3 Support for Tivoli NetView for UNIX and Windows Tivoli Software / IBM Software Group
NetView 7.1.3 AIX 4.3.3 I have had several instances where nvpagerd dies and when I look at the nvpagerd.errlog I see the following message every time: Error(/usr/OV/bin/nvpagerd): Too many consecutive child errors. 10/20/03 16:18:39 - Error(/usr/OV/bin/nvpagerd): select() failed. : A file descriptor does not refer to an open file. I don't see anything in the nvpagerd.alog or nvpagerd.blog that is obviously an issue. Has anyone seen this? Is there a way of bumping up the error level in nvpagerd? Thanks, Scott |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: [nv-l] Rulesets / Alerting, Fernandez, Rick |
---|---|
Next by Date: | RE: [nv-l] Rulesets / Alerting, Brian Kraftchick |
Previous by Thread: | [nv-l] nvpagerd dies, Bursik, Scott {PBSG} |
Next by Thread: | RE: [nv-l] nvpagerd dies, Bursik, Scott {PBSG} |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web