[Solved]System Clock - Synced but still wrong time

[grayvee]

Well everything's fine except for this rather important thing. I've set my timezone "Asia/Manila", but still wrong time.

[thenktor]

Are you using NTP?
How much differs your time?

EDIT: Perhaps just the time in your panel is not updated. Run the command "date" and check the output.

[grayvee]

Problem solved. I went to System Services and turned off ntpd. Then synced again at the System Clock settings.

[thenktor]

It should work with ntp enabled, too.

[gapan]

Probably a UTC/local time setting problem.

[toothandnail]

I'm seeing something similar on my desktop machine. Since Salix is the only OS on it, I've got it set to UCT, and I've tried manually syncing it as well as just leaving the 'use ntp' box ticked. Its quite strange - its around 4 - 5 minutes slow all the time.....

Haven't had a real look at solving it yet. I might try building chrony and see if that works a bit better, but the small amount of difference is the puzzle.

Paul.

[thenktor]

When you are running ntpd please post the output of "ntpq -p" (executed as root).

[toothandnail]

When you are running ntpd please post the output of "ntpq -p" (executed as root).

Sorry for the slow reply. I've spent the last several days trying to get a Zentyal server working with two WAN links. Not much fun , and still not working....

Anyhow, the output is as below:

Code: Select all

root[fang]# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+153.16.4.137    192.5.41.40      2 u  882 1024  377  173.392   -4.326   0.035
*barricade.rack9 209.51.161.238   2 u  887 1024  377  127.728   14.797   0.247
+153.16.4.130    192.5.41.40      2 u  424 1024  377  177.679   -6.211   0.634  

I set the time manually, then let it sync. It now looks to be correct. Still no idea why it had that small error before.

Paul.

[thenktor]

Yep, output is fine.

[xMrIS]

Hi,

'new' to Salix and I just discovered too the time problem (system in localtime, OS shows +1 hr time).

I had to disable the ntpd update... needless to say its something I never had on any previous OS (linux or not) at the past.....