To: | nv-l@lists.tivoli.com |
---|---|
Subject: | Re: [nv-l] nvpagerd - PAGE_Q full error |
From: | James Shanks <jshanks@us.ibm.com> |
Date: | Wed, 17 Sep 2003 10:52:25 -0400 |
Delivered-to: | mailing list nv-l@lists.tivoli.com |
Delivery-date: | Wed, 17 Sep 2003 15:53:28 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
List-help: | <mailto:nv-l-help@lists.tivoli.com> |
List-post: | <mailto:nv-l@lists.tivoli.com> |
List-subscribe: | <mailto:nv-l-subscribe@lists.tivoli.com> |
List-unsubscribe: | <mailto:nv-l-unsubscribe@lists.tivoli.com> |
Mailing-list: | contact nv-l-help@lists.tivoli.com; run by ezmlm |
What operating system and what level of NetView are you using? The page queue is a page of shared memory from the operating system, and whether or not that is expandable depends in large part on the OS. In AIX is expandable, up to the limits that the OS will allow. In Solaris and Linux is it not expandable, but you can configure the initial size in the options for the nvpagerd daemon. I am not certain about the queue in Windows. If you are having a problem in this area, I suggest a call to Support. But a more important question is why you need so many pages. Generally speaking, if the queue is full, it will take a long time, perhaps hours, to deliver all the pages that are already there. Is that really what you want? Perhaps you should take another look at how you are using paging. One suggestion might be that if you have a major outage, you might consider stopping daemon, renaming the warm file, and restarting the daemon with a new file to call only the folks that need to be notified about the major problem. You could switch back to the old warm file later. Not the best solution perhaps but one that bears looking into. Remember that the queue fills up because the daemon cannot dial the calls and place the pages as fast as you can process events to put them on the queue. James Shanks Level 3 Support for Tivoli NetView for UNIX and Windows Tivoli Software / IBM Software Group
All, Whenever we have an outage and some of our devices are unreachable NetView is configured to page us. This works fine for a few devices at a time. But sometimes we can have a several devices drop off the network and this causes a huge surge of alerts to be pushed into nvpagerd's queue. When this happens we se the following error and the nvpagerd daemon freezes and we have to reboot the entire machine. Has anybody ran into this error message? Suppose alot of devices go down and you need this pages. Why is there a non-expandable queue? 09/15/03 19:21:18 Error: PAGE_Q full 09/15/03 19:21:19 PAGE_Q is not expandable on this platform 09/15/03 19:21:19 Error: PAGE_Q full 09/15/03 19:21:19 PAGE_Q is not expandable on this platform 09/15/03 19:21:19 Error: PAGE_Q full Thanks!!! Clarence Hart UPS Office: 410-560-4182 Fax: 410-560-4329 chart@ups.com --------------------------------------------------------------------- To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com For additional commands, e-mail: nv-l-help@lists.tivoli.com *NOTE* This is not an Offical Tivoli Support forum. If you need immediate assistance from Tivoli please call the IBM Tivoli Software Group help line at 1-800-TIVOLI8(848-6548) |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: [nv-l] NetView MIB, Allison, Jason (JALLISON) |
---|---|
Next by Date: | Re: [nv-l] NetView MIB, John Bruer |
Previous by Thread: | Re: [nv-l] nvpagerd - PAGE_Q full error, Clarence Hart |
Next by Thread: | Re: [nv-l] nvpagerd - PAGE_Q full error, James Shanks |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web