similar to: cron error message

List, Being pretty new to CentOS and such, can someone answer a couple of questions about yum and up2date? I think I got the basic info, but I'm a bit confused about what does what. I configured yum to use the dag repo (I think) but now and then, I get the red circle from up2date stuff on the upper menubar. I have been using the up2date function to grab the latest bits when

Is it possible to set up a single disk raid (kind of redundant to call a single disk an array) but I've got a single SATA drive in the machine not doing anything. It's a 10k maxtor 74G drive, and what I really want is just to backup two home partitions. I can always reinstall the OS, but the data can't be recovered that easily. The mobo supports raid-0,1 and jbod. Suggestions? --

Hello, This morning, root received an e-mail from the cron daemon as the following: -------------------------------- Subject: Cron <root> run-parts /etc/cron.daily /etc/cron.daily:00webalizer: Warning: Truncating oversized referrer field -------------------------------- I haven't changed anything to cron or to my intranet website (I'm assuming that's what the webalizer

Just looked at the log from the x86_64 machine and I see the same zcat: stdout: Broken pipe in the 00-makewhatis.cron job as on the x86 machine. Did I miss some thread about current updates somewhere? sam -- Sam W.Drinkard -- sam at wa4phy.net NOAA Cooperative Observer http://wa4phy.net Augusta Area Mesonet

/etc/cron.daily/apt: Traceback (most recent call last): File "/usr/sbin/update-apt-xapian-index", line 581, in <module> import os.path, re, imp, glob, xapian, textwrap, shutil, fcntl, errno, itertools, time File "/usr/lib/python2.6/dist-packages/xapian.py", line 6, in <module> import _xapian ImportError: /usr/lib/python2.6/dist-packages/_xapian.so:

This may be considered a newbie question, and for me, yum is a new tool. I have discovered via yum, I am *supposed* to have libf2c (386) and libf2c (x86-64) installed. Searching the two libs, I find I only have the 32-bit version installed, and I need both. Should I use yum to remove the pkgs, and then reinstall, or should I use rpm to do the installs? Again, I'm from the BSD camp, so

> > For the record: > # service anacron status > Redirecting to /bin/systemctl status anacron.service > Unit anacron.service could not be found. > You have mail in /var/spool/mail/root It's not a service. As I said, it's run using a script in /etc/cron.hourly > > Sure, anacron is not installed. So how could stuff in /etc/cron.{daily,weekly} > work until June

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 =

Hello, On my old centos 5 system I get updates from yum automatically, it sends a mail to root. on my new centos 6 things have changed and it has a thing called 'yum-cron' I have it on and it is working....except I can find no particular file where mailto might be added. The crontab is going to root, but yum-cron has nothing as far as a variable for this. yum-cron has no man page, no

Hello, I have 2 servers which share 2 partitions with drbd, on each machine runs one VM on the drbd device, so that I have primary/secondary and secondary/primary drbd devices. There are also some more XEN VM?s that only do aa mysql replication and one is standalone. In the last 4 weeks I had 2 incidents where both machines did a sudden reboot, first one machine and 2 minutes later the other one.

Package: logcheck Version: 1.2.32 Severity: wishlist /etc/cron.daily/sysklogd restarts syslogd at the end of the script. This causes a daily log message, currently missed by logcheck: Jan 14 06:55:22 pyloric syslogd 1.4.1#16: restart (remote reception). I'm currently using this regex in ignore.server.d/local-syslogd: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ syslogd 1\.4\.1#16: restart \(remote

Hi, I just configured SquidAnalyzer, a nifty little network statistics tool that I'm using mainly in school networks to monitor network usage. I want to run the '/usr/bin/squid-analyzer' script once a day. I took a peek in /etc/cron.daily, and the package already installed an /etc/cron.daily/0squidanalyzer script. I wanted to know at what time CentOS ran the cron.daily scripts,

> > So, service is running but what could happen that makes /etc/cron.* not > being fired? You don't say, but if this is CentOS 7, then cron.daily/weekly/monthly is run using anacron, not cron. It's configured in /etc/anacrontab and is usually run once a day by the script /etc/cron.hourly/0anacron - cron.hourly is still run by cron. If the script doesn't exist, then

Hi. I'm installed yum-cron and set: # by default MAILTO is unset, so crond mails the output by itself # example: MAILTO=root MAILTO="root at domain.org.ua" I see in log that yum-cron done it's job: # grep "yum" /var/log/cron Aug 11 03:08:02 venti run-parts(/etc/cron.daily)[4516]: starting 0yum.cron Aug 11 03:49:30 venti run-parts(/etc/cron.daily)[4761]: finished

Found this entry in the log this morning. Never have seen such before....... --------------------- Named Begin ------------------------ **Unmatched Entries** dispatch 0x8ea6e48: shutting down due to TCP receive error: connection reset: 1 Time(s) ---------------------- Named End ------------------------- -- Snowman

After update from CentOS 3.4 to 3.5 on 3 different boxes, I got the following message from each server ============================================ Subject: Cron <root at premiere> run-parts /etc/cron.daily > /etc/cron.daily/makewhatis.cron: > > > zcat: stdout: Broken pipe > > zcat: stdout: Broken pipe > > zcat: stdout: Broken pipe > > zcat: stdout:

Hi all I have a '/etc/cron.daily/push-to-backup' script which the content is: #!/bin/bash /usr/bin/rsync [... long options line ...] echo "finished pushing to the backup" Launched manually, it's OK. Waiting for cron to execute it, In the "/var/log/cron", I see the starting time and the finish time, and I see it take about 10 minutes to make the job.

Hello Pete, On Mon, 02 Jul 2018 09:59:17 +0100 Pete Biggs <pete at biggs.org.uk> wrote: > > > > So, service is running but what could happen that makes /etc/cron.* not > > being fired? > > You don't say, but if this is CentOS 7, then cron.daily/weekly/monthly > is run using anacron, not cron. Oops, yes CentOS 7, sorry. For the record: # service anacron

We have some third party software running on a CentOS 4.5 virtual machine. The software is delivered as compiled python and I wrote an init script for it myself (/etc/init.d/gk). Because the software lacks the usual robustness of CentOS services, I have a bash script (/etc/cron.daily/gk-restart) which simply calls "/etc/init.d/gk restart". So, as expected, root gets an email every day

The rpm package used to provide /etc/cron.daily/rpm /etc/logrotate.d/rpm I see /usr/lib/rpm/rpm.log and rpm.daily, which looks like they're intended for that purpose. Anyone have any idea why they're not in cron.daily and logrotate.d? mark