[rsyslog-notify] Forum Thread: Re: ERROR: imuxsock cannot create /dev/log - (Mode 'reply')
noreply at adiscon.com
noreply at adiscon.com
Thu Feb 27 10:52:31 CET 2014
User: andygr
Forumlink: http://kb.monitorware.com/viewtopic.php?p=24266#p24266
Message:
----------
Thanks for the link. BTW - it looks like the PrivDrop is handled just
right. Looks like it affects mainly the creation of /var/log files.
7069.656806875:2acbf960: telling modules to activate config (before
dropping privs) 0x6d4b0 <-- DO IMUXSOCK BEFORE DROPPING
7069.656887616:2acbf960: pre priv drop activating config 0x6d4b0 for module
imuxsock
7069.657055764:2acbf960: Called LogError, msg: cannot create '/dev/log'
Maybe rsyslog gets confused by having current Debian running under antique
Droid (Kernel v2.6.35). I know that Apache for example would not run in
this environment. It checks only the chroot and assumes a modern kernel and
uses some parameters for creating network sockets which do not work on the
old Droid Kernel. Next - I will try to either upgrade to the KitKat kernel
(v3.4) or downgrade rsyslog to more ancient version like v5 or v6 (why oh
why is everybody so chroot unfriendly these days).
More information about the rsyslog-notify
mailing list