[Kolab-devel] Manticore start at reboot

[Jochen Hein]

I've just rebooted my CentOS-VM and manticore did not start:

Feb  2 21:47:33 kolab-35 systemd: Starting manticore.service...
Feb  2 21:47:33 kolab-35 ntpd[999]: 0.0.0.0 c615 05 clock_sync
Feb  2 21:47:33 kolab-35 NetworkManager[561]: <info>  Policy set 'eth0' (eth0) as default for IPv6 routing and DNS.
Feb  2 21:47:34 kolab-35 manticore: Express server listening on 8080, in production mode
Feb  2 21:47:34 kolab-35 manticore: /usr/share/manticore/node_modules/mongoose/node_modules/mongodb/lib/server.js:235
Feb  2 21:47:34 kolab-35 manticore: process.nextTick(function() { throw err; })
Feb  2 21:47:34 kolab-35 manticore: ^
Feb  2 21:47:34 kolab-35 manticore: Error: connect ECONNREFUSED
Feb  2 21:47:34 kolab-35 manticore: at exports._errnoException (util.js:746:11)
Feb  2 21:47:34 kolab-35 manticore: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1012:19)
Feb  2 21:47:34 kolab-35 systemd: manticore.service: main process exited, code=exited, status=1/FAILURE
Feb  2 21:47:34 kolab-35 systemd: Unit manticore.service entered failed state.
Feb  2 21:47:34 kolab-35 systemd: manticore.service failed.
Feb  2 21:47:34 kolab-35 systemd: manticore.service holdoff time over, scheduling restart.

It seems that manticore is started before some other service is ready.
What service is that?  We should probably add a dependency to the unit file...

Jochen

-- 
The only problem with troubleshooting is that the trouble shoots back.