similar to: a gotcha with cron and 4.2

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

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

Well, I feel silly.? There are three places MAILTO can affect crond: /etc/crontab, /etc/crond.d/0hourly, and /etc/anacrontab.? Once I set this in these 3 files, I started getting mail from crond.? Thank you all for your help. --- Chad Cordero Information Technology Consultant Enterprise & Cloud Services Information Technology Services California State University, San Bernardino 5500

I am troubleshooting a new cron line that is triggering logcheck. Other cron entries do not trigger logcheck, even though they are logged in /var/log/syslog This is a security trigger, and I know it is because of certain words in the cron entry. What I can't figure out is which entry in logcheck is ignoring the other cron events? Here is a cron log from syslog that does not

On Thu, July 20, 2017 8:54 am, Richard wrote: > >> Date: Thursday, July 20, 2017 02:25:52 +0000 >> From: Richard <lists-centos at listmail.innovate.net> >> >>> Date: Wednesday, July 19, 2017 23:31:10 +0000 >>> From: Chad Cordero <ccordero at csusb.edu> >>> >>> It???s being rejected before it even reaches the mailbox, so

Hi, I have been trying to set up a network bridge on my FreeBSD 3.4 machine (hades), and as soon as I enable the bridge, Samba stops servicing requests from both sides of the network. The following is a 'diagram' to give you an idea of my setup. |------| |----+Charon| |-------| |----| | |------| |Neptune+----+Hades+----|

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

> 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 Saturday 23 of April 2016 10:08:54 AM Kahlil Hodgson wrote: > Anything interesting in the logs? > > sudo journalctl -xf _SYSTEMD_UNIT=crond.service Don't know. [root at kohrin cron.d]# sudo journalctl -xf _SYSTEMD_UNIT=crond.service -- Logs begin at ?ro 2015-12-02 22:34:16 CET. -- kwi 22 23:11:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron) kwi 22 23:13:01

> Date: Thursday, July 20, 2017 02:25:52 +0000 > From: Richard <lists-centos at listmail.innovate.net> > >> Date: Wednesday, July 19, 2017 23:31:10 +0000 >> From: Chad Cordero <ccordero at csusb.edu> >> >> It?s being rejected before it even reaches the mailbox, so >> forwarding won?t work.? Crond should really be using the MAILTO >>

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 same like we used in CentOS 7. > > > > Meanwhile we found the reason for the bug - actually we do

Having a difficult problem getting my pam_access.so module enforced on a 3.0.22 version of Samba. Here is my /etc/pam.d/samba file: auth required pam_winbind.so debug account required pam_access.so account sufficient pam_winbind.so debug account include system-auth session include system-auth session required pam_winbind.so debug My

I am running CentOS 7 on an outbound gateway server running Postfix.? I have a couple of cron jobs I was expecting to see in my email that never showed up.? It turns out that they were delivered to root, which is restricted on our exchange server, instead of the address I defined.? Please help. # cat /etc/crontab SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=ecssupport at

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, I've stumbled upon this problem while trying to limit access to specific machine to specific domain users. I did it by setting Samba to obey PAM restrictions, and then using the pam_access PAM module ('account' clause) to do user validation (described below). On Win2000, this works fine - if an unauthorized user tries to login, Win2000 says 'Account not permitted to

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

I have a root cron job that powers down my server every day at 1am and 6pm. The output of '# crontab -l' is shown below. * 1,18 * * * poweroff Last night, after the server powered down at 6pm, I decided I wanted to use the server so I started it with the power button. The server, after a minute or so, powered itself down. This behaviour happened repeatedly until I waited past 7pm.

Hi, I am having a strange problem, where I cannot get pam_access to work as intended. I have placed the following line in /etc/pam.d/system-auth account required /lib/security/pam_access.so Then, in /etc/security/access.conf, I have put the following line: -:mok:10.14.44.104 I.e. I should prevent myself from logging on from host 10.14.44.104. However, when I try to log on (using

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.