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

On Tue, Oct 13, 2015 at 1:58 PM, Richard
<lists-centos at listmail.innovate.net> wrote:
>
>
>> Date: Tuesday, October 13, 2015 13:54:28 +0000
>> From: "C. L. Martinez" <carlopmart at gmail.com>
>>
>> On Tue, Oct 13, 2015 at 1:45 PM, Richard
>> <lists-centos at listmail.innovate.net> wrote:
>>>
>>>> Date: Tuesday, October 13, 2015 13:41:56 +0000
>>>> From: "C. L. Martinez" <carlopmart at
gmail.com>
>>>>
>>>>
>>>> On Tue, Oct 13, 2015 at 1:39 PM, Jonathan Billings
>>>> <billings at negate.org> wrote:
>>>>> On Tue, Oct 13, 2015 at 06:24:19AM +0000, C. L. Martinez
wrote:
>>>>>> For example: logwatch. Logwatch sends a daily email
report
>>>>>> about system's health. I didn't received this
email from
>>>>>> October 9th ... and email configuration is ok.
>>>>>
>>>>> So your problem is that cron jobs *DO NOT* run?
>>>>
>>>> Yes. that is the problem ... Sorry If I am not explained very
>>>> well.
>>>
>>> What does /var/log/cron show?
>>
>> Nothing ... It is empty.
>>
>>  Are the jobs triggered, but you don't
>>> get the expected output, or not triggered?
>>
>> They are not triggered ...
>>
>>>
>>> If not triggered, you might want to show your crontab entries.
>>
>> I haven't entries in conrtab's users file at this moment, but I
>> have done a test: * * * * * ls -la, and it is not triggered. But
>> like I say before, installed system cronjobs like logwatch task
>> are not triggered ...
>
> What is returned if you issue the command:
>
>   ps auxw | grep cron | grep -v grep
>
Cron service is running:

root       607  0.0  0.0 126304  1580 ?        Ss   05:33   0:00
/usr/sbin/crond -n

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

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'

-- 
Jonathan Billings <billings at negate.org>

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 ...