Re: Problem using HDUP

Miek,
A very Happy New Year to you as well.
Hope you had a good one.

Thanks for the 
suggestion.
I have been looking into it a bit further, and have a much clearer idea of where 
the problem lies.   The problem is related to access priviledges on the remote machine.   
Let me 
explain....

Say I configured on the remote machine a backup directory 
of:
/home/users/myuser

By adding a few printfs to the code I found that HDUP effectively 
performs the following mkdir commands on the remote machine:
mkdir /home
mkdir 
/home/users
mkdir /home/users/myuser

The problem is the ownership of the "home" 
directory, which is root:root with no write access to this directory for normal 
users.
Hence a "mkdir /home" command results in an "Permission denied" error.   I think HDUP 
is looking for an "Already exists" error, which is why it is declaring a fatal error at
that 
point.

My workaround for now is to ensure that I always log onto the remote machine as root, 
which keeps hdup happy.  

With regard to the date dependency, that was a red herring.
I 
trawled through the log and found that daily and weekly were clashing towards the end of
the 
month which resulted in a separate error.   Modifications to my crontab to space out the
daily 
and weekly processes should sort this one out.

Best regards,

Nigel


> [On 31 Dec, 
@21:06, Nigel wrote in "[hdup-user] Problem using HDUP ..."]
> > Miek,
> > I wonder if you can 
help me. 
> > I have been using your excellent utility for a couple of months now, but I
> > am 
having a few problems with the remote backup.
> > Sometimes it works, and sometimes it does 
not.
> > It seems to be date dependant (usually starts failing 23 days into the
> > monthly 
backup cycle).
> 
> very strange indeed, I assume that on the 23rd only a dialy backup is 
made. So
> there is no clash of a weekly and a daily?
> 
> > When a monthly backup is run on the 
1st of the month, the problem goes away.
> > 
> > I was running version 1.6.18 up to today, when 
I upgraded to 1.6.23.
> > However, this does not seem to cure my problem.
> > 
> > When a remote 
backup fails, I get the following message:
> > 
> > 	/usr/local/sbin/hdup: sslserver: 
STARTING BACKUP.
> > 	/bin/tar: Removing leading `/' from member names
> > 
	/usr/local/sbin/hdup: sslserver: STARTING BACKUP.
> > 	/usr/local/sbin/hdup: 
FATAL: Could not create directory: /home.
> > 
> > 	/usr/local/sbin/hdup: WARNING: 
SIGPIPE received, cleaning up!
> > 	/usr/local/sbin/hdup: WARNING: AN ERROR OCCURED!
> 
> 
> > 	Hdup version.:  1.6.23
> > 
> > 	Host.........:  sslserver
> > 	Date.........:  31-12-
2003
> > 	Scheme.......:  weekly
> > 	Archive......:  sslserver.31-12-
2003.weekly.tar.gz
> > 	Encryption...:  yes (rijndael-192, 
/usr/backups/system/hdup.key)
> > 
> > 	                AN ERROR OCCURED!
> > 	                NOTHING WAS DONE!
> > 
> > I 
don't really understand why it is attempting to create a directory of
> > "/home".
> > 
> > 
The config of my local host is as follows:
> > 	[global]
> > 	archive dir = 
/usr/backups/system
> > 
> > 	[sslserver]
> > 	dir = /var/cvs, /var/jtime, /var/www, 
/var/users, /etc,
> > /var/spool/mail
> > 	mcrypt = /usr/local/bin/mcrypt
> > 
	algorithm = rijndael-192
> > 	key = /usr/backups/system/hdup.key
> > 	proto = 
/usr/bin/ssh
> > 	proto option = -1 -i /home/nigel/.ssh/identity
> > 	remote hdup = 
/usr/local/sbin/hdup
> > 	remote hdup option = -c 
/home/groups/serpentine/backup/hdup.conf
> > 
> > The config file of the remote host 
is:
> > 	[global]
> > 	archive dir = /home/groups/serpentine/backup
> > 
> > 
	[sslserver]
> > 	allow remote = yes
> > 
> > Any ideas of what I can do to resolve this 
problem?
> 
> looks all fine to me. You could look in the Makefile hdup16/src/
> and change 
these lines:
> 
> # Uncomment these for debugging output
> #DEBUG=-DDEBUG
> #STRIP=
> 
> 
Maybe that can shed some light on this problem,
> 
> grtz Miek