backup suddenly stopped working

beterelektro

Verified User
Joined
Dec 22, 2006
Messages
9
Location
Haarlem the Neterlands
Hi,

I have been using DirectAdmin for a couple of months now and I like it a lot!

One of the great features is the nice and easy backup system. But for some reason I suddenly can't make backups anymore :( (both reseller and user level).

Al seems to go well, and there are no error messages, but the backups never complete (no messages are sent). And the backup folders stay empty.

I tried to chmod the backup dirs (since that was the only thing I could think of) but that does not help.

Any ideas anyone?

Thanks!
 
Last edited:
Now suddenly some backups were performed "out of nothing". While I had not tried to create backups anymore for at least several days, I think finally my previous backup requests were executed.

Thinking the backup feature might have been repaired somehow I tried to backup again, and now I got this error message:
Error during Backup Creation

Details

Unable to open task queue for appending

Any idea what that means? And if it could be related?
 
The only thing I can think of that can cause that in normal operation would be a full disk.

Login through the shell:
Code:
$ df -h
Jeff
 
I have the same problem , before the backup's worked, but now it do nothing.
 
Thanks for the reply Jeff,

I don't think it's a full disk because after the last backup I removed the "old" backups and some of the more space consuming dirs and got the same error afterwards. Also I have had no problems adding files which took a lot more space than most of the zipped backups would take.

But I will try to get into the shell (forgot how to do that :o ) or ask someone to look at the disk usage for me.

New information: the "spontanious" backups were done by the host. He probably did that to test it for me and it worked. So maybe it's some user related issue? I am a total noob at this, so it's possible I messed up some user setting without realizing it would disable the backup feature.
 
Log into the shell and do:
Code:
# ls -al /usr/local/directadmin/data/task.queue
and post the output.

Jeff
 
-rw------- 1 diradmin diradmin 5741 Jan 10 22:40 /usr/local/directadmin/data/task.queue
 
I have no idea why it has so much in it.

Try deleting it (warning, if you do this nothing in it will run) and see if that fixes the server for the future.

Jeff
 
Originally posted by jlasman Log into the shell and do:
Code:
# ls -al /usr/local/directadmin/data/task.queue
and post the output.

Jeff

-rw------- 1 diradmin diradmin 229 Jan 13 12:31 /usr/local/directadmin/data/task.queue
Does this mean there are 229 pending tasks? Note that there should be no tasks as far as I know (other than a couple of backups added by me, that did not work out).

edit: After trying to execute one more backup it says:
-rw------- 1 diradmin diradmin 321 Jan 17 10:31 /usr/local/directadmin/data/tas k.queue

edit#2:
Another try to backup increases the number to 576 (no idea if this matters, just seems a bit strange to me)
 
Last edited:
It's generally unlikely that your host will be willing to delete the DA task queue. My suggestion was based on a misunderstanding that it's your server and that you have root access.

If it's not your server, then you should discuss the problem with your hosting company; ultimately it's their responsibility and only they have the access needed to figure it out and correct the problem.

Jeff
 
I thought the problem maybe was caused by something I had done wrong and/or was something I could easyly fix, or was a known bug or something.

Hopefully my host is able to fix it then (I already asked, and they are helpfull but ... ).

Thanks a lot anyway Jeff, and sorry for the confusion
 
Problem is you don't have any rights to anything that needs to be checked and/or changed unless it's your server.

I'm moving this thread to User-Level Difficulties

Jeff
 
Tell your host to make sure the crond service is running.

(Red Hat Servers)

Code:
/sbin/service crond start
 
[root@servidor1 tmp]# ls -al /usr/local/directadmin/data/task.queue
ls: /usr/local/directadmin/data/task.queue: No such file or directory

Hi guys, I do have root access, and I get this. Tried restart crond but says already running:

[root@servidor1 tmp]# /sbin/service crond start
Starting crond: cannot start crond: crond is already runnin[FAILED]

Tried stopping and starting, and get same result:
ls: /usr/local/directadmin/data/task.queue: No such file or directory

My user gets this error when he tries to setup backups:

Error during Backup Creation
Can't get lock on task queue

Any suggestions ?
 
Last edited:
Back
Top