Re: amflush doesn't run. at all
Jean-Louis, I'm gonna send you a separate mail with the whole file, maybe
you'll figure something out I can't.
Cheers
Abe
On Jun 7, 2013, at 8:10 PM, Jean-Louis Martineau wrote:
> On 06/07/2013 11:02 AM, Abilio Carvalho wrote:
>> Does this look familiar at all? The strace of "amflush BBPTape" at one point
>> just becomes an endless (literally. I think it cycles endlessly, but I can't
>> info the pattern, it's too large) series of these. Not only this machine,
>> mind, every single DLE that's configured will show up in the log like this:
>>
>>
>> stat("/amanda/holding/20130417171040/.bbp.ch._dev_mapper_igtgrp-igtlv.0.17120",
>> {st_mode=S_IFREG|0600, st_size=1048576, ...}) = 0
>> stat("/amanda/holding/20130417171040/.bbp.ch._dev_mapper_igtgrp-igtlv.0.17120",
>> {st_mode=S_IFREG|0600, st_size=1048576, ...}) = 0
>> open("/amanda/holding/20130417171040/.bbp.ch._dev_mapper_igtgrp-igtlv.0.17120",
>> O_RDONLY) = 5
>> fcntl(5, F_SETFD, FD_CLOEXEC) = 0
>> read(5, "AMANDA: CONT_FILE 20130417171040"..., 32768) = 32768
>> close(5^C)= 0
> Can you print a little more so I can see what repeat, do the number (17120)
> increase?
>
> You have a lot of file in the holding disk, you should use a larger chunksize.
> Lot of files == slow, slower, ...
>
> Jean-Louis
>>
>> Thanks. This issue is driving me mad, and the point is fast approaching
>> where my boss just nixes amanda. (not its fault, really, I'm just bad at
>> this)
>>
>> Cheers
>> Abilio
>>
>> On May 16, 2013, at 2:00 PM, Jean-Louis Martineau
>> wrote:
>>
>>> Not creating the debug files is strange as it is one of the first thing it
>>> do.
>>>
>>> Use strace or a debugger (gdb) to find where it hang.
>>>
>>> Jean-Louis
>>>
>>> On 05/16/2013 05:16 AM, Abilio Carvalho wrote:
>>>> Hi. still slowly trying to get my backup system to work, it's going OK but
>>>> for some reason, whenever I get some dumps stuck in holding, I can't get
>>>> those to tape at all. amflush just seems to hang immediately after I run
>>>> it. amflush -fs also gives me exactly nothing to work with. Nothing in any
>>>> logs anywhere that I can see.
>>>>
>>>> Similarly, amadmin holding list hangs in exactly the same way.
>>>>
>>>> I'm definitely not good enough yet to debug this by myself, can anyone
>>>> help? with no logs or error messages or whatever I wouldn't even know
>>>> where to start.
>>>>
>>>> Cheers
>>>> Abilio
>>>> **
>>>> This email and any files transmitted with it are confidential and
>>>> intended solely for the use of the individual or entity to whom they
>>>> are addressed. If you have received this email in error please notify
>>>> the system manager.
>>>>
>>>> This footnote also confirms that this email message has been swept by
>>>> Clearswift for the presence of computer viruses.
>>>>
>>>> www.clearswift.com
>>>> **
>>>>
>
Re: amflush doesn't run. at all
Does this look familiar at all? The strace of "amflush BBPTape" at one point
just becomes an endless (literally. I think it cycles endlessly, but I can't
info the pattern, it's too large) series of these. Not only this machine, mind,
every single DLE that's configured will show up in the log like this:
stat("/amanda/holding/20130417171040/.bbp.ch._dev_mapper_igtgrp-igtlv.0.17120",
{st_mode=S_IFREG|0600, st_size=1048576, ...}) = 0
stat("/amanda/holding/20130417171040/.bbp.ch._dev_mapper_igtgrp-igtlv.0.17120",
{st_mode=S_IFREG|0600, st_size=1048576, ...}) = 0
open("/amanda/holding/20130417171040/.bbp.ch._dev_mapper_igtgrp-igtlv.0.17120",
O_RDONLY) = 5
fcntl(5, F_SETFD, FD_CLOEXEC) = 0
read(5, "AMANDA: CONT_FILE 20130417171040"..., 32768) = 32768
close(5^C)= 0
Thanks. This issue is driving me mad, and the point is fast approaching where
my boss just nixes amanda. (not its fault, really, I'm just bad at this)
Cheers
Abilio
On May 16, 2013, at 2:00 PM, Jean-Louis Martineau wrote:
>
> Not creating the debug files is strange as it is one of the first thing it do.
>
> Use strace or a debugger (gdb) to find where it hang.
>
> Jean-Louis
>
> On 05/16/2013 05:16 AM, Abilio Carvalho wrote:
>> Hi. still slowly trying to get my backup system to work, it's going OK but
>> for some reason, whenever I get some dumps stuck in holding, I can't get
>> those to tape at all. amflush just seems to hang immediately after I run it.
>> amflush -fs also gives me exactly nothing to work with. Nothing in any logs
>> anywhere that I can see.
>>
>> Similarly, amadmin holding list hangs in exactly the same way.
>>
>> I'm definitely not good enough yet to debug this by myself, can anyone help?
>> with no logs or error messages or whatever I wouldn't even know where to
>> start.
>>
>> Cheers
>> Abilio
>> **
>> This email and any files transmitted with it are confidential and
>> intended solely for the use of the individual or entity to whom they
>> are addressed. If you have received this email in error please notify
>> the system manager.
>>
>> This footnote also confirms that this email message has been swept by
>> Clearswift for the presence of computer viruses.
>>
>> www.clearswift.com
>> **
>>
>
amflush doesn't run. at all
Hi. still slowly trying to get my backup system to work, it's going OK but for some reason, whenever I get some dumps stuck in holding, I can't get those to tape at all. amflush just seems to hang immediately after I run it. amflush -fs also gives me exactly nothing to work with. Nothing in any logs anywhere that I can see. Similarly, amadmin holding list hangs in exactly the same way. I'm definitely not good enough yet to debug this by myself, can anyone help? with no logs or error messages or whatever I wouldn't even know where to start. Cheers Abilio ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by Clearswift for the presence of computer viruses. www.clearswift.com **
Re: LTO6 tapetype
OK, this is odd. Here's what I get, can you guys help me figure this out?
$ mtx -f /dev/sg2 status
Storage Changer /dev/sg2:1 Drives, 8 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 2 Loaded):VolumeTag = ABR832L6
Storage Element 1:Full :VolumeTag=ABR833L6
Storage Element 2:Empty
Storage Element 3:Empty
Storage Element 4:Empty
Storage Element 5:Empty
Storage Element 6:Empty
Storage Element 7:Empty
Storage Element 8:Empty
$ tapeinfo -f /dev/st0
Product Type: Tape Drive
Vendor ID: 'HP '
Product ID: 'Ultrium 6-SCSI '
Revision: '22CW'
Attached Changer API: No
SerialNumber: 'HU1246T9JH'
MinBlock: 1
MaxBlock: 16777215
SCSI ID: 0
SCSI LUN: 0
Ready: yes
BufferedMode: yes
Medium Type: Not Loaded
Density Code: 0x5a
BlockSize: 0
DataCompEnabled: no
DataCompCapable: yes
DataDeCompEnabled: yes
CompType: 0x1
DeCompType: 0x1
BOP: yes
Block Position: 0
ActivePartition: 0
EarlyWarningSize: 0
NumPartitions: 0
MaxPartitions: 3
$ amtapetype -c -f /dev/st0
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Checking for FSF_AFTER_FILEMARK requirement
Applying heuristic check for compression.
Wrote random (uncompressible) data at 73472726.7096774 bytes/sec
Wrote fixed (compressible) data at 101229090.13 bytes/sec
Compression: enabled
NOTE: I mistyped my last email. I ran mt on /dev/st0, not sg2. this email has
the correct devices.
Thanks for the help so far, Jean-François
On Apr 30, 2013, at 4:51 PM, Jean-Francois Malouin
wrote:
> * Abilio Carvalho [20130430 10:36]:
>> sorry, no I hadn't disabled compression. Today I installed mt-st and
>> following the wiki I ran:
>>
>> mt -f /dev/sg2 compression 0
>> mt -f /dev/sg2 defcompression 0
>>
>> but when I now run amtapetype it still tells me:
>>
>> Applying heuristic check for compression.
>> Wrote random (uncompressible) data at 73376008.2580645 bytes/sec
>> Wrote fixed (compressible) data at 101095833.6 bytes/sec
>> Compression: enabled
>>
>> how can I make sure hardware compression is off?
>
> Make sure you have a tape loaded.
> Replace the tape drive scsi generic device sgX accordingly.
> In case of LTO5 here is what I get:
>
> ~# tapeinfo -f /dev/sgX
> Product Type: Tape Drive
> Vendor ID: 'HP '
> Product ID: 'Ultrium 5-SCSI '
> ...
> DataCompEnabled: yes
> DataCompCapable: yes
> DataDeCompEnabled: yes
> ...
>
> ~# mt-st -f /dev/nst0 defcompression 0
> ~# tapeinfo -f /dev/sgX
> ...
> DataCompEnabled: no
> DataCompCapable: yes
> DataDeCompEnabled: yes
>
> hth,
> jf
>
>>
>> On Apr 17, 2013, at 6:40 PM, Jean-Francois Malouin
>> wrote:
>>
>>> * Abilio Carvalho [20130417 10:19]:
>>>> Well, since noone answered, I had to run amtapetype, so here it is if
>>>> anyone else needs it:
>>>>
>>>> define tapetype LTO6 {
>>>> comment "Created by amtapetype; compression enabled"
>>>> length 2442818848 kbytes
>>>> filemark 1806 kbytes
>>>> speed 74006 kps
>>>> blocksize 32 kbytes
>>>> }
>>>
>>> Hmmm, speed look way off. Native speed is 160MBs for LTO6...
>>> Did you disable hardware compression before running amtapetype?
>>> Also, you might want to test with larger blocksize, for LTO5 I use 2MB
>>> with good results
>>>
>>> hth,
>>> jf
>>>
>>>>
>>>>
>>>> On Apr 16, 2013, at 3:24 PM, Abilio Carvalho
>>>> wrote:
>>>>
>>>>> Hi, just a quick question, does anyone have a tape type for an LTO6
>>>>> drive? (Ideally an HP Ultrium 6 SCSI)
>>>>>
>>>>> Thanks
>>>>> Abilio
**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
Clearswift for the presence of computer viruses.
www.clearswift.com
**
Re: LTO6 tapetype
sorry, no I hadn't disabled compression. Today I installed mt-st and following
the wiki I ran:
mt -f /dev/sg2 compression 0
mt -f /dev/sg2 defcompression 0
but when I now run amtapetype it still tells me:
Applying heuristic check for compression.
Wrote random (uncompressible) data at 73376008.2580645 bytes/sec
Wrote fixed (compressible) data at 101095833.6 bytes/sec
Compression: enabled
how can I make sure hardware compression is off?
On Apr 17, 2013, at 6:40 PM, Jean-Francois Malouin
wrote:
> * Abilio Carvalho [20130417 10:19]:
>> Well, since noone answered, I had to run amtapetype, so here it is if anyone
>> else needs it:
>>
>> define tapetype LTO6 {
>>comment "Created by amtapetype; compression enabled"
>>length 2442818848 kbytes
>>filemark 1806 kbytes
>>speed 74006 kps
>>blocksize 32 kbytes
>> }
>
> Hmmm, speed look way off. Native speed is 160MBs for LTO6...
> Did you disable hardware compression before running amtapetype?
> Also, you might want to test with larger blocksize, for LTO5 I use 2MB
> with good results
>
> hth,
> jf
>
>>
>>
>> On Apr 16, 2013, at 3:24 PM, Abilio Carvalho wrote:
>>
>>> Hi, just a quick question, does anyone have a tape type for an LTO6 drive?
>>> (Ideally an HP Ultrium 6 SCSI)
>>>
>>> Thanks
>>> Abilio
>>> **
>>> This email and any files transmitted with it are confidential and
>>> intended solely for the use of the individual or entity to whom they
>>> are addressed. If you have received this email in error please notify
>>> the system manager.
>>>
>>> This footnote also confirms that this email message has been swept by
>>> Clearswift for the presence of computer viruses.
>>>
>>> www.clearswift.com
>>> **
>>>
>>
Re: LTO6 tapetype
Well, since noone answered, I had to run amtapetype, so here it is if anyone
else needs it:
define tapetype LTO6 {
comment "Created by amtapetype; compression enabled"
length 2442818848 kbytes
filemark 1806 kbytes
speed 74006 kps
blocksize 32 kbytes
}
On Apr 16, 2013, at 3:24 PM, Abilio Carvalho wrote:
> Hi, just a quick question, does anyone have a tape type for an LTO6 drive?
> (Ideally an HP Ultrium 6 SCSI)
>
> Thanks
> Abilio
> **
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>
> This footnote also confirms that this email message has been swept by
> Clearswift for the presence of computer viruses.
>
> www.clearswift.com
> **
>
LTO6 tapetype
Hi, just a quick question, does anyone have a tape type for an LTO6 drive? (Ideally an HP Ultrium 6 SCSI) Thanks Abilio ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by Clearswift for the presence of computer viruses. www.clearswift.com **
Amanda on AIX
Hi. How current is the info on the wiki about compiling Amanda for AIX? It mentions that amanda-2.5.0p2 is the latest compilable version, as opposed to 2.5.1 and 2.5.2 which don't work, but has there been any progress on that since 2.6.x came out? Thank you 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.
Weird result from amflush
Hi. I got this wierd result when flushing yesterday's backups to tape this morning, as I'd stupidly forgotten to label the tape I put in the drive yesterday. I came in today, inserted the tape again, ran amlabel bbp_tape bbp_tape-08, and this was the outcome. Now I'm kind of unsure how to proceed, and what's gonna happen to my tape sequence when I do. Thanks Abilio Begin forwarded message: > From: Amanda > Date: May 28, 2009 9:25:32 AM GMT+02:00 > To: sysad...@bbp.ch > Subject: bbp_tape AMFLUSH MAIL REPORT FOR May 28, 2009 > > Hostname: zgluck > Org : bbp_tape > Config : bbp_tape > Date: May 28, 2009 > > The dumps were flushed to tape bbp_tape-08. > *** A TAPE ERROR OCCURRED: [runtapes volumes already written]. > There are 1G of dumps left in the holding disk. > Run amflush to flush them to tape. > > The next tape Amanda expects to use is: 1 new tape. > > FAILURE DUMP SUMMARY: > galadhrim.bbp.ch /dev/dsk/c1t0d0s0 lev 1: partial taper: No space > left on device > > > STATISTICS: > Total Full Incr. > > Estimate Time (hrs:min)0:00 > Run Time (hrs:min) 0:08 > Dump Time (hrs:min)0:00 0:00 0:00 > Output Size (meg) 0.00.00.0 > Original Size (meg) 0.00.00.0 > Avg Compressed Size (%) -- -- -- > Filesystems Dumped0 0 0 > Avg Dump Rate (k/s) -- -- -- > > Tape Time (hrs:min)0:05 0:00 0:05 > Tape Size (meg) 9492.40.0 9492.4 > Tape Used (%) 2.50.02.5 > (level:#disks ...) > Filesystems Taped 6 0 6 (1:6) > (level:#chunks ...) > Chunks Taped 6 0 6 (1:6) > Avg Tp Write Rate (k/s) 33290.0-- 33290.0 > > USAGE BY TAPE: > Label Time Size %NbNc > bbp_tape-08 0:059G2.5 6 6 > > > NOTES: > taper: tape bbp_tape-08 kb 9474350 fm 6 [OK] > taper: Will request retry of failed split part. > driver: Out of tapes; going into degraded mode. > > > DUMP SUMMARY: > DUMPER STATS > TAPER STATS > HOSTNAME DISKL ORIG-GB OUT-GB COMP% MMM:SS KB/s > MMM:SS KB/s > -- - > - > bluesock.bbp -iss/c0d0p1 NO FILE TO FLUSH > -- > bluesock.bbp -0-LogVol00 1 1-- FLUSH > 0:18 45677.7 > draco.bbp.ch -_RAID160p1 NO FILE TO FLUSH > -- > draco.bbp.ch -_RAID160p3 NO FILE TO FLUSH > -- > galadhrim.bb -k/c1t0d0s0 1 0-- FLUSH > 1:54 2152.6 TAPE-PARTIAL > galadhrim.bb -k/c1t0d0s1 NO FILE TO FLUSH > -- > galadhrim.bb -k/c1t0d0s3 NO FILE TO FLUSH > -- > galadhrim.bb -k/c1t1d0s0 NO FILE TO FLUSH > -- > galadhrim.bb -k/c1t1d0s1 1 1-- FLUSH > 0:28 53248.5 > galadhrim.bb -k/c1t2d0s0 NO FILE TO FLUSH > -- > galadhrim.bb -k/c1t3d0s1 NO FILE TO FLUSH > -- > gandalf.bbp. -k/c1t0d0s0 NO FILE TO FLUSH > -- > gandalf.bbp. -k/c1t0d0s3 NO FILE TO FLUSH > -- > gandalf.bbp. -k/c2t0d0s0 NO FILE TO FLUSH > -- > gandalf.bbp. -k/c2t0d1s0 NO FILE TO FLUSH > -- > gandalf.bbp. -k/c2t0d1s1 NO FILE TO FLUSH > -- > gandalf.bbp. -k/c2t0d1s3 1 1-- FLUSH > 0:28 50207.6 > gandalf.bbp. -k/c2t0d2s0 1 3-- FLUSH > 0:49 56076.1 > ronald.bbp.c -k/c2t0d0s0 NO FILE TO FLUSH > -- > ronald.bbp.c -/md/dsk/d1 NO FILE TO FLUSH > -- > ronald.bbp.c -/md/dsk/d2 NO FILE TO FLUSH > -- > ronald.bbp.c -/md/dsk/d5 NO FILE TO FLUSH > -- > ronald.bbp.c -/md/dsk/d6 NO FILE TO FLUSH > -- > zabbix.bbp.c -0-LogVol00 1 3-- FLUSH > 0:55 54860.3 > zgluck.bbp.c -iss/c0d0p1 NO FILE TO FLUSH > -- > zgluck.bbp.c -0-LogVol00 NO FILE TO FLUSH > -- > > (brought to you by Amanda version 2.6.1) --- This e-mail is strictly confidential and may be privileged. It is intended solely for the addressee. If you are not the intended recipient,
Re: PLEASE DISREGARD FOUND THE PROBLEM-amcheck error on local server
Sometimes this is the solution even when the service is NOT in maintenance mode. This was exactly what I had to do to fix the issue I had a couple days ago. Amandad just refused to run, believing it was being run as root even though the service was correctly configured to run as amandabackup. Turns out even though the inertd.conf from where I ran inetconv AND the manifest file that generates the smf database entry were both OK, but the database had some problem. Even changing the "user" property a couple times didn't help. I ended up having to do the same thing as Peter: fully remove the service, and recreate it from the manifest file. Abilio On May 20, 2009, at 10:08 PM, Dustin J. Mitchell wrote: > On Wed, May 20, 2009 at 3:13 PM, Peter Kunst > wrote: >> Whenever this happens again on Solaris 10, not getting a service >> out of >> maintenance mode even when amanda logs say all is ok, it might help >> to >> remove/delete this service and create it from scratch. >> >> I've traced one of those issues down to some kind of sqlite stuff >> getting confused (which is used by smf(5) IMHO). > > This is good info. Robert or Peter, do you want to add it to the > wiki? I feel like we should have a more extensive "Amanda on Solaris" > section, but I'm certainly unqualified to write it.. > > Dustin > > -- > Open Source Storage Engineer > http://www.zmanda.com --- 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
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/libex
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 >>> >>> >>>&g
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
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
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.
Amanda must be run as user amandabackup when using bsdtcp authentication
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.
Re: Timeout waiting for ACK
Thanks very much for the help, this is pretty urgent now. I tried doing that, here's the new problem: This is the inetadm output: bash-3.00# inetadm -l svc:/network/amanda/tcp:default 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 This is the /tmp/amanda/amandad/amandad..debug: 1241437297.941613: amandad: pid 12498 ruid 65502 euid 65502 version 2.6.1: start at Mon May 4 13:41:37 2009 1241437297.969516: amandad: security_getdriver(name=bsdtcp) returns ff31d388 1241437297.969689: amandad: version 2.6.1 1241437297.969702: amandad: build: VERSION="Amanda-2.6.1" 1241437297.969710: amandad:BUILT_DATE="Wed Apr 29 14:53:21 CEST 2009" 1241437297.969717: amandad:BUILT_MACH="sparc-sun- solaris2.10" BUILT_REV="1609" 1241437297.969724: amandad:BUILT_BRANCH="amanda-261" CC="cc" 1241437297.969731: amandad: paths: bindir="/bin" sbindir="/sbin" libexecdir="/libexec" 1241437297.969737: amandad:amlibexecdir="/libexec/amanda" mandir="/share/man" 1241437297.969744: amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" 1241437297.969750: amandad:CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/dsk/" 1241437297.969757: amandad:RDEV_PREFIX="/dev/rdsk/" DUMP="/ usr/sbin/ufsdump" 1241437297.969763: amandad:RESTORE="/usr/sbin/ufsrestore" VDUMP=UNDEF VRESTORE=UNDEF 1241437297.969769: amandad:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF 1241437297.969776: amandad:SAMBA_CLIENT="/usr/sfw/bin/ smbclient" 1241437297.969782: amandad:GNUTAR="/usr/sfw/bin/gtar" COMPRESS_PATH="/usr/bin/gzip" 1241437297.969789: amandad:UNCOMPRESS_PATH="/usr/bin/gzip" LPRCMD="/usr/bin/lp" 1241437297.969795: amandad: MAILER=UNDEF listed_incr_dir="/ var/amanda/gnutar-lists" 1241437297.969801: amandad: defs: DEFAULT_SERVER="ronald" DEFAULT_CONFIG="DailySet1" 1241437297.969808: amandad:DEFAULT_TAPE_SERVER="ronald" DEFAULT_TAPE_DEVICE="" 1241437297.969814: amandad:HAVE_MMAP NEED_STRSTR HAVE_SYSVSHM AMFLOCK_POSIX AMFLOCK_LOCKF 1241437297.969821: amandad:AMFLOCK_LNLOCK SETPGRP_VOID AMANDA_DEBUG_DAYS=4 BSD_SECURITY 1241437297.969827: amandad:USE_AMANDAHOSTS CLIENT_LOGIN="amandabackup" CHECK_USERID 1241437297.969834: amandad:HAVE_GZIP COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" 1241437297.969840: amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" 1241437297.981156: amandad: 172.22.0.23 doesn't resolve to itself, it resolves to :::172.22.0.23 1241437297.982066: amandad: pid 12498 finish time Mon May 4 13:41:37 2009 Here's the output of amcheck: sh-3.2$ amcheck -c bbp_tape Amanda Backup Client Hosts Check WARNING: ronald.bbp.ch: selfcheck request failed: EOF on read from ronald.bbp.ch Any hints on how to proceed? NOTE: Client has been compiled without IPv6, and server is the RHEL5 binary on the download page. On May 4, 2009, at 1:32 PM, Jean-Louis Martineau wrote: > Add '-auth=bsdtcp" in argument to amandad. > > Jean-Louis > > Abilio Carvalho wrote: >> I'm getting this message when trying to run amcheck. I've run >> amservice as is specified in the wiki page about this error, and >> I'm getting the same error, so it's a client issue. Can someone >> help me debug this? >> >> I've checked the client logs, and the only thing I can find that's >> relevant is on /tmp/amanda/amandad/amandad..debug: >> >> 1241424302.890797: amandad: pid 7809 ruid 65502 euid 65502 version >> 2.6.1: start at Mon May 4 10:05:02 2009 >> 1241424302.908306: amandad: security_getdriver(name=BSD) returns >> ff31d338 >> 1241424302.908442: amandad: version 2.6.1 >> 1241424302.908455: amandad: build: VERSION="Amanda-2.6.1" >> 1241424302.908464: amandad:BUILT_DATE="Wed Apr 29 >>
Timeout waiting for ACK
I'm getting this message when trying to run amcheck. I've run
amservice as is specified in the wiki page about this error, and I'm
getting the same error, so it's a client issue. Can someone help me
debug this?
I've checked the client logs, and the only thing I can find that's
relevant is on /tmp/amanda/amandad/amandad..debug:
1241424302.890797: amandad: pid 7809 ruid 65502 euid 65502 version
2.6.1: start at Mon May 4 10:05:02 2009
1241424302.908306: amandad: security_getdriver(name=BSD) returns
ff31d338
1241424302.908442: amandad: version 2.6.1
1241424302.908455: amandad: build: VERSION="Amanda-2.6.1"
1241424302.908464: amandad:BUILT_DATE="Wed Apr 29 14:53:21
CEST 2009"
1241424302.908472: amandad:BUILT_MACH="sparc-sun-
solaris2.10" BUILT_REV="1609"
1241424302.908479: amandad:BUILT_BRANCH="amanda-261" CC="cc"
1241424302.908485: amandad: paths: bindir="/bin" sbindir="/sbin"
libexecdir="/libexec"
1241424302.908492: amandad:amlibexecdir="/libexec/amanda"
mandir="/share/man"
1241424302.908498: amandad:AMANDA_TMPDIR="/tmp/amanda"
AMANDA_DBGDIR="/tmp/amanda"
1241424302.908505: amandad:CONFIG_DIR="/etc/amanda"
DEV_PREFIX="/dev/dsk/"
1241424302.908511: amandad:RDEV_PREFIX="/dev/rdsk/" DUMP="/
usr/sbin/ufsdump"
1241424302.908518: amandad:RESTORE="/usr/sbin/ufsrestore"
VDUMP=UNDEF VRESTORE=UNDEF
1241424302.908524: amandad:XFSDUMP=UNDEF XFSRESTORE=UNDEF
VXDUMP=UNDEF VXRESTORE=UNDEF
1241424302.908530: amandad:SAMBA_CLIENT="/usr/sfw/bin/
smbclient"
1241424302.908537: amandad:GNUTAR="/usr/sfw/bin/gtar"
COMPRESS_PATH="/usr/bin/gzip"
1241424302.908543: amandad:UNCOMPRESS_PATH="/usr/bin/gzip"
LPRCMD="/usr/bin/lp"
1241424302.908550: amandad: MAILER=UNDEF listed_incr_dir="/
var/amanda/gnutar-lists"
1241424302.908556: amandad: defs: DEFAULT_SERVER="ronald"
DEFAULT_CONFIG="DailySet1"
1241424302.908563: amandad:DEFAULT_TAPE_SERVER="ronald"
DEFAULT_TAPE_DEVICE=""
1241424302.908569: amandad:HAVE_MMAP NEED_STRSTR
HAVE_SYSVSHM AMFLOCK_POSIX AMFLOCK_LOCKF
1241424302.908575: amandad:AMFLOCK_LNLOCK SETPGRP_VOID
AMANDA_DEBUG_DAYS=4 BSD_SECURITY
1241424302.908582: amandad:USE_AMANDAHOSTS
CLIENT_LOGIN="amandabackup" CHECK_USERID
1241424302.908588: amandad:HAVE_GZIP COMPRESS_SUFFIX=".gz"
COMPRESS_FAST_OPT="--fast"
1241424302.908594: amandad:COMPRESS_BEST_OPT="--best"
UNCOMPRESS_OPT="-dc"
1241424302.908852: amandad: dgram_recv(dgram=ff4c, timeout=0,
fromaddr=ff343338)
1241424302.909008: amandad: (sockaddr_in *)ff343338 = { 0, 0, 0.0.0.0 }
1241424312.470249: amandad: dgram_recv(dgram=ff4c, timeout=0,
fromaddr=ff343338)
1241424312.470327: amandad: (sockaddr_in *)ff343338 = { 0, 0, 0.0.0.0 }
1241424322.470941: amandad: dgram_recv(dgram=ff4c, timeout=0,
fromaddr=ff343338)
1241424322.471014: amandad: (sockaddr_in *)ff343338 = { 0, 0, 0.0.0.0 }
plus a lot more of those timeouts.
Here's the amanda_client.conf and inetd service setup. I'm guessing
that there's something wrong with the inetadm output, but I can't
generate a set of values that work. Adding the -auth=bsdtcp line to /
etc/inetd.conf and reconverting, for example, doesn't work at all.
#amanda-client.conf - Amanda client configuration file.
conf"bbp_tape"
index_server"zgluck"
tape_server "zgluck"
# auth - authentication scheme to use between server and client.
# Valid values are 'bsdtcp' or 'ssh'
auth"bsdtcp"
# ssh keys file if ssh auth is used
ssh_keys"/var/lib/amanda/.ssh/id_rsa_amrecover"
---
bash-3.00# inetadm -l svc:/network/amanda/tcp:default
SCOPENAME=VALUE
name="amanda"
endpoint_type="stream"
proto="tcp"
isrpc=FALSE
wait=FALSE
exec="/libexec/amanda/amandad"
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
---
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.
Can't connect to client on Solaris 10
Hi. I tried to install amanda on a solaris 10 box (sparc) but it's not responding to amchecks. amcheck's log gives: 1241020517.034653: amcheck-clients: make_socket opening socket with family 2 1241020517.034674: amcheck-clients: connect_port: Try port 703: available - Success 1241020517.035322: amcheck-clients: connect_portrange: Connect from 0.0.0.0.703 failed: Connection refused 1241020517.035333: amcheck-clients: connect_portrange: connect to 193.73.134.4.10080 failed: Connection refused 1241020517.035347: amcheck-clients: stream_client: Could not bind to port in range 700-710. 1241020517.035361: amcheck-clients: security_seterror(handle=0x8fe73b0, driver=0x2a9620 (BSDTCP) error=Connection refused) 1241020517.035370: amcheck-clients: security_close(handle=0x8fe73b0, driver=0x2a9620 (BSDTCP)) 1241020517.035378: amcheck-clients: security_stream_close(0x8ff1900) 1241020517.271757: amcheck-server: changer: << EXITSTATUS 0 1241020517.271782: amcheck-server: changer: << current 99 0 1 1241020517.271799: amcheck-server: changer_query: changer return was 99 0 1 1241020517.271831: amcheck-server: changer_query: searchable = 1 1241020517.271843: amcheck-server: changer_find: looking for NULL changer is searchable = 1 1241020517.271856: amcheck-server: changer: >> -slot current 1241020522.034995: amcheck-clients: security_handleinit(handle=0x8fe73b0, driver=0x2a9620 (BSDTCP)) 1241020522.036002: amcheck-clients: security_streaminit(stream=0x8ff1900, driver=0x2a9620 (BSDTCP)) 1241020522.037590: amcheck-clients: connect_port: Skip port 700: owned by epp. 1241020522.038124: amcheck-clients: connect_port: Skip port 701: owned by lmp. 1241020522.038651: amcheck-clients: connect_port: Skip port 702: owned by iris-beep. 1241020522.041874: amcheck-clients: make_socket opening socket with family 2 1241020522.041895: amcheck-clients: connect_port: Try port 703: available - Success 1241020522.042523: amcheck-clients: connect_portrange: Connect from 0.0.0.0.703 failed: Connection refused 1241020522.042535: amcheck-clients: connect_portrange: connect to 193.73.134.4.10080 failed: Connection refused 1241020522.042549: amcheck-clients: stream_client: Could not bind to port in range 700-710. 1241020522.042563: amcheck-clients: security_seterror(handle=0x8fe73b0, driver=0x2a9620 (BSDTCP) error=Connection refused) 1241020522.042602: amcheck-clients: security_close(handle=0x8fe73b0, driver=0x2a9620 (BSDTCP)) 1241020522.042611: amcheck-clients: security_stream_close(0x8ff1900) On the client, /etc/services has the following lines: amanda 10080/udp amandaidx 10082/tcp amidxtape 10083/tcp and inetadm -l svc:/network/amanda/udp:default reports the following: SCOPENAME=VALUE name="amanda" endpoint_type="dgram" proto="udp" isrpc=FALSE wait=TRUE exec="/libexec/amanda/amandad" 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 However, netstat -a | grep amanda OR netstat -a | grep 1008 returns nothing. I have no idea how to proceed anymore. Can anyone 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.
Newbie question: binary packages
Hi. I'm just starting to use amanda, and wanted to follow the basic instructions on the website to get a first version up and running to play with. However, I will eventually have to install it on an AIX machine, for which no binary packages exist. So my question, and I'm sorry in advance that the answer is probably basic, is how I can find out which options I should use when configuring and building the source packages on the AIX machine so that it conforms completely to the options on the prebuilt packages. Thank you 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.
