Re: Amanda must be run as user amandabackup when using bsdtcp authentication
On Tuesday 19 May 2009, Abilio Carvalho wrote: >the prefix with no argument is how the config.log interprets >prefix='', which I did to install amanda in the default directories >rather than inside a specific subdir. Again, like frank's attempt I >have another machine with the same config options and that one works >fine. I'll take your word for that. Thanks for the reply to clarify. I would assume that would equal default "/usr/local" if the option wasn't even used. Since I build from tarballs here, running the lastest snapshot, I always spec the dir by using the same build script that I've used for years. #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` != 'amanda' ]; then echo echo "!! Warning !!!" echo "Amanda needs to be configured and built by the" echo "user amanda, but must be installed by user root." echo exit 1 fi make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-gnu-ld \ --prefix=/usr/local \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=coyote \ --with-bsdtcp-security --with-amandahosts \ --with-configdir=/usr/local/etc/amanda \ --with-config=Daily \ --with-gnutar=/bin/tar echo "sleeping 5 seconds for reading configures warnings" echo "a make as amanda will continue after..." sleep 5 make - I recently wrapped that up in a new script that does it all with one invocation, but the ./configure subscript stanza abover hasn't changed since Feb 10th, when a drive failed and I had to reinstall F10 and recover. I guess amrecover didn't preserve the date. :( However that script above hasn't been edited for years. I believe the last time was when I switched to bsdauth. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) You know, Callahan's is a peaceable bar, but if you ask that dog what his favorite formatter is, and he says "roff! roff!", well, I'll just have to...
Re: Amanda must be run as user amandabackup when using bsdtcp authentication
Thanks those were all things I'd tried already. I've managed to fix it though. For some reason, completely purging the service from everywhere and recreating it from the exact same manifest did the trick, where before that I'd tried changing the user parameter on the service without destroying it, without success. Thanks everyone for the help Abilio On May 19, 2009, at 9:28 PM, Deb Baddorf wrote: > At 3:01 PM +0200 5/19/09, Abilio Carvalho wrote: >> owner is amandabackup:disk >> >> I can log in to the account just fine, I don't think any more >> logging is possible though I'll check. I checked the manifest for >> the service and it confirms that it is SUPPOSED to start as >> amandabackup. >> >> If I do what you say, and log into amandabackup and run that, I get >> the following on /tmp/amanda/amandad/amandad.TIMESTAMP.debug: >> >> 1242737635.958239: amandad: pid 9504 ruid 6028 euid 6028 version >> 2.6.1: start at Tue May 19 14:53:55 2009 >> 1242737635.989035: amandad: security_getdriver(name=bsdtcp) returns >> ff31c788 >> 1242737635.992943: amandad: version 2.6.1 >> 1242737635.992955: amandad: build: VERSION="Amanda-2.6.1" >> 1242737635.992961: amandad:BUILT_DATE="Mon May 18 >> 12:33:06 CEST 2009" >> 1242737635.992967: amandad:BUILT_MACH="sparc-sun- >> solaris2.10" BUILT_REV="1609" >> 1242737635.992973: amandad:BUILT_BRANCH="amanda-261" >> CC="/ >> opt/SUNWspro/bin/cc" >> 1242737635.992979: amandad: paths: bindir="/bin" sbindir="/ >> sbin" libexecdir="/libexec" >> 1242737635.992984: amandad:amlibexecdir="/libexec/ >> amanda" mandir="/share/man" >> 1242737635.992990: amandad:AMANDA_TMPDIR="/tmp/amanda" >> AMANDA_DBGDIR="/tmp/amanda" >> 1242737635.992995: amandad:CONFIG_DIR="/etc/amanda" >> DEV_PREFIX="/dev/dsk/" >> 1242737635.993000: amandad:RDEV_PREFIX="/dev/rdsk/" >> DUMP="/ >> usr/sbin/ufsdump" >> 1242737635.993005: amandad:RESTORE="/usr/sbin/ >> ufsrestore" VDUMP=UNDEF VRESTORE=UNDEF >> 1242737635.993011: amandad:XFSDUMP=UNDEF >> XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF >> 1242737635.993016: amandad:SAMBA_CLIENT="/usr/sfw/bin/ >> smbclient" >> 1242737635.993021: amandad:GNUTAR="/usr/sfw/bin/gtar" >> COMPRESS_PATH="/usr/bin/gzip" >> 1242737635.993026: amandad:UNCOMPRESS_PATH="/usr/bin/ >> gzip" LPRCMD="/usr/bin/lp" >> 1242737635.993032: amandad: MAILER=UNDEF >> listed_incr_dir="/ >> var/amanda/gnutar-lists" >> 1242737635.993037: amandad: defs: DEFAULT_SERVER="galadhrim" >> DEFAULT_CONFIG="DailySet1" >> 1242737635.993042: amandad: >> DEFAULT_TAPE_SERVER="galadhrim" DEFAULT_TAPE_DEVICE="" >> 1242737635.993047: amandad:HAVE_MMAP NEED_STRSTR >> HAVE_SYSVSHM AMFLOCK_POSIX AMFLOCK_LOCKF >> 1242737635.993053: amandad:AMFLOCK_LNLOCK SETPGRP_VOID >> AMANDA_DEBUG_DAYS=4 BSD_SECURITY >> 1242737635.993058: amandad:USE_AMANDAHOSTS >> CLIENT_LOGIN="amandabackup" CHECK_USERID >> 1242737635.993063: amandad:HAVE_GZIP >> COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" >> 1242737635.993069: amandad:COMPRESS_BEST_OPT="--best" >> UNCOMPRESS_OPT="-dc" >> 1242737635.997381: amandad: getpeername returned: Socket operation >> on non-socket >> 1242737635.997434: amandad: pid 9504 finish time Tue May 19 >> 14:53:55 2009 >> >> >> so it does seem like as inetd problem and not amanda. I just have >> no clue as to how that's possible > > These are my instructs (to myself) for Linux machines -- but they > may spark > a thought in your situation: > the client needs lines like this > > add these lines to /etc/services > amanda 10080/udp # Dump server control > amidxtape 10083/tcp # Amanda tape indexing > amandaidx 10082/tcp # Amanda recovery program > > add these lines to /etc/inetd.conf and then kill -HUP inetd > process > (2 lines --- mine may wrap) > > amanda dgram udp wait amandabackup /usr/local/libexec/amanda/ > amandad amandad > amidxtape stream tcp nowait amandabackup /usr/local/libexec/amanda/ > amidxtaped amidxtaped > > >> >> >> On May 19, 2009, at 2:45 PM, Jean-Louis Martineau wrote: >> >>> Who is the owner of /tmp/amanda/amandad/amandad.20090519111556.debug >>> >>> Can you use the amandabackup account? Can you log to that account? >>> Can you enabled more logging in inetd? It is an inetd >>> misconfiguration if amandad is run as root. >>> >>> Log as amandabackup and run '/libexec/amanda/amandad -auth=bsdtcp >> > amdump' >>> >>> Jean-Louis >>> >>> Abilio Carvalho wrote: follow-up: I was wrong, it wasn't syslog, it was messages. There I now see a couple lines like: May 19 13:58:23 galadhrim inetd[24015]: [ID 317013 daemon.notice] amanda[27116] from 172.22.0.23 44223 May 19 13:58:31 galadhrim inetd[24015]: [ID 317013 daemon.notice] amanda[2
Re: Amanda must be run as user amandabackup when using bsdtcp authentication
At 3:01 PM +0200 5/19/09, Abilio Carvalho wrote: owner is amandabackup:disk I can log in to the account just fine, I don't think any more logging is possible though I'll check. I checked the manifest for the service and it confirms that it is SUPPOSED to start as amandabackup. If I do what you say, and log into amandabackup and run that, I get the following on /tmp/amanda/amandad/amandad.TIMESTAMP.debug: 1242737635.958239: amandad: pid 9504 ruid 6028 euid 6028 version 2.6.1: start at Tue May 19 14:53:55 2009 1242737635.989035: amandad: security_getdriver(name=bsdtcp) returns ff31c788 1242737635.992943: amandad: version 2.6.1 1242737635.992955: amandad: build: VERSION="Amanda-2.6.1" 1242737635.992961: amandad:BUILT_DATE="Mon May 18 12:33:06 CEST 2009" 1242737635.992967: amandad:BUILT_MACH="sparc-sun- solaris2.10" BUILT_REV="1609" 1242737635.992973: amandad:BUILT_BRANCH="amanda-261" CC="/ opt/SUNWspro/bin/cc" 1242737635.992979: amandad: paths: bindir="/bin" sbindir="/sbin" libexecdir="/libexec" 1242737635.992984: amandad:amlibexecdir="/libexec/amanda" mandir="/share/man" 1242737635.992990: amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" 1242737635.992995: amandad:CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/dsk/" 1242737635.993000: amandad:RDEV_PREFIX="/dev/rdsk/" DUMP="/ usr/sbin/ufsdump" 1242737635.993005: amandad:RESTORE="/usr/sbin/ufsrestore" VDUMP=UNDEF VRESTORE=UNDEF 1242737635.993011: amandad:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF 1242737635.993016: amandad:SAMBA_CLIENT="/usr/sfw/bin/ smbclient" 1242737635.993021: amandad:GNUTAR="/usr/sfw/bin/gtar" COMPRESS_PATH="/usr/bin/gzip" 1242737635.993026: amandad:UNCOMPRESS_PATH="/usr/bin/gzip" LPRCMD="/usr/bin/lp" 1242737635.993032: amandad: MAILER=UNDEF listed_incr_dir="/ var/amanda/gnutar-lists" 1242737635.993037: amandad: defs: DEFAULT_SERVER="galadhrim" DEFAULT_CONFIG="DailySet1" 1242737635.993042: amandad:DEFAULT_TAPE_SERVER="galadhrim" DEFAULT_TAPE_DEVICE="" 1242737635.993047: amandad:HAVE_MMAP NEED_STRSTR HAVE_SYSVSHM AMFLOCK_POSIX AMFLOCK_LOCKF 1242737635.993053: amandad:AMFLOCK_LNLOCK SETPGRP_VOID AMANDA_DEBUG_DAYS=4 BSD_SECURITY 1242737635.993058: amandad:USE_AMANDAHOSTS CLIENT_LOGIN="amandabackup" CHECK_USERID 1242737635.993063: amandad:HAVE_GZIP COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" 1242737635.993069: amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" 1242737635.997381: amandad: getpeername returned: Socket operation on non-socket 1242737635.997434: amandad: pid 9504 finish time Tue May 19 14:53:55 2009 so it does seem like as inetd problem and not amanda. I just have no clue as to how that's possible These are my instructs (to myself) for Linux machines -- but they may spark a thought in your situation: the client needs lines like this add these lines to /etc/services amanda 10080/udp # Dump server control amidxtape 10083/tcp # Amanda tape indexing amandaidx 10082/tcp # Amanda recovery program add these lines to /etc/inetd.conf and then kill -HUP inetd process (2 lines --- mine may wrap) amanda dgram udp wait amandabackup /usr/local/libexec/amanda/amandad amandad amidxtape stream tcp nowait amandabackup /usr/local/libexec/amanda/amidxtaped amidxtaped On May 19, 2009, at 2:45 PM, Jean-Louis Martineau wrote: Who is the owner of /tmp/amanda/amandad/amandad.20090519111556.debug Can you use the amandabackup account? Can you log to that account? Can you enabled more logging in inetd? It is an inetd misconfiguration if amandad is run as root. Log as amandabackup and run '/libexec/amanda/amandad -auth=bsdtcp > amdump' Jean-Louis Abilio Carvalho wrote: follow-up: I was wrong, it wasn't syslog, it was messages. There I now see a couple lines like: May 19 13:58:23 galadhrim inetd[24015]: [ID 317013 daemon.notice] amanda[27116] from 172.22.0.23 44223 May 19 13:58:31 galadhrim inetd[24015]: [ID 317013 daemon.notice] amanda[27214] from 172.22.0.23 703 May 19 13:59:12 galadhrim inetd[24015]: [ID 317013 daemon.notice] amanda[27619] from 172.22.0.23 703 On May 19, 2009, at 1:37 PM, Jean-Louis Martineau wrote: Abilio Carvalho wrote: the log directory on the client only has the following: r...@backupclient:/tmp/amanda/amandad# cat amandad. 20090519111556.debug 1242724556.328466: amandad: pid 18933 ruid 0 euid 0 version 2.6.1: start at Tue May 19 11:15:56 2009 ruid 0 euid 0 That's root user Do you have an amandabackup user on the client Check inet log Jean-Louis 1242724556.339271: amandad: security_getdriver(name=bsdtcp) returns ff31c788 1242724556.339369: amandad: critical (fatal): Amanda must be run as user 'amandabackup' when u
Re: Amanda must be run as user amandabackup when using bsdtcp authentication
owner is amandabackup:disk I can log in to the account just fine, I don't think any more logging is possible though I'll check. I checked the manifest for the service and it confirms that it is SUPPOSED to start as amandabackup. If I do what you say, and log into amandabackup and run that, I get the following on /tmp/amanda/amandad/amandad.TIMESTAMP.debug: 1242737635.958239: amandad: pid 9504 ruid 6028 euid 6028 version 2.6.1: start at Tue May 19 14:53:55 2009 1242737635.989035: amandad: security_getdriver(name=bsdtcp) returns ff31c788 1242737635.992943: amandad: version 2.6.1 1242737635.992955: amandad: build: VERSION="Amanda-2.6.1" 1242737635.992961: amandad:BUILT_DATE="Mon May 18 12:33:06 CEST 2009" 1242737635.992967: amandad:BUILT_MACH="sparc-sun- solaris2.10" BUILT_REV="1609" 1242737635.992973: amandad:BUILT_BRANCH="amanda-261" CC="/ opt/SUNWspro/bin/cc" 1242737635.992979: amandad: paths: bindir="/bin" sbindir="/sbin" libexecdir="/libexec" 1242737635.992984: amandad:amlibexecdir="/libexec/amanda" mandir="/share/man" 1242737635.992990: amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" 1242737635.992995: amandad:CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/dsk/" 1242737635.993000: amandad:RDEV_PREFIX="/dev/rdsk/" DUMP="/ usr/sbin/ufsdump" 1242737635.993005: amandad:RESTORE="/usr/sbin/ufsrestore" VDUMP=UNDEF VRESTORE=UNDEF 1242737635.993011: amandad:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF 1242737635.993016: amandad:SAMBA_CLIENT="/usr/sfw/bin/ smbclient" 1242737635.993021: amandad:GNUTAR="/usr/sfw/bin/gtar" COMPRESS_PATH="/usr/bin/gzip" 1242737635.993026: amandad:UNCOMPRESS_PATH="/usr/bin/gzip" LPRCMD="/usr/bin/lp" 1242737635.993032: amandad: MAILER=UNDEF listed_incr_dir="/ var/amanda/gnutar-lists" 1242737635.993037: amandad: defs: DEFAULT_SERVER="galadhrim" DEFAULT_CONFIG="DailySet1" 1242737635.993042: amandad:DEFAULT_TAPE_SERVER="galadhrim" DEFAULT_TAPE_DEVICE="" 1242737635.993047: amandad:HAVE_MMAP NEED_STRSTR HAVE_SYSVSHM AMFLOCK_POSIX AMFLOCK_LOCKF 1242737635.993053: amandad:AMFLOCK_LNLOCK SETPGRP_VOID AMANDA_DEBUG_DAYS=4 BSD_SECURITY 1242737635.993058: amandad:USE_AMANDAHOSTS CLIENT_LOGIN="amandabackup" CHECK_USERID 1242737635.993063: amandad:HAVE_GZIP COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" 1242737635.993069: amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" 1242737635.997381: amandad: getpeername returned: Socket operation on non-socket 1242737635.997434: amandad: pid 9504 finish time Tue May 19 14:53:55 2009 so it does seem like as inetd problem and not amanda. I just have no clue as to how that's possible On May 19, 2009, at 2:45 PM, Jean-Louis Martineau wrote: > Who is the owner of /tmp/amanda/amandad/amandad.20090519111556.debug > > Can you use the amandabackup account? Can you log to that account? > Can you enabled more logging in inetd? It is an inetd > misconfiguration if amandad is run as root. > > Log as amandabackup and run '/libexec/amanda/amandad -auth=bsdtcp > amdump' > > Jean-Louis > > Abilio Carvalho wrote: >> follow-up: >> >> I was wrong, it wasn't syslog, it was messages. There I now see a >> couple lines like: >> >> May 19 13:58:23 galadhrim inetd[24015]: [ID 317013 daemon.notice] >> amanda[27116] from 172.22.0.23 44223 >> May 19 13:58:31 galadhrim inetd[24015]: [ID 317013 daemon.notice] >> amanda[27214] from 172.22.0.23 703 >> May 19 13:59:12 galadhrim inetd[24015]: [ID 317013 daemon.notice] >> amanda[27619] from 172.22.0.23 703 >> >> >> On May 19, 2009, at 1:37 PM, Jean-Louis Martineau wrote: >> >> >>> Abilio Carvalho wrote: >>> the log directory on the client only has the following: r...@backupclient:/tmp/amanda/amandad# cat amandad. 20090519111556.debug 1242724556.328466: amandad: pid 18933 ruid 0 euid 0 version 2.6.1: start at Tue May 19 11:15:56 2009 >>> ruid 0 euid 0 >>> That's root user >>> Do you have an amandabackup user on the client >>> Check inet log >>> >>> Jean-Louis >>> >>> 1242724556.339271: amandad: security_getdriver(name=bsdtcp) returns ff31c788 1242724556.339369: amandad: critical (fatal): Amanda must be run as user 'amandabackup' when using 'bsdtcp' authentication I can't even see what user it's TRYING to use, only that it should be running as amandabackup. All relevant config files tell me that it IS. Any way to get more descriptive logs? I tried debug_amandad on the amanda-client.conf, but that had no effect please help Abilio --- This e-mail is strictly confidential and
Re: Amanda must be run as user amandabackup when using bsdtcp authentication
Yes, the user amandabackup exists, as you can see it owns all the amanda-related files. I've checked nsswitch.conf and it's checking files before nisplus on passwd, so that's not it. I'm unsure what you mean by inetd log, but from what I've searched it's enabling tcp_trace and tcp_wrappers on the amanda service and check the syslog for any inetd related entries. Nothing shows up, including on a tail -f syslog while I try to connect from the server with amcheck. Can you be more specific about which log to check/use if what I did was not it? Thank you for the response, though. I'm going slightly insane here Abilio On May 19, 2009, at 1:37 PM, Jean-Louis Martineau wrote: > Abilio Carvalho wrote: >> the log directory on the client only has the following: >> >> r...@backupclient:/tmp/amanda/amandad# cat amandad. >> 20090519111556.debug >> 1242724556.328466: amandad: pid 18933 ruid 0 euid 0 version 2.6.1: >> start at Tue May 19 11:15:56 2009 >> > ruid 0 euid 0 > That's root user > Do you have an amandabackup user on the client > Check inet log > > Jean-Louis > >> 1242724556.339271: amandad: security_getdriver(name=bsdtcp) >> returns ff31c788 >> 1242724556.339369: amandad: critical (fatal): Amanda must be run >> as user 'amandabackup' when using 'bsdtcp' authentication >> >> I can't even see what user it's TRYING to use, only that it should >> be running as amandabackup. All relevant config files tell me that >> it IS. Any way to get more descriptive logs? I tried debug_amandad >> on the amanda-client.conf, but that had no effect >> >> please help >> >> Abilio >> >> --- >> This e-mail is strictly confidential and may be privileged. >> It is intended solely for the addressee. If you are not the intended >> recipient, any copying, distribution or any other use of this message >> is prohibited and may be unlawful. In such case, please notify the >> sender Immediately and destroy this e-mail. >> >> >> > --- This e-mail is strictly confidential and may be privileged. It is intended solely for the addressee. If you are not the intended recipient, any copying, distribution or any other use of this message is prohibited and may be unlawful. In such case, please notify the sender Immediately and destroy this e-mail.
Re: Amanda must be run as user amandabackup when using bsdtcp authentication
follow-up: I was wrong, it wasn't syslog, it was messages. There I now see a couple lines like: May 19 13:58:23 galadhrim inetd[24015]: [ID 317013 daemon.notice] amanda[27116] from 172.22.0.23 44223 May 19 13:58:31 galadhrim inetd[24015]: [ID 317013 daemon.notice] amanda[27214] from 172.22.0.23 703 May 19 13:59:12 galadhrim inetd[24015]: [ID 317013 daemon.notice] amanda[27619] from 172.22.0.23 703 On May 19, 2009, at 1:37 PM, Jean-Louis Martineau wrote: > Abilio Carvalho wrote: >> the log directory on the client only has the following: >> >> r...@backupclient:/tmp/amanda/amandad# cat amandad. >> 20090519111556.debug >> 1242724556.328466: amandad: pid 18933 ruid 0 euid 0 version 2.6.1: >> start at Tue May 19 11:15:56 2009 >> > ruid 0 euid 0 > That's root user > Do you have an amandabackup user on the client > Check inet log > > Jean-Louis > >> 1242724556.339271: amandad: security_getdriver(name=bsdtcp) >> returns ff31c788 >> 1242724556.339369: amandad: critical (fatal): Amanda must be run >> as user 'amandabackup' when using 'bsdtcp' authentication >> >> I can't even see what user it's TRYING to use, only that it should >> be running as amandabackup. All relevant config files tell me that >> it IS. Any way to get more descriptive logs? I tried debug_amandad >> on the amanda-client.conf, but that had no effect >> >> please help >> >> Abilio >> >> --- >> This e-mail is strictly confidential and may be privileged. >> It is intended solely for the addressee. If you are not the intended >> recipient, any copying, distribution or any other use of this message >> is prohibited and may be unlawful. In such case, please notify the >> sender Immediately and destroy this e-mail. >> >> >> > --- This e-mail is strictly confidential and may be privileged. It is intended solely for the addressee. If you are not the intended recipient, any copying, distribution or any other use of this message is prohibited and may be unlawful. In such case, please notify the sender Immediately and destroy this e-mail.
Re: Amanda must be run as user amandabackup when using bsdtcp authentication
Abilio Carvalho wrote: the log directory on the client only has the following: r...@backupclient:/tmp/amanda/amandad# cat amandad.20090519111556.debug 1242724556.328466: amandad: pid 18933 ruid 0 euid 0 version 2.6.1: start at Tue May 19 11:15:56 2009 ruid 0 euid 0 That's root user Do you have an amandabackup user on the client Check inet log Jean-Louis 1242724556.339271: amandad: security_getdriver(name=bsdtcp) returns ff31c788 1242724556.339369: amandad: critical (fatal): Amanda must be run as user 'amandabackup' when using 'bsdtcp' authentication I can't even see what user it's TRYING to use, only that it should be running as amandabackup. All relevant config files tell me that it IS. Any way to get more descriptive logs? I tried debug_amandad on the amanda-client.conf, but that had no effect please help Abilio --- This e-mail is strictly confidential and may be privileged. It is intended solely for the addressee. If you are not the intended recipient, any copying, distribution or any other use of this message is prohibited and may be unlawful. In such case, please notify the sender Immediately and destroy this e-mail.
Re: Amanda must be run as user amandabackup when using bsdtcp authentication
Done further tests, still no explanation. Amandahosts on the client is: BACKUPHOST.bbp.ch amandabackup amdump BACKUPHOST amandabackup amdump inetadm -l svc:/network/amanda/tcp on the client returns: SCOPENAME=VALUE name="amanda" endpoint_type="stream" proto="tcp" isrpc=FALSE wait=FALSE exec="/libexec/amanda/amandad -auth=bsdtcp amdump" user="amandabackup" default bind_addr="" default bind_fail_max=-1 default bind_fail_interval=-1 default max_con_rate=-1 default max_copies=-1 default con_rate_offline=-1 default failrate_cnt=40 default failrate_interval=60 default inherit_env=TRUE default tcp_trace=FALSE default tcp_wrappers=FALSE the log directory on the client only has the following: r...@backupclient:/tmp/amanda/amandad# cat amandad.20090519111556.debug 1242724556.328466: amandad: pid 18933 ruid 0 euid 0 version 2.6.1: start at Tue May 19 11:15:56 2009 1242724556.339271: amandad: security_getdriver(name=bsdtcp) returns ff31c788 1242724556.339369: amandad: critical (fatal): Amanda must be run as user 'amandabackup' when using 'bsdtcp' authentication I can't even see what user it's TRYING to use, only that it should be running as amandabackup. All relevant config files tell me that it IS. Any way to get more descriptive logs? I tried debug_amandad on the amanda-client.conf, but that had no effect please help Abilio --- This e-mail is strictly confidential and may be privileged. It is intended solely for the addressee. If you are not the intended recipient, any copying, distribution or any other use of this message is prohibited and may be unlawful. In such case, please notify the sender Immediately and destroy this e-mail.
Re: Amanda must be run as user amandabackup when using bsdtcp authentication
Maybe, but I have another machine with the exact same inetadm output and that one works fine so it's not the cause of this specific problem Abilio On May 19, 2009, at 5:31 AM, Frank Smith wrote: > Abilio Carvalho wrote: >> Anyone? I'm kinda lost at a problem that seems so basic, and I could >> really use a second pair of eyes. As far as I can see, all config >> files are correct, permissions on /tmp and /var amanda subdirectories >> are fine, etc. It's NOT just a case of me overlooking something that >> can be found on the 15 mins amanda backup doc. At least, I don't >> think >> so. >> >> Thanks >> >> Abilio >> >> >> On May 18, 2009, at 5:30 PM, Abilio Carvalho wrote: >> >>> I'm getting this when I do am amcheck -c, but I don't know what I'm >>> missing. >>> >>> Here's the relevant data: >>> >>> Server works: I have 6 hosts configured, only 1 is failing. Client >>> that fails is a new install I'm doing atm. >>> >>> amanda was configured with: ./configure --without-server --with- >>> user=amandabackup --with-group=disk --prefix= --with-amandahosts -- >>> without-ipv6 >>> >>> /var/lib/amanda and the .amandahosts in it is owned by >>> amandabackup:disk >>> >>> output of inetadm -l svc:/network/amanda/tcp is: >>> >>> SCOPENAME=VALUE >>> name="amanda" >>> endpoint_type="stream" >>> proto="tcp" >>> isrpc=FALSE >>> wait=FALSE >>> exec="/libexec/amanda/amandad -auth=bsdtcp" >>> user="amandabackup" >>> default bind_addr="" >>> default bind_fail_max=-1 >>> default bind_fail_interval=-1 >>> default max_con_rate=-1 >>> default max_copies=-1 >>> default con_rate_offline=-1 >>> default failrate_cnt=40 >>> default failrate_interval=60 >>> default inherit_env=TRUE >>> default tcp_trace=FALSE >>> default tcp_wrappers=FALSE >>> >>> >>> Can you help me figure out what unbelievably basic thing I missed? >>> Thanks >>> > > Shouldn't the 'wait' parameter be 'true'? > > Frank > > > -- > Frank Smith fsm...@hoovers.com > Sr. Systems Administrator Voice: 512-374-4673 > Hoover's Online Fax: 512-374-4501 --- This e-mail is strictly confidential and may be privileged. It is intended solely for the addressee. If you are not the intended recipient, any copying, distribution or any other use of this message is prohibited and may be unlawful. In such case, please notify the sender Immediately and destroy this e-mail.
Re: Amanda must be run as user amandabackup when using bsdtcp authentication
the prefix with no argument is how the config.log interprets prefix='', which I did to install amanda in the default directories rather than inside a specific subdir. Again, like frank's attempt I have another machine with the same config options and that one works fine. Cheers Abilio On May 19, 2009, at 5:21 AM, Gene Heskett wrote: > On Monday 18 May 2009, Abilio Carvalho wrote: >> Anyone? I'm kinda lost at a problem that seems so basic, and I could >> really use a second pair of eyes. As far as I can see, all config >> files are correct, permissions on /tmp and /var amanda subdirectories >> are fine, etc. It's NOT just a case of me overlooking something that >> can be found on the 15 mins amanda backup doc. At least, I don't >> think >> so. >> >> Thanks >> >> Abilio >> >> On May 18, 2009, at 5:30 PM, Abilio Carvalho wrote: >>> I'm getting this when I do am amcheck -c, but I don't know what I'm >>> missing. >>> >>> Here's the relevant data: >>> >>> Server works: I have 6 hosts configured, only 1 is failing. Client >>> that fails is a new install I'm doing atm. >>> >>> amanda was configured with: ./configure --without-server --with- >>> user=amandabackup --with-group=disk --prefix= --with-amandahosts -- >>> without-ipv6 >>> > > Ahh, whats the '--prefix=' but no argument for it? Other than that > you are > enough different from my setup I'm afraid I'm not going to be able > to help. > >>> /var/lib/amanda and the .amandahosts in it is owned by >>> amandabackup:disk >>> >>> output of inetadm -l svc:/network/amanda/tcp is: >>> >>> SCOPENAME=VALUE >>> name="amanda" >>> endpoint_type="stream" >>> proto="tcp" >>> isrpc=FALSE >>> wait=FALSE >>> exec="/libexec/amanda/amandad -auth=bsdtcp" >>> user="amandabackup" >>> default bind_addr="" >>> default bind_fail_max=-1 >>> default bind_fail_interval=-1 >>> default max_con_rate=-1 >>> default max_copies=-1 >>> default con_rate_offline=-1 >>> default failrate_cnt=40 >>> default failrate_interval=60 >>> default inherit_env=TRUE >>> default tcp_trace=FALSE >>> default tcp_wrappers=FALSE >>> >>> >>> Can you help me figure out what unbelievably basic thing I missed? >>> Thanks >>> >>> >>> -- >>> - This e-mail is strictly confidential and may be >>> privileged. >>> It is intended solely for the addressee. If you are not the intended >>> recipient, any copying, distribution or any other use of this >>> message >>> is prohibited and may be unlawful. In such case, please notify the >>> sender Immediately and destroy this e-mail. >>> -- >>> -- >> >> >> --- This e-mail is strictly confidential and may be privileged. >> It is intended solely for the addressee. If you are not the intended >> recipient, any copying, distribution or any other use of this message >> is prohibited and may be unlawful. In such case, please notify the >> sender Immediately and destroy this e-mail. >> >> > > > -- > Cheers, Gene > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > Prizes are for children. > -- Charles Ives, upon being given, but refusing, the > Pulitzer prize > --- This e-mail is strictly confidential and may be privileged. It is intended solely for the addressee. If you are not the intended recipient, any copying, distribution or any other use of this message is prohibited and may be unlawful. In such case, please notify the sender Immediately and destroy this e-mail.
Re: Amanda must be run as user amandabackup when using bsdtcp authentication
Abilio Carvalho wrote: > Anyone? I'm kinda lost at a problem that seems so basic, and I could > really use a second pair of eyes. As far as I can see, all config > files are correct, permissions on /tmp and /var amanda subdirectories > are fine, etc. It's NOT just a case of me overlooking something that > can be found on the 15 mins amanda backup doc. At least, I don't think > so. > > Thanks > > Abilio > > > On May 18, 2009, at 5:30 PM, Abilio Carvalho wrote: > >> I'm getting this when I do am amcheck -c, but I don't know what I'm >> missing. >> >> Here's the relevant data: >> >> Server works: I have 6 hosts configured, only 1 is failing. Client >> that fails is a new install I'm doing atm. >> >> amanda was configured with: ./configure --without-server --with- >> user=amandabackup --with-group=disk --prefix= --with-amandahosts -- >> without-ipv6 >> >> /var/lib/amanda and the .amandahosts in it is owned by >> amandabackup:disk >> >> output of inetadm -l svc:/network/amanda/tcp is: >> >> SCOPENAME=VALUE >> name="amanda" >> endpoint_type="stream" >> proto="tcp" >> isrpc=FALSE >> wait=FALSE >> exec="/libexec/amanda/amandad -auth=bsdtcp" >> user="amandabackup" >> default bind_addr="" >> default bind_fail_max=-1 >> default bind_fail_interval=-1 >> default max_con_rate=-1 >> default max_copies=-1 >> default con_rate_offline=-1 >> default failrate_cnt=40 >> default failrate_interval=60 >> default inherit_env=TRUE >> default tcp_trace=FALSE >> default tcp_wrappers=FALSE >> >> >> Can you help me figure out what unbelievably basic thing I missed? >> Thanks >> Shouldn't the 'wait' parameter be 'true'? Frank -- Frank Smith fsm...@hoovers.com Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Amanda must be run as user amandabackup when using bsdtcp authentication
On Monday 18 May 2009, Abilio Carvalho wrote: >Anyone? I'm kinda lost at a problem that seems so basic, and I could >really use a second pair of eyes. As far as I can see, all config >files are correct, permissions on /tmp and /var amanda subdirectories >are fine, etc. It's NOT just a case of me overlooking something that >can be found on the 15 mins amanda backup doc. At least, I don't think >so. > >Thanks > >Abilio > >On May 18, 2009, at 5:30 PM, Abilio Carvalho wrote: >> I'm getting this when I do am amcheck -c, but I don't know what I'm >> missing. >> >> Here's the relevant data: >> >> Server works: I have 6 hosts configured, only 1 is failing. Client >> that fails is a new install I'm doing atm. >> >> amanda was configured with: ./configure --without-server --with- >> user=amandabackup --with-group=disk --prefix= --with-amandahosts -- >> without-ipv6 >> Ahh, whats the '--prefix=' but no argument for it? Other than that you are enough different from my setup I'm afraid I'm not going to be able to help. >> /var/lib/amanda and the .amandahosts in it is owned by >> amandabackup:disk >> >> output of inetadm -l svc:/network/amanda/tcp is: >> >> SCOPENAME=VALUE >> name="amanda" >> endpoint_type="stream" >> proto="tcp" >> isrpc=FALSE >> wait=FALSE >> exec="/libexec/amanda/amandad -auth=bsdtcp" >> user="amandabackup" >> default bind_addr="" >> default bind_fail_max=-1 >> default bind_fail_interval=-1 >> default max_con_rate=-1 >> default max_copies=-1 >> default con_rate_offline=-1 >> default failrate_cnt=40 >> default failrate_interval=60 >> default inherit_env=TRUE >> default tcp_trace=FALSE >> default tcp_wrappers=FALSE >> >> >> Can you help me figure out what unbelievably basic thing I missed? >> Thanks >> >> >> -- >>- This e-mail is strictly confidential and may be privileged. >> It is intended solely for the addressee. If you are not the intended >> recipient, any copying, distribution or any other use of this message >> is prohibited and may be unlawful. In such case, please notify the >> sender Immediately and destroy this e-mail. >> -- >>-- > > >--- This e-mail is strictly confidential and may be privileged. >It is intended solely for the addressee. If you are not the intended >recipient, any copying, distribution or any other use of this message >is prohibited and may be unlawful. In such case, please notify the >sender Immediately and destroy this e-mail. > > -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Prizes are for children. -- Charles Ives, upon being given, but refusing, the Pulitzer prize
Re: Amanda must be run as user amandabackup when using bsdtcp authentication
Anyone? I'm kinda lost at a problem that seems so basic, and I could really use a second pair of eyes. As far as I can see, all config files are correct, permissions on /tmp and /var amanda subdirectories are fine, etc. It's NOT just a case of me overlooking something that can be found on the 15 mins amanda backup doc. At least, I don't think so. Thanks Abilio On May 18, 2009, at 5:30 PM, Abilio Carvalho wrote: > I'm getting this when I do am amcheck -c, but I don't know what I'm > missing. > > Here's the relevant data: > > Server works: I have 6 hosts configured, only 1 is failing. Client > that fails is a new install I'm doing atm. > > amanda was configured with: ./configure --without-server --with- > user=amandabackup --with-group=disk --prefix= --with-amandahosts -- > without-ipv6 > > /var/lib/amanda and the .amandahosts in it is owned by > amandabackup:disk > > output of inetadm -l svc:/network/amanda/tcp is: > > SCOPENAME=VALUE > name="amanda" > endpoint_type="stream" > proto="tcp" > isrpc=FALSE > wait=FALSE > exec="/libexec/amanda/amandad -auth=bsdtcp" > user="amandabackup" > default bind_addr="" > default bind_fail_max=-1 > default bind_fail_interval=-1 > default max_con_rate=-1 > default max_copies=-1 > default con_rate_offline=-1 > default failrate_cnt=40 > default failrate_interval=60 > default inherit_env=TRUE > default tcp_trace=FALSE > default tcp_wrappers=FALSE > > > Can you help me figure out what unbelievably basic thing I missed? > Thanks > > > --- > This e-mail is strictly confidential and may be privileged. > It is intended solely for the addressee. If you are not the intended > recipient, any copying, distribution or any other use of this message > is prohibited and may be unlawful. In such case, please notify the > sender Immediately and destroy this e-mail. > > --- This e-mail is strictly confidential and may be privileged. It is intended solely for the addressee. If you are not the intended recipient, any copying, distribution or any other use of this message is prohibited and may be unlawful. In such case, please notify the sender Immediately and destroy this e-mail.
