Whole Disk Backup stalls

[dialing_wand]

Hi,

I'm running PiaF 1.3 and I just installed (after carefully following the complete instructions) the "Whole Disk Backups" script.

The install went fine, but after rebooting and attempting to manually run the Cron script to test it out, the system powers away for about 30 minutes, creates an image in /backup then just sits there. The PBX works fine, I can send and receive calls, but it doesn't copy the ISO to either the USB drive or attempt to post it on the FTP I specified in the config file.

The Log file is empty:

=======================================================
disk-backup.cron - Begin Log  200810071329
Released on Date 042608 Version 2.2.1
=======================================================
=======================================================
Now starting mondo. This will be a very long log!
Creating CDR sized ISO images has been choosen
=======================================================
disk-backup.cron - Begin Log  200810071455
Released on Date 042608 Version 2.2.1
=======================================================
=======================================================
Now starting mondo. This will be a very long log!
Creating DVD sized ISO images has been choosen

I stopped the first one after an hour and a half, now it's been two hours and "top" shows nothing other than the normal PBX processes doing their thing. There has been no traffic to my FTP and nothing on the usb drive.

The log is also suspiciously empty.

 

[wardmundy]

Be sure you have the correct device name, usually sda1 or sdb1. Turn off all the storage options except the USB flash drive. Change the size of the ISOs to CD-size. Be sure your /mnt/usbmondo directory is empty when the flash drive is not mounted. Then try again.

Here's the little usbcheck.sh script we use to check our flash drive regularly:

#!/bin/bash
mount -t vfat /dev/sda1 /mnt/usbmondo
df /mnt/usbmondo
echo " "
ls -all /mnt/usbmondo
umount /mnt/usbmondo

 

[dialing_wand]

My configuration file.

#DISK-BACKUP.CONF
#This is the external configuration file used by /etc/cron.weekly/disk-backup.cron
# Each line must have a # in front of it unless it is used to provide data
#In other words NO BLANK LINES IN THIS FILE AT ALL!!!!
#
#
#
#***********************************************************************
#MASTER SWITCH
#This indicates to disk-backup.cron that this file has been configured!
#You must change it to CONFIGURED="1" for disk-backup.crion to run.
CONFIGURED="1"
#***********************************************************************
#
#***********************************************************************
#CONFIGURATION OPTIONS
#
#Do ftp backups 1=yes 0=no  Change as needed
CPFTP="1"
#
#
#Do usb flash drive backups 1=yes 0=no Change as needed
CPFLASH="1"
#
#
#Copy files to a remote SMB mount 1=yes 0=no Change as needed
CPSMB="0"
#
#
#Remove yesterdays log. 1=yes 0=no change as needed Default is to REMOVE previous days log.
REMLOGS="1"
#
#
#Archive Size
#Choose either DVD or CDR for the backup size. This will depend on what your PBX in a Flash has
#as a boot device. Choose the appropriate size. If you are backing up to USB I recommend
#the DVD as the size.  Default is CDR =670 mb ISO's  DVD=4200mb ISO's
BACKUPTYPE="DVD"
#
#
#This choice allows you to specify the USB file system to mount. Most 8gb USB keys
#have a FAT32 fs already installed, however there is a problem with the fs ID bit. I
#recommend you format the key with the information contained in manual
USBFS="vfat"
#
#
#Send log file via email 1=yes 0=no
#Change as needed Default is 1 and will send logs to the local root email account.
SENDLOG="0"
#
#
#Delete the iso files in /backup after copying to remote device "1" = yes "0" = no
DELBACKUPS="1"
#
#
#Excluded backup folders Most temp folders are not backed up however you can add extras
#here. The /backup must not be changed simply add the folders you DO NOT WANT backed up to the line
#with a space between /backup. for example EXCLUDEUDR="/backup /tmp"
EXCLUDEDIR="/backup"
#***********************************************************************
#
#
#***********************************************************************
#FTP INFORMATION
#
#This should be the user name on the remote ftp machine
USERNAME="ftp_user_was_here"
#
#This should be the remote ftp password.Change if needed
PASSWORD="my_password_was_here"
#
#this should be the remote directory you wish files to go
#into on the ftp server
#Change if needed
REMOTEDIRECTORY="/"
#
#this is the IP address or Fully Qualified Domain Name FQDN of the ftp server
#Change to where you are sending your backups
SERVER="ftp.myhost_was_here.ca"
#
#this is the local directory where files are located
#This must exist! 
DIRECTORY="/backup"
#***********************************************************************
#
#
#***********************************************************************
#USB INFORMATION
#
#USB Mount Point
#This can be modified if you understand how
USBMOUNTPOINT="/mnt/usbmondo"
#
#StickDeviceName
#This may have to be modified depending on what
#the OS assigns to your USB Flash Drive
USBDEVICENAME="/dev/sda1"
#***********************************************************************
#
#
#***********************************************************************
#SMB INFORMATION
#
#This must be an ip address ONLY Machine names are not acceptable
#THIS MUST BE CHANGED
SMBMACHINE="192.168.1.2"
#
#This is the name of the share on the remote machine
#THIS MUST BE CHANGED
SMBSHARE="sharename"
#
#This is the local mountpoint name and path
#this is created by the install-diskbackup.sh
#DO NOT CHANGE!
LOCALMOUNT="/mnt/smbmondo"
#
#This is the User name on the remote machine
#for example your username on the windows machine where you are copying the files to
#THIS MUST BE CHANGED
SMBUSER="user"
#
#This is your password on the remote machine
#For example your password that corresponds to the username on the remote
#windows machine you are copying files to.
#THIS MUST BE CHANGED
SMBPASS="pass"
#***********************************************************************

 

[dialing_wand]

I'm quite sure the device is not mounted, and, at the very least wouldn't I seen an error in the log?

I also formated the USB flash drive as per the Whole Disk Backups manual.

 

[dialing_wand]

Just checked (to be sure) and there are no issues, drive is empty, properly formatted and waiting for an image!

 

[dialing_wand]

New development:

When I tried to run the /etc/cron.weekly/disk-backup.cron job again (yet again)... and it stalled, I "Ctl-X"ed at the CLI only to have the system spit out:

KERBEROS_V4 rejected as an authentication type

Subsequently however, the system started uploading the images to the ftp site specified in the config file.

So it's definitely waiting indefinitely for something... I just don't know what.

 

[darmock]

The Kerberos message can safely be ignored. So what does the log say in /var/log? Don't post the whole flipping thing please. Just the last few lines which should give you a clue to what the problem is. If you look at it you will find reference to the copying procedure

Generally this works on most systems but sometimes there are hardware related problems.

Tom

 

[dialing_wand]

Here is where the problem is:

Writing boot+data floppy images to disk
No Imgs
---promptpopup---1--- No regular Boot+data floppies were created due of space constraints. However,
 you can burn /var/cache/mindi/mondorescue.iso to a CD and boot from that.
---promptpopup---Q--- [OK] ---
--> SIGHUP signal received from OS

That SIGHUP is the Ctrl-X I manually did. Basically it is waiting for some input when it says "--promtpopup--Q--".

The really odd thing is that I have mondorescue installed on a DMS server running ubuntu and it has the same prompt after the same message where it waits for user input.

I imagine this is a pretty big issue since the cron job will just wait there for input that's never coming. Also because there is no verbose output to the screen during the test, I don't know when I need to "Ctrl-X" or send a SIGHUP unless I load up the FreePBX interface (or run 'top' from another SSH session) and see if the cpu is working away.

 

[krzykat]

You know, I don't remember what I did but I had a similar issue when I executed the command by hand. Stayed there forever. It would create the 2 mondorescue files, but not the emergencyboot.iso file. But somehow when I had it run by the CRON job it worked properly ??? So since it did end up doing what I wanted I didn't pursue why the manual running failed to complete.

 

[dialing_wand]

Thanks krzykat.

Some annecdotal research on Google has led me to believe this is the case - so I'm going to cross my fingers and see if it works as it should this sunday!