Package: bandersnatch
Version: 0.4-1.1
Severity: important

Bandersnatch will stop logging frequently.  After a couple of days of 
running, it just won't do anything anymore.  Its process is still 
running, but no new entries appear in the DB, and 
/etc/init.d/bandersnatch won't have any impact either.  Killing the 
process and /etc/init.d/bandersnatch will cause it to start logging 
again, but it won't last long.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable'), (99, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages bandersnatch depends on:
ii  libclass-dbi-perl           3.0.15-2     A convenient abstraction layer to 
ii  libdbi-perl                 1.53-1       Perl5 database interface by Tim Bu
ii  libnet-jabber-perl          2.0-3        Perl modules for accessing the Jab
ii  libxml-stream-perl          1.22-2       Perl module for accessing XML Stre
ii  perl                        5.8.8-7etch1 Larry Wall's Practical Extraction 

Versions of packages bandersnatch recommends:
pn  bandersnatch-frontend      <none>        (no description available)
ii  ejabberd                   1.1.2-6       Distributed, fault-tolerant Jabber
ii  mysql-client               5.0.32-7etch3 mysql database client (meta packag
ii  mysql-client-5.0 [mysql-cl 5.0.32-7etch3 mysql database client binaries
ii  mysql-server               5.0.32-7etch3 mysql database server (meta packag
ii  mysql-server-5.0 [mysql-se 5.0.32-7etch3 mysql database server binaries

-- no debconf information



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

Reply via email to