similar to: cron.hourly runs twice

greetings on a simple CentOS 4 DNS server install i have the below info. crontab -l "shows nothing" pico /etc/crontab shows... SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root HOME=/ # run-parts 01 * * * * root run-parts /etc/cron.hourly 02 4 * * * root run-parts /etc/cron.daily 22 4 * * 0 root run-parts /etc/cron.weekly 42 4 1 * * root run-parts /etc/cron.monthly i

I've just noticed that cron.daily, etc, do not seem to be running on my CentOS-5.4 system. The scripts in /etc/cron.d/ all run fine, but those in /etc/cron.hourly, etc, seem to be ignored. I see that according to /var/log/cron these commands are seen, eg Feb 28 18:01:01 helen crond[6680]: (root) CMD (run-parts /etc/cron.hourly) but none of the scripts in this directory seem to be touched.

Hellos, Yes, I did some tests with "OnFailure" attribute, but the result was the same: system didn't sent any mail. Daemon and script files were: * crond.service: * [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target OnFailure=crond-notify-email.service [Service] EnvironmentFile=/etc/sysconfig/crond

On 6 Apr 2020, at 12:21, Stephen John Smoogen wrote: > On Mon, 6 Apr 2020 at 04:16, Tobias Kirchhofer <collect at shift.agency> > wrote: > >> On 5 Apr 2020, at 21:20, Tobias Kirchhofer wrote: >> >>>>>> we experience difficulties with crond behaviour sending mail >>>>>> since >>>>>> CentOS 8.1. The cron job is the

Hello, I'm trying to configure a daemon (I'm doing tests with "crond" daemon) to send me an email after daemon restart. My "crond.service" file is: # /etc/systemd/system/crond.service [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target #OnFailure=crond-notify-email@%i.service [Service]

On 5 Apr 2020, at 21:20, Tobias Kirchhofer wrote: >>>> we experience difficulties with crond behaviour sending mail since >>>> CentOS 8.1. The cron job is the same like we used in CentOS 7. > > Meanwhile we found the reason for the bug - actually we do not know if > it is related to a specific version of CentOS or a specific kind of > command as cron job.

I see that mail sent from a remote computer never leaves the computer, the last entry in /var/log/maillog being "Queued mail for delivery". 1. What is likely to cause this message? I know I registered with my remote mail server with a different name to my name on the computer. Is that likely to be the cause of my problem? And if so, what is the solution? Or is there any other likely

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,

hello list!! I'm attempting to find out why this cron job isn't running. the host is centos 5.6 on i386 just so you know. 0 3 * * * /bin/alldb > /home/bluethundr/backupdb/alldb-$(date +%Y%m%d%H%S).sql The job is meant to backup all the databases on a mysql server every day at 3 am. I have checked the backup directory and nothing is showing up for those

> On Mon, 6 Apr 2020 at 06:59, Tobias Kirchhofer <collect at shift.agency> > wrote: > >> On 6 Apr 2020, at 12:21, Stephen John Smoogen wrote: >> >> > On Mon, 6 Apr 2020 at 04:16, Tobias Kirchhofer <collect at shift.agency> >> > wrote: >> > >> >> On 5 Apr 2020, at 21:20, Tobias Kirchhofer wrote: >> >> >>

more messages in the other node of the cluster.../var/log/messages. ======== Jun 1 19:05:59 linux2 kernel: cdrom: open failed. Jun 1 19:05:59 linux2 kernel: cdrom: open failed. Jun 1 19:09:35 linux2 kernel: OCFS2 Node Manager 0.99.10-BETA14 Tue May 31 23:34:42 EDT 2005 (build 82257c19fee200eff2ba31569613b46a) Jun 1 19:09:35 linux2 kernel: OCFS2 DLM 0.99.10-BETA14 Tue May 31 23:34:43 EDT 2005

more messages in the other node of the cluster.../var/log/messages. ======== Jun 1 19:05:59 linux2 kernel: cdrom: open failed. Jun 1 19:05:59 linux2 kernel: cdrom: open failed. Jun 1 19:09:35 linux2 kernel: OCFS2 Node Manager 0.99.10-BETA14 Tue May 31 23:34:42 EDT 2005 (build 82257c19fee200eff2ba31569613b46a) Jun 1 19:09:35 linux2 kernel: OCFS2 DLM 0.99.10-BETA14 Tue May 31 23:34:43 EDT 2005

Hi, I've installed CentOS-4 4 days ago. Now, every 5 minutes, crond opens and close a root session, with no other info. Example: Apr 14 16:25:01 tux crond(pam_unix)[4031]: session opened for user root by (uid=0) Apr 14 16:25:02 tux crond(pam_unix)[4031]: session closed for user root Every five minutes the same thing. I have nothing in /etc/crontab that makes such a thing. Does anyone

Hi, Just updated a few servers to U7, and rebooted them. I found out that crond would not start at boot even if it is configured to: crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off I have tested another reboot, same thing: I had to start crond manually. I don't see anything in the logs, and I don't have direct access to the console right now. Anyone seen the

Does anyone know if the program stunbdc, which prints one's IP address, is available in CentOS-5? It comes with the libnice package in Fedora-11. ------------------------------ [tim at rose ~]$ stunbdc -4 stun.ekiga.net Server address: 75.101.138.128 port 3478 STUN transaction started (timeout 600ms). STUN unknown: 0 mandatory attribute(s)! Received 88-bytes STUN message No

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

Hi all, I've had this error rear it's ugly head again and I'm not exactly sure why. The output in /var/log/message is: crond[14764]: pam_loginuid(crond:session): set_loginuid failed opening loginuid crond[14765]: pam_loginuid(crond:session): set_loginuid failed opening loginuid crond[14811]: pam_loginuid(crond:session): set_loginuid failed opening loginuid

The RHL 6.2 command "/etc/rc.d/init.d/crond start" prevents clean logout from compiled version of OpenSSH-2.5.1p1 on all hosts. The command "/etc/rc.d/init.d/crond stop" is OK. This occurs for interactive or command line requests. ssh remotehost /etc/rc.d/init.d/crond stop --- works every time ssh remotehost /etc/rc.d/init.d/crond start --- hangs every time Control-C will

Hi All. I monitor number of crond processes on my machines. On one of them I have 2 crond processes for a short period of time (few minutes) everyday. It is at the same time when one jobs starts to run - a sphinx indexer. What are the possible causes of crond running a child crond process? Best regards, Rafal.

Fellows, I need some help regarding this thing!1! I get tons of messages like this ? Can anyone help me with resolving this problem ? Dec 18 13:52:42 constellation smbd[8063]: [2005/12/18 13:52:42, 0] lib/util_sock.c:send_smb(647) Dec 18 13:52:42 constellation smbd[8063]: Error writing 4 bytes to client. -1. (Connection reset by peer) Dec 18 14:00:01 constellation crond(pam_unix)[8126]: session