Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Status Codes Reference Guide
  3. NetBackup status codes
  4. NetBackup status codes
  5. NetBackup status code: 158
NetBackup™ Status Codes Reference Guide

NetBackup status code: 158

Message: failed accessing daemon lock file

Explanation: The process cannot lock its lock file because an error was received from a system call. This lock file synchronizes process activities (for example, it prevents more than one daemon from running at a time).

Recommended Action: Do the following, as appropriate:

  • Examine the NetBackup error log to determine why the system call failed. Then correct the problem. It may be a permission problem.

  • If the error log does not show the error, create a debug log directory for bprd or bpdbm (depending on which process encountered the error). Increase the unified logging level if nbpem, nbjm, or nbrb encountered the error. Use the vxlogcfg command as explained in the following topic:

    See "About unified logging" in the NetBackup Logging Reference Guide.

    Retry the operation and check the resulting debug log.

Click here to view technical notes and other information on the Cohesity Technical Support website about this status code.

Feedback

Was this page helpful?
Previous

NetBackup status code: 157

Next

NetBackup status code: 159

Feedback

Was this page helpful?