search for: uxsock

...fs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME systemd 1 root 27u unix 0xffff880250ea0f00 0t0 1436 /dev/log systemd-j 263 root 5u unix 0xffff880250ea0f00 0t0 1436 /dev/log In theory, rsyslog is listenning to uxsock and imjournal: # rsyslog configuration file # For more information see /usr/share/doc/rsyslog-*/rsyslog_conf.html # If you experience problems, see http://www.rsyslog.com/doc/troubleshoot.html #### MODULES #### # The imjournal module bellow is now used as a message source instead of imuxsock....

On Tue, Oct 13, 2015 at 2:35 PM, Jonathan Billings <billings at negate.org> wrote: > On Tue, Oct 13, 2015 at 02:04:49PM +0000, C. L. Martinez wrote: >> And according to systemd, without problems: >> >> crond.service - Command Scheduler >> Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled) >> Active: active (running) since Tue 2015-10-13

On 10/13/2015 07:39 AM, C. L. Martinez wrote: > Nop, because binary logs (using journalctl) are disabled in this host > ... But under /var/log/messages, there is no error ... If you haven't reconfigured rsyslogd to use the uxsock source, disabling the journal will also disable the legacy logging system. If your cron log is actually empty, then you probably aren't getting any logs at all. Start by turning your logging system back on. It's the best source of data that you have at this point.

On 10/13/2015 02:59 PM, Jonathan Billings wrote: > On Tue, Oct 13, 2015 at 02:39:24PM +0000, C. L. Martinez wrote: >> Nop, because binary logs (using journalctl) are disabled in this host >> ... But under /var/log/messages, there is no error ... > > How did you disable journald? > Changing Storage's option under /etc/systemd/journald.conf to none.

...n't holding that socket. That's outside my experience, but I'd imagine that you can: systemctl disable systemd-journald.service systemctl stop systemd-journald.service Then you'll need to restart rsyslog and verify that it owns /dev/log. > In theory, rsyslog is listenning to uxsock and imjournal: Only one process can have a socket open at a time. Since journald holds /dev/log, rsyslog can't, which is why your cron log is empty. > #### MODULES #### > # The imjournal module bellow is now used as a message source instead > of imuxsock. > $ModLoad imuxsock #...

...That's outside my experience, but I'd imagine that you can: > > systemctl disable systemd-journald.service > systemctl stop systemd-journald.service > > Then you'll need to restart rsyslog and verify that it owns /dev/log. > >> In theory, rsyslog is listenning to uxsock and imjournal: > > Only one process can have a socket open at a time. Since journald holds > /dev/log, rsyslog can't, which is why your cron log is empty. > >> #### MODULES #### >> # The imjournal module bellow is now used as a message source instead >> of imuxsoc...