Go to Cmd
All Collections
Product Documentation
Known Issues
Upstart — known issue with SSH daemon
Upstart — known issue with SSH daemon
Avoid an issue that can stop triggers from firing as expected on CentOS 6 and Amazon Linux 1
Ben Ironside avatar
Written by Ben Ironside. Updated over a week ago

Description: 

When the Cmd agent is installed on an OS that uses Upstart, restarting the SSH daemon causes the agent to hook it. This results in the incorrect evaluation of triggers that include the CQL property  session_interactive .

 
Workaround

You can avoid this problem by stopping the Cmd agent before restarting the SSH daemon, e.g.:

  1. Stop cmd daemon:
     initctl stop cmd  

  2. Make SSH daemon config changes and restart sshd:
     service sshd restart  

  3. Start cmd daemon:
     initctl start cmd   

If you believe that you are impacted by this issue, please contact Cmd support.

Did this answer your question?