STATUS CODE: A Status 134 "unable to process request because the server resources are busy" error occurs and jobs requeue. The client's bpbkar process unexpectedly runs up to hundreds of times within an hour.

Problem

STATUS CODE: A Status 134 "unable to process request because the server resources are busy" error occurs and jobs requeue. The client's bpbkar process unexpectedly runs up to hundreds of times within an hour.

Error Message

Re-queueing job due to busy resources (134)

unable to process request because the server resources are busy (134)

Solution

Overview:
A Status 134 "unable to process request because the server resources are busy" error occurs and jobs requeue. The client's bpbkar process unexpectedly runs up to hundreds of times within an hour.

Troubleshooting:  
This issue has been encountered in environments where multiple, redundant Storage Units have existed for the same media server. When this issue is encountered, the log activity below will loop continuously.

Master Log Files:
Activity Monitor "detailed status" of the job:
10.2.2004 18:07:17 - connecting
10.2.2004 18:07:17 - connected
10.2.2004 18:07:23 - mounting UZ180S
10.2.2004 18:12:14 - end writing
unable to process request because the server resources are busy(134)


Media Server Log Files:
BPTM
2/10/2005 9:46:48 AM - started process bpbrm (3496)
2/10/2005 9:46:48 AM - connecting
2/10/2005 9:47:01 AM - connected; connect time: 00:00:13
2/10/2005 9:47:03 AM - started process bptm (4352)
2/10/2005 9:47:03 AM - started process bptm (4356)
2/10/2005 9:47:03 AM - mounting UZ180S
2/10/2005 9:47:06 AM - end writing
2/10/2005 9:47:06 AM - Info bpsched(pid=4176) Re-queueing job due to busy resources (134)
2/10/2005 9:47:08 AM - started process bptm (3080)
2/10/2005 9:47:08 AM - started process bpbrm (3492)
2/10/2005 9:47:08 AM - connecting
2/10/2005 9:47:08 AM - connected; connect time: 00:00:00
2/10/2005 9:47:09 AM - started process bptm (4264)
2/10/2005 9:47:09 AM - mounting UZ180S
2/10/2005 9:47:09 AM - end writing


Client Log Files:  N/A

Resolution:
1.  Within the NetBackup (tm) Administration Console, expand NetBackup Management in the left pane and click Storage Units  
2.  Observe all Storage Unit configurations and verify that there are no duplicate or unused Storage Units  
3.  Remove all unnecessary Storage Units
4.  When possible, cycle NetBackup Services/Daemons on the master server

If the excessive bpbkar processes do not automatically terminate on the client(s) affected, it may be necessary to reboot that client or clear the bpbkar processes manually in order to regain proper functionality.


Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)