Daily remote scheduled back up job resulting in server crash

blackrose

New member
Joined
Jun 3, 2013
Messages
4
We've recently transfered our server to a new dedicated host. For the first few days everything was up and running and looking good, until suddenly our server crashed 2 days in a row right around the same time. After some investigating we found that the server crashed a couple of minutes after our daily remote Admin Backup Transfer had started. We also have a daily local and a weekly remote Admin Backup Transfer running, but these seemed to be running just fine.

The only logged error around these times was this one:

"/bin/chmod: failed to get attributes of `/usr/local/directadmin/data/task.queue.da': No such file or directory"

After searching these forums, this error implied that it could be a permission error and that we had to make sure the that "/usr/local/directadmin/data" was chowned to diradmin:diradmin. But again the day after we reset the permissions, the server still crashed around the same time.

So we completely removed the Backup task and re-entered it on a different time, and we haven't had a single crash since (this was about a week ago). The question now is there any logical reasoning for it to work now, or could there still be something wrong on the server?

Your help and suggestions are highly appreciated!
 
If the server crashes then you probably have bad hardware.

Perhaps "crashes" is a bit too harsh of a word, what I meant is that the server needed a reboot after starting the daily back up job.
This doesn't indicate bad hardware, does it?
 
Why did you think you had to reboot it?

Can you get into ssh when the backup runs?

It could be alot of things. disc i/o, memory, cpu, ... etc

Is your server a vps server or a dedicated server? What are the hardware specs?

If you can get into ssh when a backup runs you should check commands to see what is going on.

Code:
top

Code:
ps xuawww
 
Why did you think you had to reboot it?

Can you get into ssh when the backup runs?

It could be alot of things. disc i/o, memory, cpu, ... etc

Is your server a vps server or a dedicated server? What are the hardware specs?

If you can get into ssh when a backup runs you should check commands to see what is going on.

Code:
top

Code:
ps xuawww

Our programmer isn't available 24/7 so I couldn't first check matters with him.
At the first crash I didn't know what was going on (site was offline), so I called our datacenter. They rebooted it for me at that point.
Second crash, I rebooted it myself (I learned after the first crash we had a remote power switch available).

Server is a dedicated server.

I'll check with our programmer about getting into SSH and verifying the hardware specs. Get back to you on this.
 
Why did you think you had to reboot it?

Can you get into ssh when the backup runs?

It could be alot of things. disc i/o, memory, cpu, ... etc

Is your server a vps server or a dedicated server? What are the hardware specs?

If you can get into ssh when a backup runs you should check commands to see what is going on.

Code:
top

Code:
ps xuawww

SSH is available during a backup, and everything seems to be running as it should. The server is a dedicated server with the following specs:

Processor: AMD Phenom(tm) II X6 1090T Processor
Processor Speed: 3214.457 Mhz
Total Memory: 15810792 kB
Hard Disk: 2 TB (97% free disk space)
 
Back
Top