CentOS - Oct 2015 - Exists some problem with cronjobs under CentOS7

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.

On Wed, Oct 14, 2015 at 09:24:00AM +0000, C.L. Martinez
wrote:
> On 10/13/2015 02:59 PM, Jonathan Billings wrote:
> >How did you disable journald?
> Changing Storage's option under /etc/systemd/journald.conf to none.
While Storage=none is supposed to forward on messages to syslog, it
might be worth checking to see what process owns /dev/log:
# lsof /dev/log


-- 
Jonathan Billings <billings at negate.org>

On 10/14/2015 01:56 PM, Jonathan Billings wrote:
> lsof /dev/log
Uhmm ... that is not what I expect:

lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
       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.
$ModLoad imuxsock # provides support for local system logging (e.g. via 
logger command)
$ModLoad imjournal # provides access to the systemd journal
#$ModLoad imklog # reads kernel messages (the same are read from journald)
#$ModLoad immark  # provides --MARK-- message capability