Koozali.org formerly Contribs.org

Obsolete Releases => SME Server 7.x => Topic started by: jjcuk on July 08, 2006, 07:51:24 PM

Title: clamav logs showing incorrect date
Post by: jjcuk on July 08, 2006, 07:51:24 PM
Hi all

On checking my clamav logs I note the incorrect
date 2006-07-10,any ideas
------------------------------------
Viewed at Sat 08 Jul 2006 06:46:23 PM BST.

2006-07-10 15:02:48.943005500 --------------------------------------
2006-07-10 15:02:48.943500500 freshclam daemon 0.88.2 (OS: linux-gnu, ARCH: i386, CPU: i386)
2006-07-10 15:02:48.943996500 ClamAV update process started at Mon Jul 10 15:02:48 2006
2006-07-10 15:03:08.951114500 ERROR: Can't query current.cvd.clamav.net
2006-07-10 15:03:08.951123500 ERROR: Can't query current.cvd.clamav.net
2006-07-10 15:03:08.951127500 WARNING: Invalid DNS reply. Falling back to HTTP mode.
2006-07-10 15:03:28.956185500 ERROR: Can't get information about db.local.clamav.net: Temporary DNS error
2006-07-10 15:03:28.956193500 ERROR: Can't get information about db.local.clamav.net: Temporary DNS error
2006-07-10 15:03:28.956198500 ERROR: No servers could be reached. Giving up
2006-07-10 15:03:28.956202500 ERROR: No servers could be reached. Giving up
2006-07-10 15:03:28.956206500 Trying again in 5 secs...
Title: clamav logs showing incorrect date
Post by: dsemuk on July 08, 2006, 09:41:50 PM
If you logon to the console and type
Code: [Select]
date  is your system date correct or the same date as clamav ?

Dave
Title: clamav logs showing incorrect date
Post by: jjcuk on July 08, 2006, 10:06:36 PM
Thanks for reply
it seems to be correct now ?
date shows the same as the "Viewed at Sat 08 Jul 2006 06:46:23 PM BST"
part of the log, I was just puzzled why the clamav log would show next Mondays date July the 10th, when the server date was showing the 8th.

cheers anyway

Jim :-o
Title: clamav logs showing incorrect date
Post by: dsemuk on July 08, 2006, 10:29:30 PM
Weird stuff indeed, any clues in your ntpd log?

Dave
Title: clamav logs showing incorrect date
Post by: jjcuk on July 09, 2006, 11:47:21 AM
seems to be around this area the problem occured
perhaps the server dtg was out and by the time i noticed it had corrected
itself

2006-07-10 16:03:42.455092500 Error : Temporary failure in name resolution
2006-07-10 16:03:42.462347500 10 Jul 16:03:42 ntpdate[3028]: can't find host pool.ntp.org
2006-07-10 16:03:42.462364500
2006-07-10 16:03:42.462367500 10 Jul 16:03:42 ntpdate[3028]: no servers can be used, exiting
2006-07-10 16:03:42.508387500 10 Jul 16:03:42 ntpd[3018]: logging to file /dev/stdout
2006-07-10 16:03:42.508625500 10 Jul 16:03:42 ntpd[3018]: ntpd 4.2.0a@1.1190-r Tue Aug 23 12:05:06 EDT 2005 (1)
2006-07-10 16:03:42.563398500 10 Jul 16:03:42 ntpd[3018]: precision = 1.000 usec
2006-07-10 16:03:42.587144500 10 Jul 16:03:42 ntpd[3018]: Listening on interface wildcard, 0.0.0.0#123
2006-07-10 16:03:42.587325500 10 Jul 16:03:42 ntpd[3018]: Listening on interface lo, 127.0.0.1#123
2006-07-10 16:03:42.587498500 10 Jul 16:03:42 ntpd[3018]: Listening on interface eth0, 192.168.3.30#123
2006-07-10 16:03:42.587707500 10 Jul 16:03:42 ntpd[3018]: kernel time sync status 0040
2006-07-10 16:07:55.779236500 10 Jul 16:07:55 ntpd[3018]: synchronized to LOCAL(0), stratum 10
2006-07-10 16:23:02.553379500 10 Jul 16:23:02 ntpd[3018]: kernel time sync disabled 0041
2006-07-10 16:24:06.607103500 10 Jul 16:24:06 ntpd[3018]: kernel time sync enabled 0001
2006-07-04 13:28:43.926144500  4 Jul 13:28:43 ntpdate[2890]: step time server 192.36.143.234 offset -608187.092857 sec
2006-07-04 13:28:44.031246500  4 Jul 13:28:44 ntpd[2880]: logging to file /dev/stdout
2006-07-04 13:28:44.032128500  4 Jul 13:28:44 ntpd[2880]: ntpd 4.2.0a@1.1190-r Tue Aug 23 12:05:06 EDT 2005 (1)
2006-07-04 13:28:44.236304500  4 Jul 13:28:44 ntpd[2880]: precision = 1.000 usec
2006-07-04 13:28:44.261156500  4 Jul 13:28:44 ntpd[2880]: Listening on interface wildcard, 0.0.0.0#123
2006-07-04 13:28:44.261856500  4 Jul 13:28:44 ntpd[2880]: Listening on interface lo, 127.0.0.1#123
2006-07-04 13:28:44.261862500  4 Jul 13:28:44 ntpd[2880]: Listening on interface eth0, 192.168.3.30#123
2006-07-04 13:28:44.261867500  4 Jul 13:28:44 ntpd[2880]: kernel time sync status 0040
2006-07-04 13:28:49.983049500  4 Jul 13:28:49 ntpd[2880]: frequency initialized 0.000 PPM from /etc/ntp/drift
2006-07-08 16:20:02.484866500  8 Jul 16:20:02 ntpdate[2802]: step time server 195.234.188.3 offset 2.920680 sec
2006-07-08 16:20:02.555884500  8 Jul 16:20:02 ntpd[2796]: logging to file /dev/stdout
2006-07-08 16:20:02.556126500  8 Jul 16:20:02 ntpd[2796]: ntpd 4.2.0a@1.1190-r Tue Aug 23 12:05:06 EDT 2005 (1) :hammer: