Red Hat Bugzilla – Bug 24519
slocate cron job error
Last modified: 2014-03-16 22:18:19 EDT
/etc/cron.daily/slocate.cron: fatal error: updatedb: create_db(): rename: No such file or directory I think this may have begun happening only after updating to slocate-2.5-1, but it seems I've got a couple messages about it sitting in the local mailspool.
I couldn't reproduce your problem here. After updating to slocate-2.5-1 no errors occured, but when I removed /var/lib/slocate/slocate.db I got: warning: updatedb: could not open database: /var/lib/slocate/slocate.db: No such file or directory, but afterwards it worked everytime without problems. Please, check: 1. the existance of the /var/lib/slocate directory 2. remove all slocate.*-files there, 3. and try again by directly starting /etc/cron.daily/slocate.cron You should get one error, but after that it should work cleanly again.
Even if only generated on the initial install on the slocate package, it still shouldn't generate an error that gets mailed to root due to the confusion this causes to users. See bugs 13611 and 14222 for previous reports and resolutions of this on older versions of slocate
*** Bug 25252 has been marked as a duplicate of this bug. ***
Fixed in 2.5-2; slocate-2.5-info patch was broken.