Package: amanda-client
Version: 1:2.5.2p1-3
Severity: important

With the 2.5.2 client, I'm running:

        amrecover -C normal -s b.example.com -t b.example.com -d /dev/ndat

And I get:

AMRECOVER Version 2.5.2p1. Contacting server on b.example.com ...
[request failed: error sending REQ: send REQ to b.example.com failed: Socket 
operation on non-socket]

When I run the same command on b.example.com, running 2.5.1, I get:

AMRECOVER Version 2.5.1p3. Contacting server on b.example.com ...
220 b.example.com AMANDA index server (2.5.1p3) ready.

So there seems to be an important bug somewhere in the 2.5.2 code.
Both the client and the server run the same Linux kernel (2.6.25.4)
and the same Debian system (apart from a few differences, such as
AMANDA versions, on purpose, since 2.5.2 is not working fine).

Note that I have NO problems backuping my clients (who all use 2.5.2)
from my 2.5.1 server...  But then it is the server initiating the
connection.  When 2.5.2 is initiating the connection, apparently
it does not work.  It probably passes the wrong file descriptor to
some routine, as the error message "Socket operation on non-socket"
suggests...

Maybe you should ask the upstream developers about it?

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.25.4 (SMP w/2 CPU cores)
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages amanda-client depends on:
ii  amanda-common             1:2.5.2p1-3    Advanced Maryland Automatic Networ
ii  libc6                     2.7-2          GNU C Library: Shared libraries
ii  libncurses5               5.6+20071215-1 Shared libraries for terminal hand
ii  libreadline5              5.2-3          GNU readline and history libraries

amanda-client recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to