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. Robotic error codes
  4. Robotic error codes
  5. Robot Error status code 2
NetBackup™ Status Codes Reference Guide

Robot Error status code 2

Message: LTI Daemon may not be running

Explanation: On an attempt to start a robotic daemon or process, the attempt to connect to the ltid message queue failed. This error indicates that ltid (the device daemon or NetBackup Device Manager service) may not be running.

Recommended Action:

  • Start ltid so that the shared memory can be initialized, allowing the robotic daemon/process to function.

  • If problems persist, examine the command output, debug logs, and system logs for a more detailed message on the error.

    See "Setting Media Manager debug logging to a higher level" in the NetBackup Logging Reference Guide.

  • On UNIX and Linux servers, gather the output of the ipcs -a command to see the resources that are currently in use.

Feedback

Was this page helpful?
Previous

Robot Error status code 1

Next

Robot Error status code 3

Feedback

Was this page helpful?