[Top] [All Lists]

Re: [nv-l] nvpagerd - PAGE_Q full error

To: "Barr, Scott" <Scott_Barr@csgsystems.com>
Subject: Re: [nv-l] nvpagerd - PAGE_Q full error
From: Clarence Hart <rti1clh@ismd.ups.com>
Date: Wed, 17 Sep 2003 16:48:35 -0400
Cc: nv-l@lists.tivoli.com
Delivered-to: mailing list nv-l@lists.tivoli.com
Delivery-date: Wed, 17 Sep 2003 21:49:47 +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
References: <C04152CE777D294CBC46FD3E24DD329A07C8A66D@omasrv06.csgsystems.com>
User-agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
I'll reconfigure my pager settings and when the hurricane knocks out our power tommorow  I'll let you guys know if the "-q" option worked...  I think my problem is that the daemon wont recover by simply trying to restarting it.  I have to reboot the whole system to get the daemon , the OS, and modem to talk to each other.


Barr, Scott wrote:
Shameless plug.... that was my PMR!
-----Original Message-----
From: James Shanks [mailto:jshanks@us.ibm.com]
Sent: Wednesday, September 17, 2003 2:30 PM
To: nv-l@lists.tivoli.com
Subject: Re: [nv-l] nvpagerd - PAGE_Q full error

You can.  I said so before.  That feature was added as part APAR IY29166 in 7.1.2.
The conclusion of that APAR reads as follows:

The paging queue on Solaris is still fixed, but the default                    
size has been raised to 500 pages.  In addition, a new option,                  
-q <size> , has been added to the nvpagerd daemon                              
on Solaris.  The user can set this value to whatever size is                    
more suitable for him.                                                          
Users who wish to set their own size limit should                              
edit the /usr/OV/lrf/nvpagerd.lrf file and add the -q <size>                    
option there, just as they might add the -d or -w options for                  
debug tracing or using the warm file.  It is then necessary to                  
ovstop nvpagerd, and do first ovdelobj /usr/OV/lrf/nvpagerd.lrf                
and then ovaddobj /usr/OV/lrf/nvpagerd.lrf to change the options                
before starting the daemon again.  A new message has been added                
to the nvpagerd.alog file which documents the queue size in use.                
Note that the use of this new option has not been added to the                  
serversetup dialog at this time.                                                
This fix is first available in NetView for Solaris Version                      

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

Clarence Hart <rti1clh@ismd.ups.com>

09/17/2003 03:08 PM

        To:        "Barr, Scott" <Scott_Barr@csgsystems.com>
        cc:        nv-l@lists.tivoli.com
        Subject:        Re: [nv-l] nvpagerd - PAGE_Q full error

I am using Solaris 8 with NetView 7.1.3.  i do remember seeing another
message that stated a limit of 500.  i wish I could change this.


Barr, Scott wrote:

>You didn't say what version / platform. I don't believe this is a problem on AIX but it is on solaris prior to release 7. In release 7 the queue was expanded (and I think can have size changed). I believe the reason is that on Solaris they use the shared memory feature which architecturally different than AIX. Somebody jump in here if I'm off base. The default size for Solaris is 500 pages I think.
>-----Original Message-----
>From: Clarence Hart [mailto:rti1clh@ismd.ups.com]
>Sent: Wednesday, September 17, 2003 9:37 AM
>To: nv-l@lists.tivoli.com
>Subject: [nv-l] nvpagerd - PAGE_Q full error
>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
>Clarence Hart
>Office: 410-560-4182
>Fax: 410-560-4329
>To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
>For additional commands, e-mail: nv-l-help@lists.tivoli.com
>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)

To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

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>

Archive operated by Skills 1st Ltd

See also: The NetView Web