backup problemSubmitted by elad on Thu, 11/29/2007 - 5:53am.Hi, i am using the 1.02 jumpbox version when i tried to login to the admin on the jumpbox by web i get an error meesage : |
SearchJumpBox Open Collections |
backup problemSubmitted by elad on Thu, 11/29/2007 - 5:53am.Hi, i am using the 1.02 jumpbox version when i tried to login to the admin on the jumpbox by web i get an error meesage : |
SearchJumpBox Open Collections |
Backup Problem
I had exactly the same problem, my backups use to work ok a month ago, i only just noticed that any new backups created are 0kb and have nothing in them, I tried logging in and running the backup cron script manually (/jumpbox/bin/run_backup.rb) and it reported errors mounting the network drive. (I can see the network drive ok). After rebooting the virtual machine it all worked ok.
Backup Problem
Did you get the bad gateway error too?
Austin
Backup Problem still there.
I have the same probem again. I don't think that it worked ok last time either. I could log in and the gateway problem went away (after rebooting the vm) but i still can't backup onto another server.
Whenever I try to back it up from the admin login over the web interface it just sits there with the please wait screen; and whenever i do it from the console (last time i run the backup script not as su, my mistake).
By running
sudo ruby /jumpbox/bin/run_backup.rb -- does lots of stuff and creates lots of tmp.* directories. The console outputs the following (copied by hand hopefully no mistakes):
...
...
* Dumped revision 301
* Dumped revision 202
Hotcopying /var/data/projects/trac/project to /tmp/trac-dump/tracdump ... Hotcopy done
tar : Removing leading `/' from member names
tar : Removing leading `/' from member names
jumpbox/bin/../application_portal/privileged_scripts/ubuntu/lib/backup.rb:350 in ``': Bad file descriptor - mount (Errno::EBADF)
from /jumpbox/bin/../application_portal/privileged_scripts/ubuntu/lib/backup.rb:350 in `unmount'
from /jumpbox/bin/run_backup.rb:111
Manual Fix
To manually do a backup you can do the following process:
mount /data/backup
cd /data/backup
mkdir my_backupdir
cd my_backupdir
sudo tar -cf backupfile.tar /data/databases /data/projects
This seems to work ok for me. (Note that this doesn't do the correct backup process of doing a hot copy of the svn repositry)
Manual Fix
One needs to be careful manually doing things the JumpBox already does. Various earlier releases may not gracefully handle certain situations.
Austin
Backup Problem still there.
Is it because I am running low on hdd space? Using du i find that
/var = 316MB and
/usr = 186MB
is this ok?
Backup Problem still there.
Try the command:
df -h
also, what version of the trac JumpBox are you using?
Austin
Backup Problem still there.
Yes that was using the du -h option. Could the size be the problem?
trac 1.0.2
Backup Problem still there.
Can you send an email to support@jumpbox.com and go through and create an account and I will help you through there. You are probably encountering a known bug that I have fixed before. In that mail include the output of "df -h" ... thats an f no a u.
Austin
backup problem
I have sent you an email to the address listed in your profile regarding your post.
i am backing up to smb on a
i am backing up to smb on a windows 2003 sp2 server
What type of backup are you trying to use?
Are you backing up to a Windows share (SMB) or to NFS? And if its a Windows share, what type of machine is that share running on?
Austin