what I'm saying (though not well) is we run this huge nvdbimport and it
seems to cause nvUtil to go out to lunch and never returns. yet it's
not always repeatable for the same files. is there a size limit as to
how big these import files can be?
thanks
________________________________
From: nv-l-bounces AT lists.ca.ibm DOT com
[mailto:nv-l-bounces AT lists.ca.ibm DOT com] On Behalf Of James Shanks
Sent: Tuesday, June 19, 2007 9:39 AM
To: Tivoli NetView Discussions
Subject: RE: [NV-L] nvUtil dying
Perhaps I'm the only one confused by this, but I'm having a hard time
following this thread. We are no longer talking about nvUtil, or are we?
nvdbimport is not nvUtil, though both of them iterate over the object
database, using calls to ovwdb. If he's busy doing one, then he cannot
respond to the other, or probably to anything else. And as your object
db gets bigger it will obviously take longer and longer to examine each
object and determine whether or not to add the fields. And from the size
of your import file, you must be adding a lot.
So what you are saying is that this huge manipulation of the object
database does not finish as quickly as you think it should, and while it
is running "nvUtil -e" doesn't return either. No surprise there given
the task you've given ovwdb to do. Database updates have to be single
threaded.
Realistically, this sounds like a performance issue to me, and you
probably need to find a "quiet" time for your script to run, or perhaps
stop the other daemons and the GUIs so that ovwdb isn't trying to
service the world all at once.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp
"Kain, Becki \(B.\)" <bkain1 AT ford DOT com>
"Kain, Becki \(B.\)" <bkain1 AT ford DOT com>
Sent by: nv-l-bounces AT lists.ca.ibm DOT com
06/19/2007 09:01 AM
Please respond to
Tivoli NetView Discussions <nv-l AT lists.ca.ibm DOT com>
To
"Tivoli NetView Discussions" <nv-l AT lists.ca.ibm DOT com>
cc
"Archer, Walker \(W.A.\)" <warcher1 AT ford DOT 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 AT lists.ca.ibm DOT com [
mailto:nv-l-bounces AT lists.ca.ibm DOT 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 AT lists.ca.ibm DOT 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 AT ford DOT com>
Sent by: nv-l-bounces AT lists.ca.ibm DOT com
06/18/2007 02:17 PM
Please respond to
Tivoli NetView Discussions <nv-l AT lists.ca.ibm DOT com>
To
"Tivoli NetView Discussions" <nv-l AT lists.ca.ibm DOT com>
cc
"Archer, Walker \(W.A.\)" <warcher1 AT ford DOT 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 AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
|
