Mailinglist Archive: opensuse (1698 mails)

< Previous Next >
[opensuse] locatedb not being updated by cron.daily
Argh. My mail reader destroyed the original formatting of the log
messages on the mailer's re-edit / re-send message procedure. That's
another bug, for a different list (claws mail).

OK, trying to resend the original message again. Sorry for all this.
When things go wrong, they really go wrong. Bear with me...

=======================================================

Hello. I sent the following message to the list yesterday but I don't
see it so it may have ended up in the bucket. Resending...

=======================================================

Hello...

openSUSE 12.1 / LXDE / 3.1.0-1.2-desktop / 32-bit

While running locate tonight I got the following message...

locate: warning: database `/var/lib/locatedb' is more than 8 days old
(actual age is 12.2 days)

... which seems strange since this has always been automatically done
daily by cron (/etc/cron.daily/suse-updatedb).

According to my yast2>software management>package history, cron was
auto-updated to 4.2 on 8th December. The last successful cron
run of the database update was apparently on 7th December, the day
before this cron update. (also apparently auto-updated on that
date was susefirewall2 but I don't know if that also is somehow
related).

The log output from cron also changed. Here are the relevant lines from
/var/log/messages from 7th December versus 8th December:

Dec 7 21:00:01 msbmain7 run-crons[15107]: logrotate: OK
Dec 7 21:00:08 msbmain7 run-crons[15107]: opensuse.org-online_update: OK
Dec 7 21:00:08 msbmain7 run-crons[15107]: packagekit-background.cron: OK
Dec 7 21:00:08 msbmain7 run-crons[15107]: suse-clean_catman: OK
Dec 7 21:00:11 msbmain7 run-crons[15107]: suse-do_mandb: OK
Dec 7 21:00:11 msbmain7 su: (to nobody) root on none
Dec 7 21:00:11 msbmain7 su: pam_systemd(su:session): Failed to create session:
Invalid argument
Dec 7 21:00:11 msbmain7 su: (to nobody) root on none
Dec 7 21:00:11 msbmain7 su: pam_systemd(su:session): Failed to create session:
Invalid argument
Dec 7 21:00:11 msbmain7 su: (to nobody) root on none
Dec 7 21:00:11 msbmain7 su: pam_systemd(su:session): Failed to create session:
Invalid argument
Dec 7 21:00:14 msbmain7 run-crons[15107]: suse-updatedb: OK
Dec 7 21:00:14 msbmain7 run-crons[15107]: suse.de-backup-rc.config: OK
Dec 7 21:00:29 msbmain7 run-crons[15107]: suse.de-backup-rpmdb: OK
Dec 7 21:00:29 msbmain7 run-crons[15107]: suse.de-check-battery: OK
Dec 7 21:00:29 msbmain7 run-crons[15107]: suse.de-clean-tmp: OK
Dec 7 21:00:29 msbmain7 run-crons[15107]: suse.de-cron-local: OK


Dec 8 21:00:01 msbmain7 run-crons[9639]: logrotate: OK
Dec 8 21:00:20 msbmain7 systemd[1]: Reloading.
Dec 8 21:00:20 msbmain7 run-crons[9639]: opensuse.org-online_update returned
143
Dec 8 21:00:20 msbmain7 run-crons[9639]: packagekit-background.cron returned 1
Dec 8 21:00:20 msbmain7 run-crons[9639]: suse-clean_catman returned 1
Dec 8 21:00:20 msbmain7 run-crons[9639]: suse-do_mandb returned 1
Dec 8 21:00:20 msbmain7 run-crons[9639]: suse-updatedb returned 1
Dec 8 21:00:20 msbmain7 run-crons[9639]: suse.de-backup-rc.config returned 1
Dec 8 21:00:20 msbmain7 run-crons[9639]: suse.de-backup-rpmdb returned 1
Dec 8 21:00:20 msbmain7 run-crons[9639]: suse.de-check-battery returned 1
Dec 8 21:00:20 msbmain7 run-crons[9639]: suse.de-clean-tmp returned 1
Dec 8 21:00:20 msbmain7 run-crons[9639]: suse.de-cron-local returned 1
Dec 8 21:00:21 msbmain7 /usr/sbin/cron[9886]: (CRON) INFO (running with
inotify support)
Dec 8 21:00:21 msbmain7 /usr/sbin/cron[9886]: (CRON) INFO (@reboot jobs will
be run at computer's startup.)


General bug or something unique to me? Help, anyone? Thanks.

Ralph

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups