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

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 05:33:28 UTC; 8h ago
>>  Main PID: 607 (crond)
>>    CGroup: /system.slice/crond.service
>>            ??607 /usr/sbin/crond -n
>
> Do you see anything helpful in the journal?
>
> run 'journalctl _SYSTEMD_UNIT=crond.service'
>
Nop, because binary logs (using journalctl) are disabled in this host
... But under /var/log/messages, there is no error ...

On Tue, 13 Oct 2015, C. L. Martinez wrote:
> Nop, because binary logs (using journalctl) are disabled in this host
> ... But under /var/log/messages, there is no error ...
Might it be an idea to *not* disable logging?

jh

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?  
-- 
Jonathan Billings <billings at negate.org>

John Hodrien wrote:
> On Tue, 13 Oct 2015, C. L. Martinez wrote:
> 
>> Nop, because binary logs (using journalctl) are disabled in this host
>> ... But under /var/log/messages, there is no error ...
> 
> Might it be an idea to *not* disable logging?
More to the point, perhaps, is there any way
of recovering the entries that used to be in /var/log/ eg maillog?
Does "journalctl -u sendmail" give exactly the same information?
And what exactly is the status of syslog now?


-- 
Timothy Murphy  
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin

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.

Please note that /etc/cron.* files use a bit different syntax as normal
crontab entries. First entry is user-id for cron job. It also requires
strict permissions like (rw,r,r)

Eero

2015-10-13 17:39 GMT+03:00 C. L. Martinez <carlopmart at gmail.com>:
> 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 05:33:28 UTC; 8h
ago
> >>  Main PID: 607 (crond)
> >>    CGroup: /system.slice/crond.service
> >>            ??607 /usr/sbin/crond -n
> >
> > Do you see anything helpful in the journal?
> >
> > run 'journalctl _SYSTEMD_UNIT=crond.service'
> >
>
> Nop, because binary logs (using journalctl) are disabled in this host
> ... But under /var/log/messages, there is no error ...
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

On 10/13/2015 05:38 PM, Gordon Messmer wrote:
> 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.

Correct Gordon, but I have enabled uxsock under rsyslog.conf to avoid 
the situation that you have explained.

Thanks.

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.