Mongo Automation agent error

706 views
Skip to first unread message

KASHINATH VISHWAKARMA

unread,
Apr 18, 2017, 7:45:18 PM4/18/17
to mongodb-user

while starting the automation agent , we are getting below error.
Please can you suggest the root cause 


OS -CentOS Linux release 7.1.1503 (Core)
OPs Manager version: 3.4.3.402 
 

Error details:

sudo systemctl -l status  mongodb-mms-automation-agent.service
mongodb-mms-automation-agent.service - MongoDB MMS Automation Agent
   Loaded: loaded (/etc/systemd/system/mongodb-mms-automation-agent.service; disabled)
   Active: failed (Result: exit-code) since Tue 2017-04-18 17:46:13 IST; 11min ago
  Process: 1125 ExecStart=/opt/mongodb-mms-automation/bin/mongodb-mms-automation-agent -f /etc/mongodb-mms/automation-agent.config -pidfilepath /var/run/mongodb-mms-automation/mongodb-mms-automation-agent.pid >> /var/log/mongodb-mms-automation/automation-agent-fatal.log 2>&1 (code=exited, status=8)
 Main PID: 1125 (code=exited, status=8)

Apr 18 17:46:13 imslab01.mwdbcoe.net systemd[1]: [/etc/systemd/system/mongodb-mms-automation-agent.service:13] Unknown lvalue 'RuntimeDirectory' in section 'Service'
Apr 18 17:46:13 imslab01.mwdbcoe.net systemd[1]: [/etc/systemd/system/mongodb-mms-automation-agent.service:14] Unknown lvalue 'RuntimeDirectoryMode' in section 'Service'
Apr 18 17:46:13 imslab01.mwdbcoe.net systemd[1]: Starting MongoDB MMS Automation Agent...
Apr 18 17:46:13 imslab01.mwdbcoe.net systemd[1]: Started MongoDB MMS Automation Agent.
Apr 18 17:46:13 imslab01.mwdbcoe.net mongodb-mms-automation-agent[1125]: [2017/04/18 17:46:13.931] [.info] [cm/util/sysdep_unix.go:LockAutomationLockFile:170] [17:46:13.931] Locking automation lock file at /tmp/mongodb-mms-automation.lock
Apr 18 17:46:13 imslab01.mwdbcoe.net systemd[1]: mongodb-mms-automation-agent.service: main process exited, code=exited, status=8/n/a
Apr 18 17:46:13 imslab01.mwdbcoe.net systemd[1]: Unit mongodb-mms-automation-agent.service entered failed state. 
sudo systemctl -l status  mongodb-mms-automation-agent.se...

Kevin Adistambha

unread,
Apr 26, 2017, 1:07:43 AM4/26/17
to mongodb-user

Hi Kashinath,

It looks like the automation agent failed to start. However, there is insufficient information in your post to point out the exact reason why it failed to start.

Please note that Ops Manager and the automation agent is part of MongoDB Enterprise Advanced edition which is a commercially supported product. If your organisation/company already has a commercial subscription I would suggest to open a case in the Commercial Support Portal. They would be able to provide you with the support required to troubleshoot your Ops Manager deployment.

Alternatively if you are evaluating MongoDB Enterprise and interested, please send me a private message with your contact details and I can request a MongoDB Account Executive to contact you.

Best regards,
Kevin

Reply all
Reply to author
Forward
0 new messages