Couple of problems ok maybe more then a couple..

Incognito

Verified User
Joined
Jan 17, 2010
Messages
28
Hi all i have a VPS with directadmin installed on...

in log viewer i see lots errors ill lets them..

Directadmin Error Log:
010:01:17-14:38:34: ConfigFile::writeFile() : Timestamp from when it was read is different, overwriting anyway

Directadmin Secuirty Log:
Unable to read log

Apache Error Log:
Sun Jan 17 04:02:06 2010] [warn] RSA server certificate CommonName (CN) `localhost' does NOT match server name!?
[Sun Jan 17 04:02:06 2010] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!!

Apache Suexec Log:
Unable to read log

System Messages:
Jan 17 13:37:44 server named[4847]: client 204.194.239.11#53902: query (cache) 'irc.awesome-chat.net/A/IN' denied
Jan 17 13:37:44 server named[4847]: client 204.194.239.11#34790: query (cache) 'irc.awesome-chat.net/A/IN' denied
Jan 17 13:37:44 server named[4847]: client 204.194.239.11#61914: query (cache) 'irc.awesome-chat.net/A/IN' denied
Jan 17 13:37:44 server named[4847]: client 204.194.239.11#18903: query (cache) 'irc.awesome-chat.net/A/IN' denied
Jan 17 14:42:14 server ntpd[2275]: no servers reachable
Jan 17 14:44:16 server ntpd[2275]: synchronized to 66.250.45.2, stratum 2
Jan 17 14:48:33 server ntpd[2275]: no servers reachable

Anyone know how to sort these errors do i dont get them any more

Thanks
 
I don't know about the Directadmin Error log, but the others are:

- Directadmin Security log: path to log must be wrong

- Apache Error log, first warning: self-signed certificate should be recreated with a CN containing the server's hostname, but it's a warning: it works anyway
- second warning: it is just a warning about having multiple name-based virtualhosts with the same SSL certificate, it's the default config and it's ok

- Apache Suexec log: path to log must be wrong

- System Messages, named: recursive queries failure, this is not a problem on your side but on awesome-chat.net's side
- ntpd: check your ntpd conf, there must be some unstable pool addresses; use 1.pool.ntp.org 2.pool.ntp.org 3.pool.ntp.org 4.pool.ntp.org (or the equivalent for your country, like 1-4.us.pool.ntp.org), then check with "ntpq -p" that all of the servers have a similar delay and there is a reference (*) server after a few minutes. Should be something like that:
Code:
$ ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+ntp0.nl.uu.net  .PPS.            1 u 1009 1024  377    2.844   -1.272   0.142
*ntp1.nl.uu.net  .PPS.            1 u 1003 1024  377    1.337   -1.284   0.142
+chime1.surfnet. .GPS.            1 u  220 1024  377    1.563   -1.188   0.108
-chime2.surfnet. .GPS.            1 u  501 1024  277    4.888   -1.159   0.009
 
Last edited:
The DirectAdmin error log error may be caused by the server not keeping correct date/time information.

Jeff
 
First check to see if the clock is off, and if so, reset it. Then check it again after some time has passed.

If the time drifts again, then it could be hardware problem. If that's the case then install a way to correct the time, to run every hour or so.

Jeff
 
Back
Top