Amanda-Users

Re: Error redirecting stderr to fd 52

2009-08-24 14:17:48
Subject: Re: Error redirecting stderr to fd 52
From: John Hein <jhein AT timing DOT com>
To: Jean-Louis Martineau <martineau AT zmanda DOT com>
Date: Mon, 24 Aug 2009 10:56:49 -0600
Jean-Louis Martineau wrote at 11:48 -0400 on Aug 24, 2009:
 > John Hein wrote:
 > > On a 2.6.1b1 client ...
 > >   
 > Hmm, beta software ...
 > 
 > It's not fixed in 2.6.1 neither in 2.6.1p1.
 > 
 > You must use the latest 2.6.1p1 snapshot from 
 > http://www.zmanda.com/community-builds.php

Building a new version now.

Another interesting note.  On the client in question, amandad is still
running, but it shouldn't be.  It's got a couple unreaped zombies and
is waiting in select.

ps awwx -o user,pid,ppid,start,stat,wchan,command | grep backup
backup       37628 60010  4:43AM Z    -      <defunct>
backup       37629 60010  4:43AM Z    -      <defunct>
backup       60010 23993  7:01PM Ss   select amandad


lsof shows quite a few file descriptors still open.

COMMAND   PID   USER   FD   TYPE       DEVICE SIZE/OFF    NODE NAME
amandad 60010 backup    0u  IPv4   0xc87f5438      0t0     UDP *:amanda
amandad 60010 backup    1u  IPv4   0xc87f5438      0t0     UDP *:amanda
amandad 60010 backup    2u  IPv4   0xc87f5438      0t0     UDP *:amanda
amandad 60010 backup    4u  IPv4   0xcdd09bf4      0t0     UDP *:58068
amandad 60010 backup   10w  VREG         0,88   107863  331113 / -- 
amandad/amandad.20090823190102.debug
amandad 60010 backup   21u  PIPE   0xcb0064c8    16384         ->0xcb006580
amandad 60010 backup   22u  PIPE   0xc916a990    16384         ->0xc916aa48
amandad 60010 backup   23u  PIPE   0xcd629990    16384         ->0xcd629a48
amandad 60010 backup   24u  PIPE   0xce8a8990    16384         ->0xce8a8a48
amandad 60010 backup   28u  PIPE   0xc86b47f8    16384         ->0xc86b48b0
amandad 60010 backup   29u  IPv4   0xce6f63a0      0t0     TCP *:6108 (LISTEN)
amandad 60010 backup   30u  PIPE   0xc8d2f330    16384         ->0xc8d2f3e8
amandad 60010 backup   31u  PIPE   0xc9466198    16384         ->0xc9466250
amandad 60010 backup   33u  PIPE   0xca15c330    16384         ->0xca15c3e8
amandad 60010 backup   37u  IPv4                   0t0     TCP no PCB, 
CANTSENDMORE, CANTRCVMORE
amandad 60010 backup   39u  PIPE   0xcdeb4cc0    16384         ->0xcdeb4d78
amandad 60010 backup   40u  PIPE   0xc9c307f8    16384         ->0xc9c308b0
amandad 60010 backup   42u  PIPE   0xc96317f8    16384         ->0xc96318b0
amandad 60010 backup   44u  PIPE   0xc9c30660    16384         ->0xc9c30718
amandad 60010 backup   46u  PIPE   0xc9c1d330    16384         ->0xc9c1d3e8
amandad 60010 backup   47u  PIPE   0xc914e718        0         ->0xc914e660
amandad 60010 backup   48u  PIPE   0xcc4dd4c8    16384         ->0xcc4dd580
amandad 60010 backup   49u  PIPE   0xc96be7f8    16384         ->0xc96be8b0
amandad 60010 backup   50u  PIPE   0xce8a8330    16384         ->0xce8a83e8
amandad 60010 backup   51u  PIPE   0xc914e580        0         ->0xc914e4c8
amandad 60010 backup   52u  PIPE   0xc914ecc0    16384         ->0xc914ed78
amandad 60010 backup   60u  PIPE   0xc8e10330    16384         ->0xc8e103e8
amandad 60010 backup   61u  PIPE   0xcc37fb28    16384         ->0xcc37fbe0
amandad 60010 backup   62u  PIPE   0xce649660    16384         ->0xce649718
amandad 60010 backup   63u  PIPE   0xcaa00990    16384         ->0xcaa00a48
amandad 60010 backup   64u  PIPE   0xc912f660    16384         ->0xc912f718
amandad 60010 backup   65u  PIPE   0xc90f1cc0    16384         ->0xc90f1d78

A few seconds of tracing the process shows..

 60010 amandad  RET   poll 0
 60010 amandad  CALL  gettimeofday(0xbfbfea88,0)
 60010 amandad  RET   gettimeofday 0
 60010 amandad  CALL  gettimeofday(0xbfbfea88,0)
 60010 amandad  RET   gettimeofday 0
 60010 amandad  CALL  poll(0x8052600,0x1,0x7530)


<Prev in Thread] Current Thread [Next in Thread>