similar to: yum-cron email notification doesn't appear

Hi. I have installed Zabbix 2.2.6 on CentOS 6.5. Question not too relative to CentOS, but hope somebody can help with it. All triggers works correctly, but venti:system.users.num.last(0)}>0 - dont't. Screenshot one: http://i.stack.imgur.com/YM9mu.png And second one: http://i.stack.imgur.com/TMNqx.png From manual

Hi, Up until now I always kept my servers up-to-date manually. Currently I'm experimenting with yum-cron to automate this process. I read through various online tutorials, and now I have a couple questions. 1. As far as I know, when editing /etc/yum/yum-cron.conf, I can only use the following value for update_cmd : update_cmd = default If I understand this correctly, 'update_cmd =

LDAP Account Manager (LAM) 5.0 - June 30th, 2015 ================================================ LAM is a web frontend for managing accounts stored in an LDAP directory. Announcement: ------------- LAM Pro can notify your users via cron job that their passwords will expire soon. The Windows support was also enhanced. LAM no longer supports Internet Explorer 8. Full changelog:

I receive messages like this from cron often. Not every hour, and not consistently between the servers running CentOS, but at least two per day. Is this normal? /etc/cron.hourly/0yum-hourly.cron: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: HTTP Error 403 - Forbidden Could not retrieve mirrorlist

Hi, folks, Has anyone else seen the issue of having an excludes= in /etc/yum.conf, but yum-cron appears to be ignoring it? This may have been the case earlier this year, where it seemed to partly install a new kernel, then not done the post-install. I *think* that's what I'm seeing on a box with twin Tesla cards, with yum.conf: exclude=kernel* xorg* cuda* kmod* and yet cron.daily

It looks like my CentOS 4.2 box is attacking other people with some type of ftp attack. I got an email from somebody saying they were being attacked by my IP address. Further investigation /var/log/messages shows a whole bunch of sshd attacks on me, none of which appear successful. I'm running ethereal right now and I can see that my system is doing some kind of ftp attacks on others.

Hello, I have thousands of this messages on my servers ?? Is this a Problem on my site or is the infrastructure broken?? /etc/cron.hourly/0yum-hourly.cron: Could not get metalink https://mirrors.fedoraproject.org/metalink? repo=epel-7&arch=x86_64 error was 14: HTTPS Error 503 - Service Unavailable Thanks for a answer, -- mit freundlichen Gr?ssen / best regards, G?nther J. Niederwimmer

Hi all, 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). Last cron's entry log is: Oct 9 17:01:01 santgraal CROND[9014]: (root) CMD (run-parts /etc/cron.hourly) Oct 9 17:01:01 santgraal run-parts(/etc/cron.hourly)[9014]: starting 0anacron

Puppet 3.2.4 is now available. 3.2.4 addresses two security vulnerabilties discovered in the 3.x series of Puppet. These vulnerabilities have been assigned Mitre CVE numbers CVE-2013-4956 and CVE-2013-4761. All users of Puppet 3.2.3 and earlier are strongly encouraged to upgrade to 3.2.4. For more information on these vulnerabilities, please visit http://puppetlabs.com/security/cve/cve-2013-4761

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

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

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

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

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

Hi, I'm regularly getting spammed by my own servers, with the following message: /etc/cron.hourly/0yum-hourly.cron: Not using downloaded epel/repomd.xml because it is older than what we have: Current : Sat Sep 12 19:05:04 2020 Downloaded: Thu Sep 10 19:12:19 2020 How can I make this nonsense stop? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de

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.

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.

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;

On 23 April 2016 at 10:25, Marcin Trendota <moonwolf.rh at gmail.com> 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 > ?...? > (/etc/cron.d/osticket-cron) > kwi 22 23:28:01 vz471 crond[30534]: (*system*)