similar to: cron.allow.local

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.

Hi, we experience difficulties with crond behaviour sending mail since CentOS 8.1. The cron job is the same like we used in CentOS 7. crontab -l /usr/bin/python3 -c 'import random; import time; time.sleep(random.random() * 3600)' && /usr/local/bin/backup.sh backup.sh writes the backup to the remote backup server. There are around 30 machines with the same cron job. The python

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

On 27 Feb 2020, at 14:42, Jonathan Billings wrote: > On Feb 27, 2020, at 08:01, Tobias Kirchhofer <collect at shift.agency> > wrote: >> >> ?Hi, >> >> we experience difficulties with crond behaviour sending mail since >> CentOS 8.1. The cron job is the same like we used in CentOS 7. >> >> crontab -l >> /usr/bin/python3 -c 'import

From: Christian Hesse <mail at eworm.de> Logging to stderr results in line endings being terminated with carriage return (\r) and new line (\n). While this is fine for terminals it may have undesired effects when running from crond and logging to syslog or similar. I run ssh from cron on an recent linux host. Viewing logs with journalctl I see: Sep 06 16:50:01 linux CROND[152575]: [96B

Do you need cron installed for the files in /etc/cron.daily/ to execute? Did a Centos 6.x minimal openvz install and noticed cron is not installed by default and after installing mlocate cant help but wander if it will be updated without it.

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

On Fri, 2019-11-15 at 16:32 -0500, Karl Vogel wrote: > > > On Fri, Nov 15, 2019 at 05:54:07PM +0000, John Horne wrote: > > J> In trying to resolve a problem with a cron job, we can see when the job > J> starts by looking in the /var/log/cron log file. However, I was asked if > J> when the job ends could also be logged. (It seems to be something that > J> crops

Hello there, I've just noticed that scripts in /etc/cron.{daily,weekly,...} are not launched for several weeks (I noticed a `locate` not finding a recently added binary). Exactly, it's since June 02, and `# service cron status` says: Redirecting to /bin/systemctl status crond.service * crond.service - Command Scheduler Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled;

Hi, A couple of days ago, cron service stopped been running on my Centos 6. When I try to start with "service crond start" I get this error : "Starting /usr/sbin/crond: [-] Error 0x7a911401 in attaching to process!" Any ideas? Thanks

Hi all, CentOs has choosen anacron as default cron daemon. I did not look further about the reasons, I think there are some good reasons. I want to create a minute based set of scripts. No much precision required, once a minute more or less 20 sec is OK. Using anacron, how do you recommend to do it? Is anacron the right tool? Otherwise what's the right tool? -- RMA.

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

For some reason I cannot fathom, cron.hourly runs twice each hour on one of my two CentOS-5.4 systems, as reported in /var/log/cron: ------------------------- Mar 16 14:01:01 helen crond[27833]: (root) CMD (run-parts /etc/cron.hourly) Mar 16 14:01:01 helen crond[27834]: (root) CMD (run-parts /etc/cron.hourly) ------------------------- On the other it just runs once, as expected.

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

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: > >> > >>>>>> we experience difficulties

Anything interesting in the logs? sudo journalctl -xf _SYSTEMD_UNIT=crond.service

Hi When I enable a box to do authentication using LDAP it breaks cron for users like jboss. I get the following in /var/log/secure Sep 14 15:25:01 exoipatest01 crond[7214]: pam_access(crond:account): access denied for user `jboss' from `cron' I have the following in /etc/ldap.conf nss_initgroups_ignoreusers root,ldap,named,avahi,haldaemon,dbus,tomcat,radiusd,news,mailman,nscd,jboss

Hi, Last year, I installed Asterisk 10.4.2 and enabled logrotate on daily basis which was working perfect. Now in couple of months back, the logrotate feature is not working at all but simply appending the logs in 'messages' file. Listing down down the configuration for logrotate below; /var/log/asterisk/messages { missingok rotate 5 daily postrotate /usr/sbin/asterisk -rx 'logger

hey centos long time no hear! :) I'm having a small issue where the backup jobs that I set to run in the crontab of the backup user do not appear to be running. Here's how I set it up (with crontab -e as the backup user): run amanda every night (check at 2:45 and backup at 3) 45 2 * * * /usr/sbin/amcheck /var/log/amanda/crontab/amcheck.log * 3 * * * /usr/sbin/amdump

>>> 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. Let me explain what we have: - sssd for ssh login of ldap user - crond for