That solved our problem!
Thank you for your help, Holger.
Cheers
Rui

from eturnal.

We tried to reproduce the issue by installing CentOS 7 but things work just fine here. It seems your systemd/journald version/setup is different from what I got after installing CentOS 7 and running yum update, though. On my system, the old systemd-journald.socket unit is used, which reads /dev/log directly. I.e., /dev/log is not a symlink (to /run/systemd/journal/dev-log) on a vanilla CentOS 7 system, as far as I can see. So I'm not quite sure how to reproduce your issue, I'm afraid.

Anyway, what's the output of ls -l /run/systemd/journal/dev-log?

from eturnal.

Thanx, Holger for looking into this. The output of

ls -l /run/systemd/journal/dev-log

srw-rw---- 1 root mysyslog 0 May 1 15:54 /run/systemd/journal/dev-log

from eturnal.

Ok, so only processes run by users in the mysyslog group are permitted to log messages on your system (quick web search sounds as if that might be a ConfigServer thing?). I guess one workaround could be to add eturnal to that group, e.g. by calling systemctl edit eturnal and entering:

[Service]
SupplementaryGroups=mysyslog

from eturnal.