Clock problem

English Applications
1

Hi,

i have an Suse 10.2 64Bit running with Plesk on it.
Now i will update to a new Server with Suse 11.1.

But the old system has a clock problem so i can not backup.
The Plesk service and some other things are confused of the time thing.

If i type date in teh console i get this:

suse:~ # date
Tue Aug 11 09:17:18 CEST 2009
suse:~ # date
Tue Aug 11 10:13:22 CEST 2009
suse:~ # date
Tue Aug 11 09:17:22 CEST 2009
suse:~ # date
Tue Aug 11 10:13:24 CEST 2009
suse:~ # date
Tue Aug 11 09:17:23 CEST 2009
suse:~ # date
Tue Aug 11 10:13:25 CEST 2009
suse:~ # date
Tue Aug 11 09:17:24 CEST 2009
suse:~ # date
Tue Aug 11 10:13:25 CEST 2009
suse:~ # date
Tue Aug 11 09:17:24 CEST 2009
suse:~ # date
Tue Aug 11 10:13:25 CEST 2009
suse:~ # date

The time hops forward and backward again.
From some minutes to 1 and 2 houres.

Have someone an idear what goes wrong?

Hardware:
Tyan Serverboard
2x Xeon 3GhZ
4GB Ram
Suse Linux 10.2 64Bit

2

Have you tried setting up nntp and seeing if this fixes it?

3

The NTP port from the server to the net is closed.
So i cannot setup ntp service.

4

Steff B adjusted his/her AFDB on Tuesday 11 Aug 2009 08:36 to write:

>
> Hi,
>
> i have an Suse 10.2 64Bit running with Plesk on it.
> Now i will update to a new Server with Suse 11.1.
>
> But the old system has a clock problem so i can not backup.
> The Plesk service and some other things are confused of the time
> thing.
>

IIRC there is a prob with the clock on maybe 10.2 you have /usr or /home on
a separate partition.

Do you?

Let me see if I can find the error report and fix.

–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum

5

No i have not.
Only one partition.
Thank you for your help.

Hope that we can fix it.

6

baskitcaise adjusted his/her AFDB on Tuesday 11 Aug 2009 08:56 to write:

> Steff B adjusted his/her AFDB on Tuesday 11 Aug 2009 08:36 to write:
>
>>
>> Hi,
>>
>> i have an Suse 10.2 64Bit running with Plesk on it.
>> Now i will update to a new Server with Suse 11.1.
>>
>> But the old system has a clock problem so i can not backup.
>> The Plesk service and some other things are confused of the time
>> thing.
>>
>
> IIRC there is a prob with the clock on maybe 10.2 you have /usr or /home
> on a separate partition.
>
> Do you?
>
> Let me see if I can find the error report and fix.
>

I cannot find the prob that is was looking for but I do remember a lot of
people having trouble with the clock on 10.2.

Here was one page I found at random:;

http://forums.opensuse.org/archives/sf-archives/archives-install-
boot/334023-synchronize-clock-ntp-boot.html

Sorry mind the wrap there.

If you google for clock+10.2+suse

You will find all sorts of posts and attempts to fix it, ntp is the only was
I think.

Can you check your logs to see if you are getting seg faults when you
shutdown and boot concerning the hardware clock if so that post above might
help.

Sorry cannot help fully but am on my way out in 10 mins or so.

–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum

7

Also, if you are running as a server and not workstation, it’s important to have a reliable working clock so you need to set ntp to sync the clock. How often, depends on how reliable the motherbard clock is.

8

Sorry if you already fixed it. I read this thread flimsy because of the length. But if you need to sync your systems and can not use NTP to the outside world you can allways use NTP to one of your internal systems. Thus all systems on the LAN have at least the same time. It is enough to start ntp on all (via YaST) and let all apart from Server point to Server.