Package: ircd-ratbox
Version: 3.0.8.dfsg-2
Severity: important

Dear Maintainer,

After upgrading to 3.0.8-dfsg-2, I noticed connecting to the IRC server was
very slow and resulted in hostnames not being (reverse) resolved.

Upon inspection, it seemed that the ircd resolver daemon was using a lot of
CPU (100% in top). A systrace did not yield anything, but an ltrace showed a
continuous stream of the same line:

rb_get_pseudo_random(0x7fffa62abc86, 2, 0x7f583268fba0, 0) = 1

(I'll get back to this later).

I tried killing the ircd resolver daemon (had to kill it with SIGKILL) and it
came back at 0% CPU usage. However, everytime a client connected, the same
thing happened (cpu to 100%, ip not reverse resolved).

I did a quick check in the source code and it seemed that this function was
called in a tight loop if the random number that was returned is always
0xffff (a 16-bit short was requested).


ADDITIONAL INFORMATION
 * tested with 3.0.7.dfsg-3, does NOT suffer from this problem
 * tested on two different machines, both virtualized (one OpenVZ, one LXC)
   (I don't know if it matters, but I included it for completeness).

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
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 ircd-ratbox depends on:
ii  libc6              2.19-7
ii  libgnutls-deb0-28  3.2.15-3
ii  libltdl7           2.4.2-1.7
ii  libsqlite3-0       3.8.5-2
ii  lsb-base           4.1+Debian13
ii  multiarch-support  2.19-7

ircd-ratbox recommends no packages.

Versions of packages ircd-ratbox suggests:
pn  ntp | openntpd | time-daemon  <none>

-- Configuration Files:
/etc/default/ircd-ratbox changed [not included]

-- 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