I have been getting these error messages in the error log since I updated to 3.0.1 and don’'t know what it is. These are the only messages in there.
Sep 28 09:08:41 localhost – MARK –
Sep 28 09:09:01 localhost CRON: (pam_unix) session opened for user root by (uid=0)
Sep 28 09:09:01 localhost /USR/SBIN/CRON: (root) CMD ( && find /var/lib/php4/ -type f -cmin +$(/usr/lib/php4/maxlifetime) -print0 | xargs -r -0 rm)
Sep 28 09:09:01 localhost CRON: (pam_unix) session closed for user root
Sep 28 09:17:01 localhost CRON: (pam_unix) session opened for user root by (uid=0)
Sep 28 09:17:01 localhost /USR/SBIN/CRON: (root) CMD ( run-parts --report /etc/cron.hourly)
Sep 28 09:17:01 localhost CRON: (pam_unix) session closed for user root
Sep 28 09:28:42 localhost – MARK –
When I look at crontab there is only an hourly running for webmin to sync the time. Not real familier with this part of Linux so I am most likely missing something.
well those are definitely your hourly CRON jobs getting put in there. As to why, I have no idea… Why would Wildfire even care about CRON?
which error log are you refering to? For me it looks like /var/log/messages. Did you configure syslogd to write in wildfire/logs/error.log or do you have a corrupted file system?
When I look at Wildfire here is the location of the log file Log dir: /opt/wildfire/logs
Here are the last few enties in messages:
Sep 29 05:08:48 localhost – MARK –
Sep 29 05:28:48 localhost – MARK –
Sep 29 05:48:48 localhost – MARK –
Sep 29 06:08:48 localhost – MARK –
Sep 29 06:25:04 localhost syslogd 1.4.1#17: restart.
Sep 29 06:48:48 localhost – MARK –
Sep 29 07:08:49 localhost – MARK –
Sep 29 07:28:49 localhost – MARK –
Sep 29 07:48:49 localhost – MARK –
Sep 29 08:08:49 localhost – MARK –
Sep 29 08:28:49 localhost – MARK –
This only started when I upgraded to 3.0.1, it was not showing this information in the logs with the previous stable version.
Thought I would add that all the other log files for Wildfire appear to be normal.
Message was edited by: ItsNewToYou
it looks like a corrupted file system or buggy syslogd, these are not Wildfire messages.
Do you still see these messages if you shutdown syslogd?
I reinstalled syslogd with apt and now it appears that I am getting the correct messages in the log file now so that appeared to be the issue.