Yesterday I had to change my Haproxy configuration and I noticed I couldn't restart it with systemctl. I had to launch it by hand.
Today I had to restart Docker and the same thing happened.
journalctl -xe after a
systemctl restart haproxy:
-- Unit haproxy.service has begun starting up. Aug 06 11:19:30 ns3038251 systemd: haproxy.service: Control process exited, code=dumped status=7 Aug 06 11:19:30 ns3038251 systemd: haproxy.service: Failed with result 'core-dump'. Aug 06 11:19:30 ns3038251 systemd: Failed to start HAProxy Load Balancer. -- Subject: Unit haproxy.service has failed
And for Docker:
-- The start-up result is RESULT. Aug 06 11:19:08 ns3038251 systemd: containerd.service: Main process exited, code=dumped, status=7/BUS Aug 06 11:19:08 ns3038251 systemd: containerd.service: Failed with result 'core-dump'.
I know this is not a config file issue because both
containerd (and then
dockerd) works when I run them in the console.
The problem is that internet doesn't give much information and I don't know what I can try to debug, this is on a distant server and I don't want to reboot in case it can't boot at all when started. By the way I didn't do anything recently, like updating
Thanks for any advice you can give me
I have been busy since posting the question, I logged back to the server minutes ago. I didn't do anything since and I returned to the same
And now there is no problem
systemctl restart haproxy or
systemctl restart docker. I don't get what have happened here...