Looking at the crawler mirrormanager log files on bapp02 it seems the last crawler run had some kind of problem:
-rw-r--r--. 1 mirrormanager mirrormanager 0 Sep 11 04:02 crawler.log -rw-rw-r--. 1 mirrormanager mirrormanager 0 Sep 11 04:02 generate-publiclist.log
Both files have no content and it seems the last run of the crawler has finished. Looking at the output of crawler_perhost in /var/log/mirrormanager/crawler it also seems all recent log files are empty.
It would probably be a good thing to start the crawler manually to update the mirrormanager database.
Adrian
On Thu, 11 Sep 2014 11:31:12 +0200 Adrian Reber adrian@lisas.de wrote:
Looking at the crawler mirrormanager log files on bapp02 it seems the last crawler run had some kind of problem:
-rw-r--r--. 1 mirrormanager mirrormanager 0 Sep 11 04:02 crawler.log -rw-rw-r--. 1 mirrormanager mirrormanager 0 Sep 11 04:02 generate-publiclist.log
Both files have no content and it seems the last run of the crawler has finished. Looking at the output of crawler_perhost in /var/log/mirrormanager/crawler it also seems all recent log files are empty.
It would probably be a good thing to start the crawler manually to update the mirrormanager database.
I figured out the issue and it's running again now.
It seems the pid file was owned by root, so perhaps someone tried to run it as root instead of mirrormanager?
Anyhow, it should be running now.
kevin
infrastructure@lists.fedoraproject.org