Re: Problems getting client to work.
+ John R. Jackson <[EMAIL PROTECTED]> [07.04.02 20:24]: > >Of course... I've tried 2.4.2p2 too, with no luck. So I updated to the > >"bleeding-edge" version. > > OK. Just wanted to make sure you understood what you were running. I've downgraded to 2.4.2p2 again, since the beta did not work either. Another thing I did was touching /home/balu/.amanda.exclude, selfcheck ignored it, but the admin told me that it was listed as an ERROR in the amcheck mail... I've also redone the config, checked the amanda-user (who had /bin/false as shell for whatever reason) and all rights (I didn't have to change them though). And now it suddenly works. :-) Thanks for you suggestions Balu
Re: Problems getting client to work.
>Of course... I've tried 2.4.2p2 too, with no luck. So I updated to the >"bleeding-edge" version. OK. Just wanted to make sure you understood what you were running. >As far as I can see the client is happy, but the administrator of the >backup-server is not. He told me that there has to be a problem with my >client ... As before, there is zero information here. "has to be a problem" is useless without knowing what error messages or other indications there are that a problem exists. >I've asked the admin of the server to send me the amcheck-output. That will help a lot. >> What's in the runtar*.debug file? > >There is no such file. That's very odd. But without any other info from the server admin it's hard to tell if it's important. >BTW - does amanda store the archive-files on the client before sending >them to the server ... No. The data goes straight onto the wire back to the server. > Balu John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Problems getting client to work.
+ John R. Jackson <[EMAIL PROTECTED]> [07.04.02 19:13]:
> >I've got a|some problem|s ;) getting amanda 2.4.3b3 running as client.
>
> First, you do understand that the 'b' in that name means you're running
> beta test code, and as such should be prepared to help debug any problems,
> right?
Of course... I've tried 2.4.2p2 too, with no luck. So I updated to the
"bleeding-edge" version.
>
> >One problem is that I don't know how the backup-server is set up, so I
> >wonder if anyone here can see sthg in the logs below.
>
> You didn't say why you think you're having a problem. What makes you
> think this client is not happy?
As far as I can see the client is happy, but the administrator of the
backup-server is not. He told me that there has to be a problem with my
client, because the same setup works with other machines. We have tried
some scenarios with no result and the only idea left was asking here.
> The only thing I see that's odd is that the sendsize log does not appear
> to have completed. Is anything still running as your Amanda user?
There are no processes running as amanda anymore, nor any tars or
similar.
> What's in the runtar*.debug file?
There is no such file.
> What version of GNU tar are you using (gtar --version)?
# tar --version
tar (GNU tar) 1.13.17
> How big is /home/balu? How many files (e.g. from "df")?
du /home/balu/ -s
140 /home/balu
It is a very small dir, just to make sure it is not the filesize-limit
or the like that prevents the backup from working.
BTW - does amanda store the archive-files on the client before sending
them to the server (then I'd have to watch for the 2GB-limit of my
2.2-kernel)? Or does it transfer the archive to the server "on the fly"?
> >... The homedir contains the following files:
> >
> >-rw-r--r-- 1 root root 21 Mar 1 16:39 .amandahosts
>
> This would not affect whatever problem you're having, but .amandahosts
> should be owned by your Amanda user ("amanda") and mode 0400 or 0600.
Fixed that.
I've asked the admin of the server to send me the amcheck-output.
Balu
Re: Problems getting client to work.
>I've got a|some problem|s ;) getting amanda 2.4.3b3 running as client.
First, you do understand that the 'b' in that name means you're running
beta test code, and as such should be prepared to help debug any problems,
right?
>One problem is that I don't know how the backup-server is set up, so I
>wonder if anyone here can see sthg in the logs below.
You didn't say why you think you're having a problem. What makes you
think this client is not happy?
The only thing I see that's odd is that the sendsize log does not appear
to have completed. Is anything still running as your Amanda user?
What's in the runtar*.debug file? What version of GNU tar are you
using (gtar --version)? How big is /home/balu? How many files (e.g.
from "df")?
>... The homedir contains the following files:
>
>-rw-r--r-- 1 root root 21 Mar 1 16:39 .amandahosts
This would not affect whatever problem you're having, but .amandahosts
should be owned by your Amanda user ("amanda") and mode 0400 or 0600.
>Balu
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Problems getting client to work.
On Wed, 3 Apr 2002 at 8:23pm, Thomas -Balu- Walter wrote > > Err, it would help if you told us what the problem was, i.e. send us the > > amanda email report that notes the problem or the problematic amcheck > > output. > > The problem is, that I don't get an email report or the amcheck > output... As stated above, I only set up the client. The backup-server > itself is not under my control - the admin of that server told me that > it has to be something with my client-setup. And I wanted to see if you > can see any problem on my side in those logs. Have him or her send you (or us) the output of amcheck. You really can't debug this without being able to run those tools. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Problems getting client to work.
+ Joshua Baker-LePain <[EMAIL PROTECTED]> [03.04.02 18:51]: > On Wed, 3 Apr 2002 at 6:28pm, Thomas -Balu- Walter wrote > > > I've got a|some problem|s ;) getting amanda 2.4.3b3 running as client. > > One problem is that I don't know how the backup-server is set up, so I > > wonder if anyone here can see sthg in the logs below. > *snip* > > Err, it would help if you told us what the problem was, i.e. send us the > amanda email report that notes the problem or the problematic amcheck > output. The problem is, that I don't get an email report or the amcheck output... As stated above, I only set up the client. The backup-server itself is not under my control - the admin of that server told me that it has to be something with my client-setup. And I wanted to see if you can see any problem on my side in those logs. > Those logs looked fine, except for the missing exclude list. Ok, thanks. So I'll have to kick the other admin to get it working ;-) Balu -- "Linux is like a fractal: No matter how deep you go, there's always more!" [Casey Bralla, 24.01.2001 in [EMAIL PROTECTED]]
Re: Problems getting client to work.
On Wed, 3 Apr 2002 at 6:28pm, Thomas -Balu- Walter wrote > I've got a|some problem|s ;) getting amanda 2.4.3b3 running as client. > One problem is that I don't know how the backup-server is set up, so I > wonder if anyone here can see sthg in the logs below. *snip* Err, it would help if you told us what the problem was, i.e. send us the amanda email report that notes the problem or the problematic amcheck output. Those logs looked fine, except for the missing exclude list. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Problems getting client to work.
Hi all, I've got a|some problem|s ;) getting amanda 2.4.3b3 running as client. One problem is that I don't know how the backup-server is set up, so I wonder if anyone here can see sthg in the logs below. The client is running on a SuSE-Linux 7.3 - self compiled using ./configure --with-user=amanda --with-group=disk Compiling and installing didn't give me an error. /var/lib/amanda which is the amanda-user homedir is owned by amanda:disk and amanda has the right to rwx there. Amanda itself got a bash as shell. The homedir contains the following files: -rw-r--r-- 1 root root 21 Mar 1 16:39 .amandahosts drwxr-xr-x 2 amanda disk 4096 Mar 12 11:00 gnutar-lists drwxr-xr-x 2 amanda disk 4096 Apr 28 2000 index Both dirs are empty, .amandahosts contains "backupserver.dom.ain backup" Can you see a problem in the following logs? Or point me into a direction where to have a look? Regards from Muenster/Germany Balu PS: please reply personally too, as I am not subscribed to this list. amandad.20020403005137.debug amandad: debug 1 pid 30345 ruid 37 euid 37 start time Wed Apr 3 00:51:37 2002 amandad: version 2.4.3b3 amandad: build: VERSION="Amanda-2.4.3b3" amandad:BUILT_DATE="Tue Mar 12 16:08:21 MET 2002" amandad:BUILT_MACH="Linux RoadRunner 2.2.14 #1 Mon Mar 13 10:51:48 GMT 2000 i686 unknown" amandad:CC="gcc" amandad:CONFIGURE_COMMAND="'./configure' '--with-user=amanda' '--with-group=disk'" amandad: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" amandad:libexecdir="/usr/local/libexec" mandir="/usr/local/man" amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" amandad:CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/" amandad:RDEV_PREFIX="/dev/" SAMBA_CLIENT="/usr/bin/smbclient" amandad:GNUTAR="/bin/tar" COMPRESS_PATH="/usr/bin/gzip" amandad:UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/Mail" amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="RoadRunner" DEFAULT_CONFIG="DailySet1" amandad:DEFAULT_TAPE_SERVER="RoadRunner" amandad:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" got packet: Amanda 2.4 REQ HANDLE 007-60610608 SEQ 1017787508 SECURITY USER backup SERVICE sendsize OPTIONS maxdumps=1;hostname=123.123.123.123; GNUTAR /home/balu 0 1970:1:1:0:0:0 -1 exclude-list=.amanda.exclude sending ack: Amanda 2.4 ACK HANDLE 007-60610608 SEQ 1017787508 bsd security: remote host backupserver.dom.ain user backup local user amanda amandahosts security check passed amandad: running service "/usr/local/libexec/sendsize" amandad: sending REP packet: Amanda 2.4 REP HANDLE 007-60610608 SEQ 1017787508 OPTIONS maxdumps=1; amandad: got packet: Amanda 2.4 ACK HANDLE 007-60610608 SEQ 1017787508 amandad: pid 30345 finish time Wed Apr 3 00:51:37 2002 amandad.20020403005137.debug sendsize.20020403005137.debug sendsize: debug 1 pid 30346 ruid 37 euid 37 start time Wed Apr 3 00:51:37 2002 /usr/local/libexec/sendsize: version 2.4.3b3 sendsize: calculating for amname '/home/balu', dirname '/home/balu' sendsize: getting size via gnutar for /home/balu level 0 sendsize.20020403005137.debug sendsize._home_balu.20020403005137.exclude is empty additionally there is a selfcheck-file selfcheck.20020403160640.debug selfcheck: debug 1 pid 2338 ruid 37 euid 37 start time Wed Apr 3 16:06:40 2002 /usr/local/libexec/selfcheck: version 2.4.3b3 selfcheck: exclude list file "/home/balu/.amanda.exclude" does not exist, ignoring selfcheck: checking disk /home/balu selfcheck: device /home/balu selfcheck: OK selfcheck: pid 2338 finish time Wed Apr 3 16:06:40 2002 selfcheck.20020403160640.debug -- "Wipe Info uses hexadecimal values to wipe files. This provides more security than wiping with decimal values." -- Norton SystemWorks 2002 Professional Edition User's Guide
