By default, systemd services will log their output to /var/log/messages, and you can view these messages with journalctl commands.
To tail the logs for a specific service you are running, you can simply do the following.
journalctl -u service-name -f
Just remove the -f if you want to view the log in general.
You can also just lazily use -f without the -u and service name if you want to tail recent system logs, which is often useful.
This has bitten me badly twice now. I was deploying Centos 7.5 servers and trying to run HA Proxy on them through SystemD (I’m not sure if it is an issue otherwise).
Basically, no matter what port I use I get this message:
Starting frontend main: cannot bind socket [0.0.0.0:80]
Note that as I was too lazy to set up separate logging for the HAProxy config, I found this message in /var/log/messages with the other system messages.
Of course, seeing this your first thought is “he’s running another process on that port!”… but nope. Also, the permissions are set up properly, etc.
The problem here is actually SE Linux. I haven’t quite dug into why, but when running under SystemD, SELinux will deny access to all ports for HAProxy unless you go out of your way to allow it to access them.
The fix is very simple thankfully, just set this selinux boolean as a root/sudo user:
sudo setsebool -P haproxy_connect_any 1
…and voilà! if you restart your HAProxy it will connect fine. I spent a lot of time on this before I found a decent documentation and forum references in these places. I hope this helps you fix it faster! I also found a stack-overflow eventually… but the accepted/good answer is like 10 down so I missed it the first pile of times.
Coding Stream of Consciousness 