nv-l
[Top] [All Lists]

RE: [NV-L] nvUtil dying

To: Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
Subject: RE: [NV-L] nvUtil dying
From: Greg Keetch <gkeetch@ca.ibm.com>
Date: Tue, 19 Jun 2007 06:57:36 -0700
Delivery-date: Tue, 19 Jun 2007 15:10:46 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <4B7EE6C5FCFF304D9A1880844C82AE4602151CA6@na1fcm08.dearborn.ford.com>
List-help: <mailto:nv-l-request@lists.ca.ibm.com?subject=help>
List-id: Tivoli NetView Discussions <nv-l.lists.ca.ibm.com>
List-post: <mailto:nv-l@lists.ca.ibm.com>
List-subscribe: <http://lists.ca.ibm.com/mailman/listinfo/nv-l>, <mailto:nv-l-request@lists.ca.ibm.com?subject=subscribe>
List-unsubscribe: <http://lists.ca.ibm.com/mailman/listinfo/nv-l>, <mailto:nv-l-request@lists.ca.ibm.com?subject=unsubscribe>
Reply-to: Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
Sender: nv-l-bounces@lists.ca.ibm.com

Hello,

I have run some very large import files through nvdbimport with no problems. To get a better idea of what is happening with this, you should probably try running the command on it's own with verbose output and without the error output redirection:

> /usr/OV/bin/nvdbimport -fv /opt/Tivoli/custom/scripts/tmp/QClear.import

That might help you see what it's doing, where it might be getting stuck, or possibly other errors.

Incidentally, the only time I've run into problems with the nvUtil command is when the ovwdb cache setting (-n flag) is set to zero (so it can change as needed). Setting a fixed cache size (I usually go with approximately 1.5 times number of objects in database) has always resolved the issue for me... At least so far ;-)

Regards,
Greg Keetch
IT Specialist (Advisor), Network Services
Network Management Tools Specialist
Information Technology Services Americas (ITSA), Global Services, IBM Canada

Inactive hide details for "Kain, Becki \(B.\)" <bkain1@ford.com>"Kain, Becki \(B.\)" <bkain1@ford.com>


          "Kain, Becki \(B.\)" <bkain1@ford.com>
          Sent by: nv-l-bounces@lists.ca.ibm.com

          06/19/2007 06:01 AM
          Please respond to
          Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>


To

"Tivoli NetView Discussions" <nv-l@lists.ca.ibm.com>

cc

"Archer, Walker \(W.A.\)" <warcher1@ford.com>

Subject

RE: [NV-L] nvUtil dying

      This is where it's dying:

/usr/OV/bin/nvdbimport -f /opt/Tivoli/custom/scripts/tmp/QClear.import 2>> /opt/Tivoli/custom/logs/nv/NV_TEC_TICKETS20070619.log
where the file QClear.import is 204262 in size. could that be a limit for nvdbimport? and I'll have to go back through the code and try to figure out why we are making this setting, but could that be the problem? thanks




From: nv-l-bounces@lists.ca.ibm.com [mailto:nv-l-bounces@lists.ca.ibm.com] On Behalf Of Gareth Holl
Sent:
Monday, June 18, 2007 3:14 PM
To:
Tivoli NetView Discussions
Cc:
Tivoli NetView Discussions; Archer, Walker (W.A.); nv-l-bounces@lists.ca.ibm.com
Subject:
Re: [NV-L] nvUtil dying


Bad syntax for the rule might do it. What rule were you using ?

Did nvUtil throw an error when it died ?
Does "die" mean exit or hung (never returns bad to the command prompt) ?

Of the bunch of nvUtils your script runs, how many of them does your script complete before the problem occurs ... can you pinpoint the problematic nvUtil call within your script and provide some details of its syntax (rule etc) ?

When you attempt the "nvUtil L" after your script completes, I'm assuming one of the nvUtil's from your script has already hosed things. Can you check to see if any nvUtils are still left running (ps -ef |grep nvUtil), kill them, then retry your "nvUtil L" test to see if that is all that is needed to resume normal operation (instead of restarting the daemons). If not, just recycle nvcold daemon and see if that frees things up.


Gareth


"Kain, Becki \(B.\)" <bkain1@ford.com>
Sent by: nv-l-bounces@lists.ca.ibm.com

06/18/2007 02:17 PM

Please respond to
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>

To
"Tivoli NetView Discussions" <nv-l@lists.ca.ibm.com>
cc
"Archer, Walker \(W.A.\)" <warcher1@ford.com>
Subject
[NV-L] nvUtil dying




What would cause nvUtil to die when all the daemons are up, based on ovstatus? Is there a limit to how big a list can be , that is returned by nvUtil e? I'm trying to debug this issue, and a bunch of nvUtil e's are issued for this script, and for unknown reasons, after this script runs, nvUtil L never returns and I have to stop all the daemons and restart them. The code has not changed, at all, on the Netview servers, but I was thinking that the output of the nvUtil was too big and hitting some limit

Thanks in advance _______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)

GIF image

_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to 
internal IBM'ers only)
<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web