Hi,
I have been receiving "logger: socket /dev/log: Connection refused" from the 0anacron script every hour since recently doing an update. I've enabled tracing in the script with -x to try and isolate where it's coming from, but nothing obvious is produced.
I've even disabled selinux to make sure. Running logger manually as root succeeds as expected.
# ls -l /dev/log srw-rw-rw- 1 root root 0 Aug 10 06:04 /dev/log
logger: socket /dev/log: Connection refused /etc/cron.hourly/0anacron:
+ test -r /var/spool/anacron/cron.daily ++ cat /var/spool/anacron/cron.daily + day=20150811 ++ date +%Y%m%d + '[' 20150811 = 20150811 ']' + exit 0 logger: socket /dev/log: Connection refused logger: socket /dev/log: Connection refused logger: socket /dev/log: Connection refused
Any ideas greatly appreciated. Thanks, Alex
On 08/11/2015 02:24 PM, Alex wrote:
I've even disabled selinux to make sure. Running logger manually as root succeeds as expected.
Disabling SELinux because some random program crashes is nothing more than voodoo troubleshooting. If you're not getting alerts about violations, it's not a factor.
Hi,
I've even disabled selinux to make sure. Running logger manually as root succeeds as expected.
Disabling SELinux because some random program crashes is nothing more than voodoo troubleshooting. If you're not getting alerts about violations, it's not a factor.
Yes, thanks. In the past, I've always received a ton of "have you tried with selinux disabled?" responses, so it was an effort to pre-empt those emails.
Thanks, Alex
On 08/11/2015 04:20 PM, Alex wrote:
Yes, thanks. In the past, I've always received a ton of "have you tried with selinux disabled?" responses, so it was an effort to pre-empt those emails.
Understood. I've always found the best answer to be "What makes you think SELinux is involved?"
On 08/12/15 05:24, Alex wrote:
Hi,
I have been receiving "logger: socket /dev/log: Connection refused" from the 0anacron script every hour since recently doing an update. I've enabled tracing in the script with -x to try and isolate where it's coming from, but nothing obvious is produced.
I've even disabled selinux to make sure. Running logger manually as root succeeds as expected.
# ls -l /dev/log srw-rw-rw- 1 root root 0 Aug 10 06:04 /dev/log
No errors here. But a difference
[egreshko@meimei dev]$ ll /dev/log lrwxrwxrwx. 1 root root 28 Aug 10 13:27 /dev/log -> /run/systemd/journal/dev-log
[egreshko@meimei dev]$ ll /run/systemd/journal/dev-log srw-rw-rw-. 1 root root 0 Aug 10 13:27 /run/systemd/journal/dev-log
Hi,
I have been receiving "logger: socket /dev/log: Connection refused" from the 0anacron script every hour since recently doing an update. I've enabled tracing in the script with -x to try and isolate where it's coming from, but nothing obvious is produced.
I've even disabled selinux to make sure. Running logger manually as root succeeds as expected.
# ls -l /dev/log srw-rw-rw- 1 root root 0 Aug 10 06:04 /dev/log
No errors here. But a difference
[egreshko@meimei dev]$ ll /dev/log lrwxrwxrwx. 1 root root 28 Aug 10 13:27 /dev/log -> /run/systemd/journal/dev-log
[egreshko@meimei dev]$ ll /run/systemd/journal/dev-log srw-rw-rw-. 1 root root 0 Aug 10 13:27 /run/systemd/journal/dev-log
Interesting. Perhaps it had something to do with the upgrade from fc21 to fc22. lsof also shows nothing was listening on /dev/log, but systemd is listening on the device you showed:
# ls -l /run/systemd/journal/dev-log srw-rw-rw- 1 root root 0 Aug 10 06:03 /run/systemd/journal/dev-log [root@mail03 cron.hourly]# lsof|grep dev-log systemd 1 root 26u unix 0xffff880036821180 0t0 14422 /run/systemd/journal/dev-log type=DGRAM systemd-j 574 root 4u unix 0xffff880036821180 0t0 14422 /run/systemd/journal/dev-log type=DGRAM
Somehow it's now stopped, at least for this latest hour, but I'll change the device to point to the systemd one anyway.
Thanks, Alex
-
Alex -
Ed Greshko -
Joe Zeff