The graph does not display immediately
-
It looks like the graphing that is done client side is initially failing as it's trying to show a few minutes but there is actually a 9hr offset there.
Set the timezone correctly in System > General Setup. Set at least one ntp server there it can connect to.
Steve
-
'Timezone' Asia / Seoul
Setting it to 'TimeServer' Korea NTP server does not change anything.
Pfsense Tue Jan 28 09:17:15 KST 2020
Korea Time Tue Jan 28 00:15:10 KST 2020 -
It can take a while to sync to NTP when the time is that far out.
You can set the time and date manually using the date command. That should get it close enough to sync quicker using NTP.
Steve
-
Maybe it's my server computer problem.
I'll check and comment on this afternoon... -
Lets forget the timezone thing for a bit.. your time still looks to be off if that those are your pfsense and you client your viewing the web gui from... Even when in different time zones your minutes should be the same.. you have a 17:15 for minutes:seconds and 15:10 for minutes:seconds - which is right about the time your seeing in delay of info right, couple of minutes.
-
Right the graph is mostly client side generated right? I will admit to not being all that sure on that!
It starts out with a 9hr time difference in the data so you see almost nothing until it has enough data start scrolling and drops that first data point.
Seems almost certain to be relate to the client/server time difference there. More likely the server.
Steve
-
Is it something you don't have to care about?
-
devices can be in different timezones... And still be the same time... UTC vs CST for example... Doesn't matter - the problem is your times are off more than just the timezone difference!
-
-
Well make sure you devices times line up.. Be it they are in different timezones or not.. The minutes:seconds should be the same... Hours would just be off by the different timezones. You shouldn't have to wait couple of minutes for graphs to populate.
-
Yes, if the time is set correctly on both devices this will not be a problem. It looks like the pfSense end is ~9hrs out currently.
Steve
-
It looks like my server computer problem.
If you install it on another server computer, the time is just right and the graph is displayed immediately.
Thank you for your help.
-
Well correct the time... Not sure why this thread is still going on?
-
In fact, not only this but there are other problems as well, so I think I need to replace the server computer...
-
@NullLouting Just throwing this out there, but is the BIOS battery bad?
-
I don't know.....
-
Time being off would not a be a reason to replace it ;) Unless its specs no longer meet your needs, just fix whatever other problems it is having... But accurate time should take you like 10 seconds to fix, either set it by hand or point it to time source (ntp) or if your MS AD shop, make sure your DC are showing correct time and syncing with valid source. And all your member machines should be accurate..
-
@johnpoz
Thank you -
pfsense can be the ntp source for your whole network.. Are your devices doing that? What are your machines pointing to for time? Clearly something is not right if off by minutes.. And I don't really get why devices in the same location would be in different timezones?
The times you posted are both listed as KST... So the times should be the same... Not 9 hours and couple of minutes off..
What are you devices and pfsense using for time? Does your pfsense NTP status show its in sync - is it correct?
If pfsense time is correct?
-
@johnpoz
Another server computer was tested at my home.NTP information of the server computer that had the problem.
-
Computers in the same timezone KST would and should show the exact same time... Plus or minus a second or 2 at most... All of the computers in my home and also devices are only off by milliseconds from each other - because they all sync to same time source. Which as you can see above is currently showing being off by 0.001395 seconds..
-
Well yeah.. That is not able to talk to that, see the 0 reach!! Fix it!
that ntp server is clearly reachable
server 210.98.16.100, stratum 2, offset 0.009085, delay 0.22990 28 Jan 08:34:51 ntpdate[10360]: adjust time server 210.98.16.100 offset 0.009085 sec -
@johnpoz
Anyway, the server computer had a problem and had to change to another server computer.
-
What server computer? The one running pfsense or the one you using to access pfsense web gui? That pfsense time is not going to be correct.. Since its not currently able to talk to what you set for its ntp source.
