Veritas NetBackup™ Status Codes Reference Guide
- NetBackup status codes
- NetBackup status codes
- NetBackup KMS status codes
- NetBackup status codes
- Media Manager status codes
- Media Manager status codes
- Media Manager status codes
- Device configuration status codes
- Device configuration status codes
- Device configuration status codes
- Device management status codes
- Device management status codes
- Device management status codes
- Robotic status codes
- Robotic status codes
- Robotic status codes
- Robotic error codes
- Robotic error codes
- Robotic error codes
- Security services status codes
- Security services status codes
- Security services status codes
- NetBackup alert notification status codes
NetBackup status code: 509
Explanation: The NetBackup Java authentication or user service reported an error that relates to the creation (or demise) of a child job process. The NetBackup Java service programs create separate jobs to accomplish specific tasks, as follows. The NetBackup Java authentication service creates the NetBackup Java user service. When it is created and connected to, the NetBackup Java user service creates all other child processes on behalf of requests from the NetBackup Java interface.
The cause of status code 509 can be found in the appropriate log file, either for bpjava-msvc, bpjava-susvc, or bpjava-usvc.
The cause can be categorized as one of the following:
A job (started by either the NetBackup Java authentication service or user service) no longer exists and did not report its result status.
The NetBackup Java service cannot monitor a job (started by either the NetBackup Java authentication service or user service). The reason it cannot monitor is probably due to a lack of system resources (insufficient memory).
The maximum number of non-transient Activity Monitor jobs (>100) has already been started.
Recommended Action: Do the following, as appropriate:
If the problem persists, restart the NetBackup Java interface and try again.
If the problem still persists, enable detailed debug logging as explained in the following topic:
See "Setting debug logging to a higher level" in the NetBackup Logging Reference Guide.
Restart the NetBackup Java interface and examine the logs.
The error is probably the result of a system resource issue. When detailed debug logging is enabled, you can retrieve the details from the bpjava-msvc, bpjava-susvc, or bpjava-usvc log files.
Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.