Package: amanda-client
Version: 1:3.3.1-4
Severity: normal

Since switching to bsdtcp, routine security scans have caused amandad to get
stuck doing this:

read(0, "", 253605)                     = 0
poll([{fd=0, events=POLLIN}], 1, -1)    = 1 ([{fd=0, revents=POLLIN}])
read(0, "", 253605)                     = 0
poll([{fd=0, events=POLLIN}], 1, -1)    = 1 ([{fd=0, revents=POLLIN}])
read(0, "", 253605)                     = 0
poll([{fd=0, events=POLLIN}], 1, -1)    = 1 ([{fd=0, revents=POLLIN}])
read(0, "", 253605)                     = 0
poll([{fd=0, events=POLLIN}], 1, -1)    = 1 ([{fd=0, revents=POLLIN}])
read(0, "", 253605)                     = 0
poll([{fd=0, events=POLLIN}], 1, -1)    = 1 ([{fd=0, revents=POLLIN}])
read(0, "", 253605)                     = 0
poll([{fd=0, events=POLLIN}], 1, -1)    = 1 ([{fd=0, revents=POLLIN}])
read(0, "", 253605)                     = 0
poll([{fd=0, events=POLLIN}], 1, -1)    = 1 ([{fd=0, revents=POLLIN}])
read(0, "", 253605)                     = 0
poll([{fd=0, events=POLLIN}], 1, -1)    = 1 ([{fd=0, revents=POLLIN}])
read(0, "", 253605)                     = 0
poll([{fd=0, events=POLLIN}], 1, -1)    = 1 ([{fd=0, revents=POLLIN}])
read(0, "", 253605)                     = 0
poll([{fd=0, events=POLLIN}], 1, -1)    = 1 ([{fd=0, revents=POLLIN}])
read(0, "", 253605)                     = 0
poll([{fd=0, events=POLLIN}], 1, -1)    = 1 ([{fd=0, revents=POLLIN}])
read(0, "", 253605)                     = 0
poll([{fd=0, events=POLLIN}], 1, -1)    = 1 ([{fd=0, revents=POLLIN}])
read(0, "", 253605)                     = 0
poll([{fd=0, events=POLLIN}], 1, -1)    = 1 ([{fd=0, revents=POLLIN}])
read(0, "", 253605)                     = 0
poll([{fd=0, events=POLLIN}], 1, -1)    = 1 ([{fd=0, revents=POLLIN}])
read(0, "", 253605)                     = 0
poll([{fd=0, events=POLLIN}], 1, -1)    = 1 ([{fd=0, revents=POLLIN}])
read(0, "", 253605)                     = 0

The relevant amandad process uses up all the CPU time that it can, taking the
load average to 1.

The scan is coming from a system which is not listed in /etc/amandahosts but
which tcp_wrappers will allow to connect.

I hope to have packet captures that will cause this once I can coordinate with
the relevant folks to have tcpdump running during a scan.

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages amanda-client depends on:
ii  amanda-common  1:3.3.1-4
ii  libc6          2.13-37
ii  libcurl3       7.26.0-1+wheezy1
ii  libglib2.0-0   2.33.12+really2.32.4-3
ii  libreadline6   6.2+dfsg-0.1
ii  libssl1.0.0    1.0.1c-4

amanda-client recommends no packages.

Versions of packages amanda-client suggests:
pn  dump       <none>
pn  gnuplot    <none>
ii  smbclient  2:3.6.6-5

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to