Re: SV: FAILED [spawn /bin/gzip: dup2 out: Bad file descriptor] on 2.6.1p2

2010-05-03 Thread Volker Pallas
Hi,

just wanted to send you an update on this issue. Switching to
auth=bsdtcp completely solved my problem.
The working line from /etc/inetd.conf (for openbsd-inetd, and the
amanda-user being "backup") is:

amanda stream tcp nowait backup /usr/lib/amanda/amandad amandad
-auth=bsdtcp amdump amindexd amidxtaped

During the last 7 days there hasn't been a single failed backup on any
of my previously affected systems.

Thank you for your support!

Volker





Re: SV: FAILED [spawn /bin/gzip: dup2 out: Bad file descriptor] on 2.6.1p2

2010-04-21 Thread Dustin J. Mitchell
On Wed, Apr 21, 2010 at 11:04 AM, Volker Pallas  wrote:
> Is auth=bsdtcp mandatory?

If you want to switch to bsdtcp, then yes.  You'll also need to change
your (x)inetd configuration accordingly.  The amanda-auth(7) manpage
may be of use to you in figuring the whole thing out.

DUstin

-- 
Open Source Storage Engineer
http://www.zmanda.com


Re: SV: FAILED [spawn /bin/gzip: dup2 out: Bad file descriptor] on 2.6.1p2

2010-04-21 Thread Volker Pallas
Hello again,

unfortunately my dup2-problems reappeared after that one night when it
was working, I still have the same error on my machines.

so far I have only changed the entry in /etc/inetd.conf (I'm using
openbsd-inetd) from:
amanda dgram udp wait backup /usr/lib/amanda/amandad amandad -auth=bsd
amdump amindexd amidxtaped
to:
amanda dgram tcp wait backup /usr/lib/amanda/amandad amandad -auth=bsd
amdump amindexd amidxtaped
and of course restarted the inetd process.

Are there any other places I need to adapt when "completely switching
amanda to tcp"?
Is auth=bsdtcp mandatory?

Thanks you,

Volker

Volker Pallas wrote:
> Gunnarsson, Gunnar wrote:
>   
>> Switching to tcp instead of using udp cured those problems.
>> 
>>>  Hi,
>>>
>>> I'm having a bit of a problem on *some* servers concerning failed 
>>> backups with the error message:
>>> lev # FAILED [spawn /bin/gzip: dup2 out: Bad file descriptor]
>>> 
>>>   
>> Gunnar had a similar problem - maybe his experience will help?
>>
>>   http://www.mail-archive.com/amanda-users@amanda.org/msg42119.html
>>
>> Dustin
>>   
>> 


Re: SV: FAILED [spawn /bin/gzip: dup2 out: Bad file descriptor] on 2.6.1p2

2010-04-16 Thread Volker Pallas
Thank you Gunnar and Dustin!
I switched to tcp on one host yesterday and it worked fine so far. I
will observe this for the next couple of days and report back to you.

Thank you again for your fast response,
Volker

Gunnarsson, Gunnar wrote:
> Switching to tcp instead of using udp cured those problems.
>>  Hi,
>>
>> I'm having a bit of a problem on *some* servers concerning failed 
>> backups with the error message:
>> lev # FAILED [spawn /bin/gzip: dup2 out: Bad file descriptor]
>> 
>
> Gunnar had a similar problem - maybe his experience will help?
>
>   http://www.mail-archive.com/amanda-users@amanda.org/msg42119.html
>
> Dustin
>   


SV: FAILED [spawn /bin/gzip: dup2 out: Bad file descriptor] on 2.6.1p2

2010-04-13 Thread Gunnarsson, Gunnar
Switching to tcp instead of using udp cured those problems.

-- GG 

-Ursprungligt meddelande-
Från: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] För 
Dustin J. Mitchell
Skickat: den 13 april 2010 18:11
Till: Volker Pallas
Kopia: amanda-users@amanda.org
Ämne: Re: FAILED [spawn /bin/gzip: dup2 out: Bad file descriptor] on 2.6.1p2

On Mon, Apr 12, 2010 at 4:48 AM, Volker Pallas  wrote:
>  Hi,
>
> I'm having a bit of a problem on *some* servers concerning failed 
> backups with the error message:
> lev # FAILED [spawn /bin/gzip: dup2 out: Bad file descriptor]

Gunnar had a similar problem - maybe his experience will help?

  http://www.mail-archive.com/amanda-users@amanda.org/msg42119.html

Dustin

--
Open Source Storage Engineer
http://www.zmanda.com




Re: FAILED [spawn /bin/gzip: dup2 out: Bad file descriptor] on 2.6.1p2

2010-04-13 Thread Dustin J. Mitchell
On Mon, Apr 12, 2010 at 4:48 AM, Volker Pallas  wrote:
>  Hi,
>
> I'm having a bit of a problem on *some* servers concerning failed
> backups with the error message:
> lev # FAILED [spawn /bin/gzip: dup2 out: Bad file descriptor]

Gunnar had a similar problem - maybe his experience will help?

  http://www.mail-archive.com/amanda-users@amanda.org/msg42119.html

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com



FAILED [spawn /bin/gzip: dup2 out: Bad file descriptor] on 2.6.1p2

2010-04-12 Thread Volker Pallas
 Hi,

I'm having a bit of a problem on *some* servers concerning failed
backups with the error message:
lev # FAILED [spawn /bin/gzip: dup2 out: Bad file descriptor]

usually these failed backups are "successfully retried", but sometimes I
get the same error twice and the backup for the day fails completely.

This only happens on servers backing up windows clients via
smb-share/"smbclient" which are running amanda version 2.6.1p2. Servers
with Linux clients are not affected and other versions of amanda backing
up windows clients are also not affected. Additionally, as I said, this
does not happen all the time and not always with the same clients.

I verified amanda-user-access to /dev/null and I would rule out that the
file systems are suddenly corrupt on all these different servers.

I would like to know what this error message means and how to fix it or
maybe you can point me in the right direction.

If you need any more information, please tell me.
Thank you in advance,
Volker

some detailed output from sendbackup.*.debug (this time failed and then
retried successfully):
1270767389.972013: sendbackup: start: serverfqdn://ipaddr/backupshare$ lev 1
1270767389.972046: sendbackup: pipespawnv: stdoutfd is 50
1270767389.972078: sendbackup: Spawning "/bin/gzip /bin/gzip --fast" in
pipeline
1270767389.972196: sendbackup: gnutar: pid 24511:
/bin/gzip1270767389.972213: sendbackup: pid 24511: /bin/gzip --fast
1270767389.972347: sendbackup: critical (fatal): error [spawn /bin/gzip:
dup2 out: Bad file descriptor]
1270767389.972928: sendbackup: gnutar: backup of \\ipaddr\backupshare$
1270767389.973070: sendbackup: pipespawnv: stdoutfd is 6
1270767389.973188: sendbackup: Spawning "/usr/bin/smbclient smbclient
"ipaddr\\backupshare$" -U username -E -d0 -Tqcg -" in pipeline
1270767389.976787: sendbackup: Started index creator: "/bin/tar -tf -
2>/dev/null | sed -e 's/^\.//'"
1270767389.979324: sendbackup: gnutar: /usr/bin/smbclient: pid 24513
1270767389.979343: sendbackup: Started backup

software versions on affected servers:
the OS is Debian Lenny
amanda 2.6.1p2
gzip 1.3.12-6+lenny1
tar 1.20-1
smbclient 3.2.5-4lenny9