Nathan, I will try with the server estimate, also I am able to run calcsize manually with no problem. I will try this now and report back. Thanks Robert
-----Original Message----- From: [email protected] <[email protected]> On Behalf Of Nathan Stratton Treadway Sent: Thursday, September 19, 2019 9:56 PM To: [email protected] Subject: Re: amandad defunct on client calcsize/sendsize hung On Thu, Sep 12, 2019 at 17:48:28 +0000, Robert Reilly wrote: > I did a while loop started the backup and I see that noop is also > defunct but dose get cleaned up > > backup 8919 8829 0 17:45 ? 00:00:00 sshd: backup@notty > backup 8928 8919 0 17:45 ? 00:00:00 /usr/lib/amanda/amandad > -auth=ssh > backup 9056 8928 0 17:45 ? 00:00:00 [noop] <defunct> > backup 9057 8928 0 17:45 ? 00:00:00 [amandad] <defunct> (I am not sure how long you had between cycles of your while loop, but I as far as I can tell it's normal operation for the spawned "noop" process to remain defunct for a short period of time while the main amandad process copies the noop process's data back over the network to the server, but then once that copying has finished the "noop" process is cleaned up. Probably the same thing would happen with the "sendsize" process -- but since that is never finishing you never get to the point that there's a defunct sendsize process. Then defunct "amandad" processes, on the other hand, seem to be subproceses amandad spawns of itself to offload some work -- and as far as I can tell those may not get cleaned up until amandad as a whole exits.) Nathan ---------------------------------------------------------------------------- Nathan Stratton Treadway - [email protected] - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
