Today I was running a license scan with Fossology 1.0 when my Apache server stopped unexpectedly. I started looking around in my logs to see if I could figure out what caused it and found this in my syslog right around the time of the crash:
Mar 3 11:39:01 engsrv3 cron[6236]: Error: bad username; while reading /etc/cron.d/Fossology Here are the contents of /etc/cron.d/Fossology: # this cron should be run daily by user postgres for fossology database # # Copyright (C) 2007 Hewlett-Packard Development Company, L.P. # # cluster 0 0 * * * if [ -x /usr/bin/clusterdb ]; then /usr/bin/clusterdb --username postgres fossology >/dev/null; fi # # Run VACUUM ANALYSE on all databases every 5 hours if pg_autovacuum is not # running 0 3 * * * if [ -x /usr/sbin/pg_maintenance ]; then /usr/sbin/pg_maintenance --full --analyze >/dev/null; fi I saw it a few more times after that as well: Mar 3 11:39:01 engsrv3 cron[6236]: Error: bad username; while reading /etc/cron.d/fossology Mar 3 11:42:01 engsrv3 cron[6236]: Error: bad username; while reading /etc/cron.d/fossology Mar 3 11:49:01 engsrv3 cron[6236]: Error: bad username; while reading /etc/cron.d/fossology Mar 3 11:51:01 engsrv3 cron[6236]: Error: bad username; while reading /etc/cron.d/Fossology Two questions: 1) could this be related to my Apache crash in anyway? 2) what does this mean? I'm running on Ubuntu 8.04.2 (Hardy) 64bit. Thanks, Dave McLoughlin | OpenLogic [email protected] 720 240 4530 | phone 303 818 1686 | cell 720 240 4556 | fax @OpenLogic | twitter 1 888 OpenLogic | toll free www.openlogic.com OpenLogic, Inc. Headquarters, Broomfield, Colorado 80021 <http://www.openlogic.com>
<<image001.gif>>
_______________________________________________ fossology mailing list [email protected] http://fossology.org/mailman/listinfo/fossology
