Package: exim4
Version: 4.68-2
Followup-For: Bug #463929
Due to other packages on my machine (apache etc) I can't easily do the
libpq5 downgrade. Has anyone had any success with going to
libpq5_8.3.0-1 from unstable?
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
Package: rtorrent
Version: 0.7.8-1
Severity: normal
The syntax of the schedule lines in the .rtorrent.rc has changed with
this release. The sample .rtorrent.rc has a (commented out) sample of
using the schedule line:
schedule = ratio,60,60,stop_on_ratio=200,200M,2000
This line doesn't work and
Package: kernel
Version: 2.6.21-2
Severity: serious
--- Please enter the report below this line. ---
When running under 2.6.21-2 in testing, the 3c509x network card
intermittently locks up after a few hours.
When shutting down for a reboot, messages appear on the console like
interrupt posted
Package: mediawiki1.9
Version: 1.9.3-2
Severity: important
Installation of mediawiki1.9 failed on my system. Output is:
No packages found matching mediawiki1.7.
Selecting previously deselected package php5.
Unpacking php5 (from .../archives/php5_5.2.0-10_all.deb) ...
Selecting previously
:
Hi !
Le Tuesday 24 April 2007 10:18:40 Philip Craig, vous avez écrit :
Installation of mediawiki1.9 failed on my system. Output is:
Where does it fail ?
Romain
Package: slimserver
Version: 6.3.0-4
Severity: normal
slimserver 6.5.0 was released 2006-09-19
Adds support for the Transporter product and also upgrades for v2 and v3
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
it seemed to be the apache.pem key cert. Not the config files.
Andreas Barth wrote:
Hi,
* Philip Craig ([EMAIL PROTECTED]) [060830 10:43]:
I have more info. I did a stack trace with apache-ssl.dbg built from
source, and it was crashing in libssl.
But this didn't help.
What *did* help
Package: apache-ssl
Version: 1.3.34-4
Followup-For: Bug #385004
Mine crashes in the same (nasty) way
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
I have now built and installed apache-ssl and apache-common from source
using the previous version in testing, 1.34-2. This still fails with the
same error, so I guess it must actually be a bug in a dependency? As
apache is fine, I guess it may be some ssl dependency. Any ideas what
this could
is that possibly just forcing a regeneration of the certs
would also have worked.
Philip Craig wrote:
I have now built and installed apache-ssl and apache-common from
source using the previous version in testing, 1.34-2. This still fails
with the same error, so I guess it must actually be a bug
Package: jwchat
Version: 1.0beta2-6
Severity: grave
Justification: renders package unusable
I can't install jwchat (never tried before). Here is the log:
Setting up jwchat (1.0beta2-6) ...
Creating config file /etc/jwchat/config.js with new version
Creating config file
Package: slimserver
Version: 6.2.1-3
Severity: wishlist
The newer 6.3.0 stable release is out and it's got lots of nice features :)
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Shell:
Package: wnpp
Severity: wishlist
Owner: Philip Craig [EMAIL PROTECTED]
* Package name: alienbbc
Version : 1.0.5
Upstream Author : Jules Taplin [EMAIL PROTECTED]
* URL : http://www.x2systems.com/AlienBBC/
* License : GPL
Programming Lang: Perl
Description
Al wrote:
Hi Phil
How many servers do you have linked?
2
I presume you're running with zipped links enabled, are you
specifically enabling zipped links in ircd.conf? I.E. they are
enabled within the ircd itself, but are you enabling compression of
each individual server link? If so,
Package: rageircd
Version: 2.0.1-4
Followup-For: Bug #331089
==8384== Memcheck, a memory error detector.
==8384== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al.
==8384== Using LibVEX rev 1471, a library for dynamic binary translation.
==8384== Copyright (C) 2004-2005, and GNU
It's still up and has stayed up for upwards of 100 days when run under
valgrind (until reboot). It still crashes every few hours when run normally.
I'm not sure that I can offer much more. Maybe the author can?
Marc Haber wrote:
Hi,
On Tue, Nov 01, 2005 at 05:15:47PM +, Philip Craig
Package: logcheck-database
Version: 1.2.42
Severity: normal
Tags: patch
I had to change the case of the dovecot login line or it was generating
spurious logchecks. Here is the version after my change:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dovecot: (imap|pop3)-login: Login:
user=[.[:alnum:[EMAIL
Package: rageircd
Version: 2.0.1-1
Followup-For: Bug #331089
As reported earlier, running rageircd under valgrind is a workaround to
stop it crashing. And, it works great so far, 23 days continuous uptime
and counting
-- System Information:
Debian Release: testing/unstable
APT prefers
Running with assert switched on and debugging at level 9, -O2 and not
under valgrind gives the usual crash, this time after 3 hours 14 minutes.
It is the usual crash in m_away.c:88
Here is the tail of the output:
ENGINE: send queued for [vangogh.ath.cx]
Parsing [EMAIL PROTECTED]: :!4000 u
Actually, not quite.
The situation is:
If I run it -O0 or the normal -O2 via the normal means (command line or
debian init.d script) then it crashes in 3-6 hours.
If I run it under valgrind as either -O2 or -O0, then it stays up for
days!! The first run stayed up 1 day and 1 hour before I
I compiled with -O0 in preparation for valgrind. That alone appears to
have fixed the issue, in that for the first time, the daemon has stayed
up for 15 hours. And with no valgrind-reported errors.
I'm now running standalone just to see if it is really fixed. So let me
get back to you in a
Alasdair McWilliam wrote:
Rather an interesting one.
What strikes me is that AWAY verifies sptr-user is non-NULL before
it does anything. However just because sptr-user is non-NULL does
not mean it's valid memory space. Methinks a heap corruption.
What are you doing on the server prior
Do you have the opportunity to retry on a known good machine, or at
least with the crashing one in single CPU mode?
I have booted the machine into single CPU mode, same kernel version. The
behaviour is exactly the same. One time it again broke at m_away.c line
88. Another time it broke at
Marc Haber wrote:
One time it again broke at m_away.c line
88. Another time it broke at m_away.c line 68
That, however, looks like that we have either _two_ bugs, or you have
a hardware issue. A single bug would most probnably show at the same
point .
Reading the code, it looked like it
Package: rageircd
Version: 2.0.1-1
Followup-For: Bug #331089
After a few hours, a debug version of the current release ended up here:
(gdb) run -t -V -c /etc/rageircd/rageircd.conf
Starting program: /usr/bin/rageircd -t -V -c /etc/rageircd/rageircd.conf
Attempting to open config file
Package: rageircd
Version: 2.0.1-1
Severity: important
Hi, I have rageircd setup on this machine to autoconnect to another
server, using this machine as a backup in case of connectivity loss.
There hasn't been a loss of connectivity so far as I know, but the
daemon quits with no log message, not
Package: ircd-hybrid
Version: 1:7.0.3-3
Followup-For: Bug #300638
After a few messages, ircd-hybrid segfaults on amd64. I have the
following in /var/log/messages:
Sep 29 12:29:08 vangogh kernel: ircd-hybrid[19420]: segfault at
0025 rip 2af839d0 rsp 7fb6dc98 error 4
Package: rageircd
Version: 2.0.1-1
Severity: important
On my system, rageircd starts up but doesn't even beind to 6667,
according to netstat. The /etc/init.d/rageircd stop script also doesn't
kill the daemon successfully. The package is unusable.
-- System Information:
Debian Release:
Package: rageircd
Version: 2.0.1-1
Followup-For: Bug #330887
listen * {
range 6660-6669;
port 7000;
};
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh
:
On Fri, Sep 30, 2005 at 11:38:10AM +0100, Philip Craig wrote:
listen * {
range 6660-6669;
port 7000;
};
What does happen if you replace the * with your IP address, and
issue a single port 6667; statement? I know that this is not what
you intend to do, but it might enlighten us
Package: rageircd
Version: 2.0.1-1
Followup-For: Bug #330887
The server's logging is turned on and it shows the server starting up
and shutting down as follows:
[Fri Sep 30 14:35:55 2005] Restarting server...
[Fri Sep 30 14:41:01 2005] Server shutting down due to SIGTERM, deleting
pid
I have
Marc Haber wrote:
Cannot help you with that, but some network, disk, mouse and/or
keyboard drivers fill the entropy pool, so it might help to copy big
files inside the file system.
Maybe your hardware has a hardware random number generator, which can
be utilized by installing the rng-tools
32 matches
Mail list logo
