This post is more than 5 years old
15 Posts
0
1490
Any solution for this error?
Host Name,Level,Location,Function,Message,Timestamp
server,Error,clctr.mod.nbu.job,nbuGetFilteredBpdbJobs,timeout querying server 'suusag21',3/18/11 23:39
server,Warn,fwk.base.sysutils,csystemreadline,timeout while waiting for child process,3/19/11 00:10
server,Error,clctr.mod.nbu.job,nbuGetFilteredBpdbJobs,timeout querying server 'suusag21',3/19/11 00:10
doster1
31 Posts
0
March 24th, 2011 10:00
Hi Haffiz,
There is option for many of the Requests to set timeout parameters.
First it needs to be determined what command from what request is timing out. Then, best is test that command to see how long it takes. Of course this should be done around the same time period it runs as the business of the Backup server can affect the command but overall you can double and then triple, etc the command to allow it to finish. Note if the you set a high timeout period which maybe needed the next request for the same data will wait till the first request finishes or times out.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 23rd, 2011 01:00
Good Day Haffiz,
The error you provided can be due to numerous reasons, but the most common are
1) No reponse from server (resolution issue)
2) The command run against the server did not complete within a certain time limit.
For #2, I would suggest running the following command on the collector host:
bpdbjobs -report -all_columns
If the collector is not on 'suusag21' then run the following:
bpdbjobs -M suusag21 -report -all_columns
After you run the command, see if it takes more than 5 minutes for the output to complete. If it does take longer than 5 minutes, you should change the default 'Frequency' for the 'Netbackup Job Monitor' request from 5 minutes to a higher value OR you can try to reduce the output from the bpdbjobs by adjusting your activity monitor within NBU so that the output completes within the 5 minute window. If none of these suggestions resolves the issue, I would recommened you open up a SR and attach a Collector Log in DEBUG LOW (logging for about 5 minutes) so that we can investigate further.
Regards,
Sang Pak
EMC Technical Support
Haffiz
15 Posts
0
March 23rd, 2011 08:00
trying to run backfillbut colletor.log not created.
already done this step but no success.
1) Stop the collector service:
opt/dpa/etc/dpa stop
2) Rename /var/tmp/dpa_collector.pfile and /var/tmp/dpa_collector_repq.pfile to .old
3) Start the collector:
opt/dpa/etc//dpa start