Hi everybody, I dare to write again with this unsolved problem because the success that has obtained a (hope) similar problem related the the setuid (amrecover: Error binding socket: Permission denied). I still have a pure Linux Debian environment with three workstations, one used as Backup Master the other two ar clients, that presents the peculiarity that: 1) All backups occurr correctly 2) one Client can run amrecover (it runs kernel 2.2.16) 3) one Client (who runs kernel 2.2.14) shows the message: AMRECOVER Version 2.4.1p1. Contacting server on localhost ... amrecover: Error binding socket: Cannot assign requested address The amrecover.debug log of the faulty one shows: amrecover: debug 1 pid 499 ruid 0 euid 0 start time Tue Nov 14 10:39:46 2000 Error binding socket: Cannot assign requested address amrecover: pid 499 finish time Tue Nov 14 10:39:46 2000 The Amanda version is that comes from the Debian Distribution site and is the "2.4.1p1-12" Is there any relationship with the kernel version? OK I could upgrade the kernel to the 2.2.16 release but I would like to now if this "IS the solution" or only a wasting of time Please, those who know how this software was made, help. Thank you. Marco Bagni
