0
Answered

Ajenti not restarting successfully after restart my ubuntu server?

Ni Lay 6 years ago updated by Eugene Pankov (Project coordinator) 6 years ago 3
Hello,
I'm currently running Ajenti on Amazon Web Services EC2 ubuntu-trusty-14.04-amd64-server.
This was a clean Ajenti install.
After reboot server the ajenti service is down. Here is my ajenti log.

2014-08-13 19:18:56,287 INFO registry.register_crypt_handler(): registered crypt handler 'sha512_crypt': <class 'passlib.handlers.sha2_crypt.sha512_crypt'>
2014-08-13 19:18:56,363 INFO core.run(): Ajenti 1.2.22.6 running on platform: debian
2014-08-13 19:18:56,382 WARNING __init__.load(): *** [openvpn] skipping due to BinaryDependency (openvpn)
2014-08-13 19:18:56,385 WARNING __init__.load(): *** [ntpd] skipping due to BinaryDependency (ntpd)
2014-08-13 19:18:56,402 WARNING __init__.load(): *** [mongo] skipping due to BinaryDependency (mongod)
2014-08-13 19:18:56,405 WARNING __init__.load(): *** [nsd] skipping due to BinaryDependency (nsd)
2014-08-13 19:18:56,409 WARNING __init__.load(): *** [apache] skipping due to BinaryDependency (apache2)
2014-08-13 19:18:56,416 WARNING __init__.load(): *** [megaraid] skipping due to FileDependency (/opt/MegaRAID/MegaCli/MegaCli)
2014-08-13 19:18:56,424 WARNING __init__.load(): *** [fail2ban] skipping due to BinaryDependency (fail2ban-client)
2014-08-13 19:18:56,427 WARNING __init__.load(): *** [dhcpd] skipping due to BinaryDependency (dhcpd)
2014-08-13 19:18:56,430 WARNING __init__.load(): *** [smartctl] skipping due to BinaryDependency (smartctl)
2014-08-13 19:18:56,433 WARNING __init__.load(): *** [memcache] skipping due to BinaryDependency (memcached)
2014-08-13 19:18:56,433 WARNING __init__.load(): *** [elements] Plugin error: format error
2014-08-13 19:18:56,437 WARNING __init__.load(): *** [squid] skipping due to BinaryDependency (squid3)
2014-08-13 19:18:56,447 WARNING __init__.load(): *** [exports] skipping due to BinaryDependency (nfsstat)
2014-08-13 19:18:56,451 WARNING __init__.load(): *** [lm_sensors] skipping due to BinaryDependency (sensors)
2014-08-13 19:18:56,456 WARNING __init__.load(): *** [ctdb] skipping due to BinaryDependency (ctdb)
2014-08-13 19:18:56,461 WARNING __init__.load(): *** [ipmi] skipping due to BinaryDependency (ipmitool)
2014-08-13 19:18:56,464 WARNING __init__.load(): *** [hddtemp] skipping due to BinaryDependency (hddtemp)
2014-08-13 19:18:56,466 WARNING __init__.load(): *** [snmpd] skipping due to BinaryDependency (snmpd)
2014-08-13 19:18:56,478 WARNING __init__.load(): *** [munin] skipping due to BinaryDependency (munin-cron)
2014-08-13 19:18:56,481 WARNING __init__.load(): *** [apcups] skipping due to BinaryDependency (apcaccess)
2014-08-13 19:18:56,491 WARNING __init__.load(): *** [psql] skipping due to BinaryDependency (psql)
2014-08-13 19:18:56,494 WARNING __init__.load(): *** [netatalk] skipping due to BinaryDependency (afpd)
2014-08-13 19:18:56,497 WARNING __init__.load(): *** [samba] skipping due to BinaryDependency (smbd)
2014-08-13 19:18:56,500 WARNING __init__.load(): *** [csf] skipping due to BinaryDependency (csf)
2014-08-13 19:18:56,506 WARNING __init__.load(): *** [bind9] skipping due to BinaryDependency (named)
2014-08-13 19:18:56,516 WARNING __init__.load(): *** [raid] skipping due to BinaryDependency (mdadm)
2014-08-13 19:18:56,939 INFO core.run(): Starting server on (u'554.77.xx.xx', 8000)
2014-08-13 19:18:56,944 ERROR core.run(): Could not bind to (u'54.77.xx.xx', 8000)
2014-08-13 19:18:56,944 ERROR : Could not bind to (u'54.77.xx.xx', 8000)


Answer

Answer
Under review
Looks like another service is taking this port. Check with sudo netstat -tlnp | grep 8000
Answer
Under review
Looks like another service is taking this port. Check with sudo netstat -tlnp | grep 8000
I solved this problem. Ajenti used public ip adress, i changed it to private in /etc/ajenti/config.json 

"host": "172.31.xx.xxx",