On 10/19/2015 04:49 AM, C.L. Martinez wrote:
Ok, I have solved this problem partially. First, I have changed under
journald.conf file Storage=volatile instead of Storage=none. After
doing that, logs returned but there is no error under cron.log about
cronjobs, system's jobs included. But they
On 10/14/2015 06:42 PM, Gordon Messmer wrote:
On 10/14/2015 07:09 AM, C.L. Martinez wrote:
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 DEVIC
On 10/14/2015 07:09 AM, C.L. Martinez wrote:
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
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
system
On Wed, Oct 14, 2015 at 09:24:00AM +, 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 wort
On 10/14/2015 04:36 AM, C.L. Martinez wrote:
> On 10/13/2015 04:44 PM, zep wrote:
>>
>>
>> On 10/13/2015 09:54 AM, C. L. Martinez wrote:
>>> 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, in
On 10/13/2015 04:44 PM, zep wrote:
On 10/13/2015 09:54 AM, C. L. Martinez wrote:
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
..
On 10/13/2015 02:59 PM, Jonathan Billings wrote:
On Tue, Oct 13, 2015 at 02:39:24PM +, 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 opti
On 10/13/2015 05:49 PM, m.r...@5-cent.us wrote:
zep wrote:
On 10/13/2015 09:54 AM, C. L. Martinez wrote:
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 ta
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
zep wrote:
> On 10/13/2015 09:54 AM, C. L. Martinez wrote:
>> 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
>
> I'd say that cro
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 :
> On Tue, Oct 13, 2015 at 2:35 PM, Jonathan Billings
> wrote:
> > On T
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 s
On 10/13/2015 09:54 AM, C. L. Martinez wrote:
> 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
> ...
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
On Tue, Oct 13, 2015 at 02:39:24PM +, 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
___
Ce
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
___
CentOS mailing list
CentOS@c
On Tue, Oct 13, 2015 at 2:35 PM, Jonathan Billings wrote:
> On Tue, Oct 13, 2015 at 02:04:49PM +, C. L. Martinez wrote:
>> And according to systemd, without problems:
>>
>> crond.service - Command Scheduler
>>Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled)
>>Active: act
On Tue, Oct 13, 2015 at 02:04:49PM +, 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 P
On Tue, Oct 13, 2015 at 2:11 PM, Scott Robbins wrote:
> On Tue, Oct 13, 2015 at 02:05:47PM +, Richard wrote:
>>
>>
>> >> 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
On Tue, Oct 13, 2015 at 02:05:47PM +, Richard wrote:
>
>
> >> 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, ins
On Tue, Oct 13, 2015 at 1:39 PM, Jonathan Billings wrote:
> On Tue, Oct 13, 2015 at 06:24:19AM +, 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.
>
> Date: Tuesday, October 13, 2015 13:54:28 +
> From: "C. L. Martinez"
>
> On Tue, Oct 13, 2015 at 1:45 PM, Richard
> wrote:
>>
>>> Date: Tuesday, October 13, 2015 13:41:56 +
>>> From: "C. L. Martinez"
>>>
>>>
>>> On Tue, Oct 13, 2015 at 1:39 PM, Jonathan Billings
>>> wrote:
On
On Tue, Oct 13, 2015 at 1:58 PM, Richard
wrote:
>
>
>> Date: Tuesday, October 13, 2015 13:54:28 +
>> From: "C. L. Martinez"
>>
>> On Tue, Oct 13, 2015 at 1:45 PM, Richard
>> wrote:
>>>
Date: Tuesday, October 13, 2015 13:41:56 +
From: "C. L. Martinez"
On Tue, Oct
> Date: Tuesday, October 13, 2015 13:54:28 +
> From: "C. L. Martinez"
>
> On Tue, Oct 13, 2015 at 1:45 PM, Richard
> wrote:
>>
>>> Date: Tuesday, October 13, 2015 13:41:56 +
>>> From: "C. L. Martinez"
>>>
>>>
>>> On Tue, Oct 13, 2015 at 1:39 PM, Jonathan Billings
>>> wrote:
On
On Tue, Oct 13, 2015 at 1:45 PM, Richard
wrote:
>
>> Date: Tuesday, October 13, 2015 13:41:56 +
>> From: "C. L. Martinez"
>>
>>
>> On Tue, Oct 13, 2015 at 1:39 PM, Jonathan Billings
>> wrote:
>>> On Tue, Oct 13, 2015 at 06:24:19AM +, C. L. Martinez wrote:
For example: logwatch. Logw
> Date: Tuesday, October 13, 2015 13:41:56 +
> From: "C. L. Martinez"
>
>
> On Tue, Oct 13, 2015 at 1:39 PM, Jonathan Billings
> wrote:
>> On Tue, Oct 13, 2015 at 06:24:19AM +, C. L. Martinez wrote:
>>> For example: logwatch. Logwatch sends a daily email report about
>>> system's health.
On Tue, Oct 13, 2015 at 06:24:19AM +, 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? Because every me
On Mon, Oct 12, 2015 at 2:59 AM, Eero Volotinen wrote:
> Because systemwide cronjobs are installed in /etc/cron.* directories, not
> in root user cron file..
>
Thanks Eero. I know this. And I have tried to put some cron job in
these directories to test ... and nothing ...
On Mon, Oct 12, 2015 at 12:15 AM, Gordon Messmer
wrote:
> On 10/11/2015 09:38 AM, C. L. Martinez wrote:
>>
>> That's the problem. There is no error but any cron job configured runs..
>> And this is the cuestion: why any cron job works?.
>
>
> It's not clear what you're asking. It would help if yo
Because systemwide cronjobs are installed in /etc/cron.* directories, not
in root user cron file..
Eero
11.10.2015 7.39 ip. "C. L. Martinez" kirjoitti:
> On Sunday, October 11, 2015, Jonathan Billings
> wrote:
>
> > On Oct 11, 2015, at 8:20 AM, C. L. Martinez > > wrote:
> > > I am having stran
On 10/11/2015 09:38 AM, C. L. Martinez wrote:
That's the problem. There is no error but any cron job configured runs..
And this is the cuestion: why any cron job works?.
It's not clear what you're asking. It would help if you replied with an
example of a specific job that's configured on your
On Sunday, October 11, 2015, Jonathan Billings wrote:
> On Oct 11, 2015, at 8:20 AM, C. L. Martinez > wrote:
> > I am having strange problems with my cron jobs in my CentOS7 kvm
> > host. After the initial install and first boot, any cron job
> > configured had run (including cron tasks installe
On Oct 11, 2015, at 8:20 AM, C. L. Martinez wrote:
> I am having strange problems with my cron jobs in my CentOS7 kvm
> host. After the initial install and first boot, any cron job
> configured had run (including cron tasks installed by some rpm
> packages).
Did you have a question or error to po
34 matches
Mail list logo
