System Time and DirectAdmin Issues

[cryptodan]

What all do I need to do in order to repair the damage done by having the wrong system date?

I am unable to access directadmin via web gui, and other services are not working as well.

Any help will be greatly appreciated.

 

[scs]

What all do I need to do in order to repair the damage done by having the wrong system date?

I am unable to access directadmin via web gui, and other services are not working as well.

Any help will be greatly appreciated.

I hope I understand your problem.

You should use an SSH client (PuTTY). In the file

/etc/default/ntpdate

you will see, what kind of servers use the ntp. For example: 0.debian.pool.ntp.org
Than you give the command:

ntpdate 0.debian.pool.ntp.org

(Of course with your server.)

With this I could setup the server time.


Update: If necessary, restart the ntpdate. Command:

/etc/init.d/ntpdate restart

 

[cryptodan]

Well due to the CMOS battery running low the server was rebooted/moved to another area in the office, and well when it booted up it defaulted to August 15th 2005 so a lot of files and pid's are messed up. I got mail working, but the rest of DirectAdmin is dead. I cannot access it al via webgui.

 

[scs]

I cannot access it al via webgui.

Perhaps I misunderstood your problem. I hope so not.
PuTTY doesn't need webgui. It's an SSH client.
Or have you the server near you (in the office)?

 

[cryptodan]

I can use SSH just fine thats how I fixed the daemons and the pids to get mail working.

 

[scs]

I can use SSH just fine thats how I fixed the daemons and the pids to get mail working.

I suggest to try the ntpdate (see above).

 

[cryptodan]

I suggest to try the ntpdate (see above).

I already did that, and that does not affect the time stamp of files located on the server itself.

 

[scs]

I already did that, and that does not affect the time stamp of files located on the server itself.

Sorry, I've got no more idea. Perhaps somebody else.