DA error.log keeps writing certain errors

Richard G

Richard G

Verified User
Joined
Jul 6, 2008
Messages
13,848
Location
Maastricht
I only have this on a VPS, not on servers.

In /var/log/directadmin/error.log I see these a lot:
2012:10:08-03:55:52: File ./data/admin/admin.usage has been written to after this process read it. Not going to overwrite it.
2012:10:08-03:55:52: File ./data/admin/reseller.list has been written to after this process read it. Not going to overwrite it.
2012:10:08-03:55:52: File ./data/admin/admin.list has been written to after this process read it. Not going to overwrite it.
2012:10:08-03:55:52: ConfigFile::writeFile(./data/admin/admin.allocation) : Timestamp from when it was read is different, overwriting anyway
2012:10:08-03:55:52: ConfigFile::writeFile(./data/admin/admin.conf) : Timestamp from when it was read is different, overwriting anyway
Click to expand...

Can this be fixed or do I just have to ignore it?
The timestamp on the vps is correct.
 
Make sure that not only the time but the timezone data are correct.

Jeff
 
I have a symlink made:
localtime -> /usr/share/zoneinfo/Europe/Amsterdam

So that should be oke.
I also have regular socket write errors in the DA error.log:
2012:10:09-10:33:56: Socket write error: Unknown error
2012:10:09-10:34:13: Socket write error: Unknown error
2012:10:09-10:34:20: Socket write error: Unknown error
 
Do you keep your time synced with ntp?

You might want to run a cronjob like this or use ntpd.

Code: 
#Sync network time
*/15 * * * * /usr/sbin/ntpdate -4 -u us.pool.ntp.org >/dev/null 2>&1
 
Thank you.
On this VPS I don't keep the time synced with ntp but that seems not needed either.
Every time when I login to the vps, the date and time is correct. I check it with my windows machine, so the clock is working fine.
 
That would be odd, because we did not do any backups yet. It's a newly installed VPS.
But I will see what happens in debug mode when the problem keeps appearing.

Thank you!
 
Oh I thought it was when you were doing backups. Maybe it happened when you added the user then. I would just ignore it unless you see it happening often.
 
No problem. Thank you for thinking about the problem.
I will monitor it and try to see if and when it happens again.
 
You must log in or register to reply here.
Back
Top