Forum Discussion

cmhnz's avatar
cmhnz
Level 3
17 years ago
Solved

NetBackup Service Layer service failed to start

Hi,

 

We have a problem in that the NetBackup Service Layer service won't start with the following errors in Event Viewer:

 

Event Type:    Error
Event Source:    Service Control Manager
Event Category:    None
Event ID:    7009
Description:
Timeout (30000 milliseconds) waiting for the NetBackup Service Layer service to connect.

 

Event Type:    Error
Event Source:    Service Control Manager
Event Category:    None
Event ID:    7000
Description:
The NetBackup Service Layer service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

 

We've done the basic troubleshooting; rebooted the server, brought services down and back up using bpdown / bpup command.  We've stopped services, restarted VERITAS Private Branch Exchange service, started services but all yield the same result.

 

We've added the following registry entry to increase the timeout:

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServicePipeTimeout = 90

 

Although we're unsure whether this has taken effect because the error reported states that this is still 30 seconds, rather than 90 like we've set.

 

I was not here when the issue occurred, but reports from colleagues state that an erase tape (multiple erase jobs running) was being performed and someone ran the inventory robot at the same time and the jobs hung.  The decision was made to restart the server to try and correct, but since then, the only service which fails to restart is the NetBackup Service Layer.

 

Running NetBackup 6.0, and I believe without any MP's installed.  Nothing mentioned as being installed under Help -> About (I inherited looking after this system...).

 

Can anyone assist?

 

Thanks in advance.

 

Chris

  • Issue resolved after installing the latest maintenance pack (MP7).
  • Perhaps the best starting point would be to apply MP5. The 6.0 GA release was notorious for having many many issues in various places. This could well be a side effect from one of these. If once you've done that, you get the same message and have checked your license keys are all valid, then we could go further and start a debuging procedure (ie increase log verbosities and see what logs you get ...)
  • Thanks for the reply Dami.

     

    I'll probably look at doing this on Thursday (first day I'll get a chance) in the hope it fixes the problem.  We were hopeful someone had encountered this and could provide a fix, then we would install MP5 at our leisure.

     

    I'll post results once I've installed MP5.

     

    Cheers

  • Issue resolved after installing the latest maintenance pack (MP7).