Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: Tom Carroll on June 19, 2003, 06:08:26 PM

Title: Logrotate errors - still
Post by: Tom Carroll on June 19, 2003, 06:08:26 PM

Version: 5.6U4 UDR
Mode: Server & Gateway

I asked several weeks ago without any response.  I will try to address one issue at a time concerning my logrotate cron job.

Here is the first, which is repeated on a daily basis:

/etc/cron.daily/slocate.cron:

fatal error: updatedb: create_db(): rename: No such file or directory

I am assuming it is caused by this line in /etc/cron.daily/slocate.cron:

/usr/bin/updatedb -f "nfs,smbfs,ncpfs,proc,devpts" -e "/tmp,/var/tmp,/usr/tmp,/afs,/net"

I do not have any directories named "/afs" or "/net".  Also, the "/usr/tmp" is a hard link to "/var/tmp".

I remove the reference to "/afs", "/net", and "/usr/tmp" in the slocate.cron job, to see if it will hurt anything.

How do I cause the daily, or any cron job for that matter, to run?

Thanks!

Tom

Title: Re: Logrotate errors - still
Post by: Nathan Fowler on June 19, 2003, 09:38:33 PM

If you've isolated that command as the root cause, I'd simply run /sbin/updatedb with the passed directories in the list, minus the ones you say are missing.  If it works, then you've found your root cause and can update the template (if it is templated) accordingly.

Hope this helped,
Nathan

Title: Re: Logrotate errors - still
Post by: Jon Blakely on June 20, 2003, 04:24:16 PM

Tom,

I think you are barking up the wrong tree. The -e means exclude those directories. If you havn't got those directories (and none of us do) it doesn't matter.
Check to see that you have a file

/var/lib/slocate/slocate.db

and it should have permissions of

-rw-r-----    1 root     slocate

slocate.db is the database that is created daily by updatedb. It looks like updatedb is trying to rename the old database for the new one but can't, either due to the file not being there or permission problems.

Jon

Title: Re: Logrotate errors - still
Post by: Tom Carroll on June 20, 2003, 04:38:43 PM

I checked it out Jon, but the permissions and ownership are in fact as you say they should be.  Here is another cron message I got this morning:
------------------------------------------
From: Cron Daemon [root@carrollweb.net]
Subj: Cron run-parts /etc/cron.daily

/etc/cron.daily/slocate.cron:

fatal error: updatedb: create_db(): rename: No such file or directory
------------------------------------------
I changed the entry as mentioned in the previous message, so that evidently did not fix the problem.

Tom