Time date in logs not correct.
-
So the time in the logs is off. It appears to be off by like 9 hours.
Still trying to figure this one out.
Sincerely,
Brendhan -
Is it exactly 9hrs?
-
I believe it is.
Nov 3 22:36:45 Ignis filterlog[16230]: 82,,,1770008940,ix5,match,block,in,4,0x28,,12,39,0,DF,1,icmp,44,1.71.141.102,104.219.179.88,request,62198,3824 Nov 3 22:36:46 Ignis filterlog[16230]: 4,,,1000000103,ix5,match,block,in,4,0x0,,235,8021,0,none,6,tcp,40,91.191.209.14,104.219.179.88,55893,40656,0,S,871183069,,1024,, [2.6.0-RELEASE][admin@Ignis.brendhanhorne.com]/root: date Thu Nov 3 13:36:52 EDT 2022 -
Hmm, curious. The timezone you have set is not 9hrs from UTC.
Have you tried setting different TZ and then switching back? Or setting GMT+5 directly?
-
Hello!
Have you restarted all of the relevant services since making any system timezone changes?
John
-
@serbus Yes
-
[2.6.0-RELEASE][admin@Ignis.brendhanhorne.com]/root: date Thu Nov 3 13:38:02 -05 2022
I have done that as suggested. I will let it run for a bit and see what the logs say. I thank you again for your help. It will be interesting because I am technically gmt -5 and I may have to do another restart. Which I will do later tonight.
Sincerely,
Brendhan -
@understudy said in Time date in logs not correct.:
I am technically gmt -5
Not if you use the POSIX time format, which FreeBSD/pfSense does.
https://docs.netgate.com/pfsense/en/latest/troubleshooting/time-zone.html#clock-does-not-use-the-expected-zone-offset -
I am going to do a reboot also just to be sure.
Brendhan
-
Okay, I did a reboot and checked the bios time. The bios time was off by two hours. It wasn't before so I am probably going to have to replace the cmos battery. As it stands right now it looks like the times for everything are correct. I am leaving it with posix time and making sure the ntpq -pn is good. I will check again in the morning to be sure and report back but initial reports look good.
[2.6.0-RELEASE][admin@Ignis.brendhanhorne.com]/root: date Thu Nov 3 17:15:46 -05 2022 [2.6.0-RELEASE][admin@Ignis.brendhanhorne.com]/root: ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== 2.pfsense.pool. .POOL. 16 p - 64 0 0.000 +0.000 0.000 0.north-america .POOL. 16 p - 64 0 0.000 +0.000 0.000 1.north-america .POOL. 16 p - 64 0 0.000 +0.000 0.000 2.north-america .POOL. 16 p - 64 0 0.000 +0.000 0.000 216.197.156.83 .PPS. 1 u 24 64 377 87.111 -358288 1.279 198.211.103.209 206.108.0.131 2 u 19 64 377 36.503 -358289 0.932 159.203.158.197 128.59.0.245 2 u 19 64 377 37.168 -358289 0.977 157.245.141.244 129.6.15.29 2 u 23 64 377 38.057 -358289 2.271 12.167.151.1 158.51.134.123 3 u 17 64 377 36.220 -358291 0.514 +209.115.181.110 206.108.0.131 2 u 37 64 7 88.227 -358289 0.135 *167.99.186.165 129.6.15.28 2 u 30 64 7 48.159 -358289 0.748 [2.6.0-RELEASE][admin@Ignis.brendhanhorne.com]/root: -
@understudy The BIOS being off by exactly a multiple of an hour is frustrating to figure out. Much more obvious if it is 27 minutes. :)
re: some services using other times, I actually posted a log of that in a completely unrelated redmine, https://redmine.pfsense.org/issues/13593. That log entry was:
system log (14:07 is UTC, 9:07 is US CDT):
Oct 25 14:07:44 check_reload_status 353 Syncing firewall Oct 25 14:07:44 php-fpm 69691 /pkg_mgr_install.php: Configuration Change: admin@ip (Local Database): Saved firmware branch setting. Oct 25 09:07:13 pkg-static 50845 pfSense-repo upgraded: 2.6.0_8 -> 2.7.0.a.20221025.0600 Oct 25 09:07:11 pkg-static 47503 pkg upgraded: 1.17.5_2 -> 1.18.4_1 Oct 25 14:07:02 check_reload_status 353 Syncing firewall Oct 25 14:07:01 php-fpm 69213 /pkg_mgr_install.php: Configuration Change: admin@ip (Local Database): Saved firmware branch setting.In that case it was the 5 hour time zone.
Not on pfSense, AFAIK, but I have set up Linux servers where if you change time zones some services don't pick it up until they restart.
