Package: keepalived
Version: 1:1.2.2-3
Severity: normal
Dear Maintainer,
When you run /etc/init.d/keepalived stop, and subsequently start, you get
strange failures, that's because keepalived stays in stopping mode for
quite some time, it seems to be unalocating interfaces one-by-one.
Only
Package: keepalived
Version: 1:1.2.2-3
Severity: normal
Dear Maintainer,
When configuring keepalived with more then 31 VRRP_Interface stanzas, I
usually received this message in logs:
Sep 16 14:16:28 fw Keepalived_vrrp[7647]: Netlink: Received message
overrun
which leads later to:
Package: lxctl
Version: 0.3.1+debian-2
Severity: important
This is mainly request for newer upstream, it seems many obvious mistakes
are fixed there, this one is that lxctl generates mac adds with '01'
at the start:
/usr/share/perl5/Lxctl/set.pm
my $mac = 01: .
Package: fusioninventory-agent
Version: 2.2.3-2
Severity: minor
Dear Maintainer,
fusioninventory is missing iLO configuration from my machines, it turns out,
that the culprit is they way fusioninventory calls hponcfg:
command = 'hponcfg -aw -'
I verified, that when you run hponcfg this way,
Package: udev
Version: 175-3.1
Followup-For: Bug #671859
Dear Maintainer,
On my machines the boot delay is less noticable, but the udev still loops and
eats CPU, restart seems
to help to a degree, but usually it just keeps on looping and eating up CPU
after few minutes.
On one machine it
,
offset=0 ao=0 and number=0 for /dev/uba
Error opening /dev/uba: No medium found
which is ok, since there is no medium inserted in that slot.
regards, Eyck
--
Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9
Total Existance Failure
--
To UNSUBSCRIBE, email to debian-bugs-dist
Package: wnpp
Severity: wishlist
* Package name: sqlite3-pcre
Version : 0.1.a
Upstream Author : Roger A. Light ro...@atchoo.org
* URL :
http://git.altlinux.org/people/at/packages/?p=sqlite3-pcre.git
* License : Public Domain
Programming Lang: C
Description
Package: wnpp
Severity: wishlist
* Package name: libanyevent-couchdb-perl
Version : 1.28
Upstream Author : be...@cpan.org
* URL : http://search.cpan.org/dist/AnyEvent-CouchDB/
* License : Perl
Programming Lang: Perl
Description : a non-blocking CouchDB
Package: openssh-client
Version: 1:5.8p1-7
Severity: important
Connections fail with:
Read from socket failed: Connection reset by peer
example failed connections:
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.5p1
FreeBSD-20061110
debug1: match: OpenSSH_4.5p1
tags 510188 moreinfo unreproducible
thanks
Hello,
Back in 2008, you reported issues with W2K client connection to samba
3.0.24 servers. Something quite obscure, indeed.
No test case could be found and I'm not really sure about what the bug
might be.
Given that samba got several
On Fri, 4 Feb 2011, Philipp Kern wrote:
On Fri, Feb 04, 2011 at 11:23:48AM +0100, eyck wrote:
None of the medium-sized (2-4G) archives created using 0.45 can be
recovered.
Those archives cannot be recovered using neither 0.18 nor 0.551.
Archives created using 0.18 work ok, archives
Package: lrzip
Version: 0.45-1
Severity: critical
Justification: causes serious data loss
Archives created with 0.45 cannot be decompressed, decompression fails with
various errors:
lrzip -d 2010-1-11-sent.tar.lrz
Output filename is: 2010-1-11-sent.tar...Decompressing...
Decompressing...Failed
None of the medium-sized (2-4G) archives created using 0.45 can be
recovered.
Those archives cannot be recovered using neither 0.18 nor 0.551.
Archives created using 0.18 work ok, archives created using 0.551 also work
OK.
Small archives created using 0.45 seem to work ok.
As it
From mod_jk.log:
[Thu Jan 13 15:05:34 2011] [441:140327941527312] [error]
jk_open_socket::jk_connect.c (444): socket() failed (errno=22)
[Thu Jan 13 15:05:34 2011] [441:140327941527312] [info]
ajp_connect_to_endpoint::jk_ajp_common.c (959): Failed opening socket to
Package: libapache2-mod-jk
Version: 1.2.30
Severity: grave
Justification: renders package unusable
From mod_jk.log:
[Thu Jan 13 15:05:34 2011] [441:140327941527312] [error]
jk_open_socket::jk_connect.c (444): socket() failed (errno=22)
[Thu Jan 13 15:05:34 2011] [441:140327941527312] [info]
Package: libdbd-sybase-perl
Version: 1.00-3+b3
Severity: grave
Tags: squeeze
Justification: renders package unusable
Trying to use package results in:
DBI/DBD internal version mismatch (DBI is v94/s208, DBD Sybase.xsi expected
v95/s208) you probably need to rebuild the DBD driver (or possibly
Package: samba
Version: 3.0.24-6etch10
Severity: normal
I'm trying to trace (I think) the same problem as reported by
yurapadl...@gmail.com,
writes to the file fail, and in logs I find following messages:
Dec 29 19:04:10 hostname smbd_audit[3095]: [2008/12/29 19:04:10, 0,
effective(0, 1666),
It seems that described behaviour is caused by max_profiles being set to
10, when I re-configure it to use 21 profiles up to 21 unique settings for
tabs may be used.
Thus this report should be downgraded to 'wishlist' for upping the limit
on max profiles, thanks.
--
Key fingerprint = 40D0 9FFB
Package: mrxvt
Version: 0.5.3-2
Severity: wishlist
Please configure --with-max-term=51 or some other more reasonable
number, 15 is way too little, especially as mrxvt's main advantage is
ability to use multiple (and many) tabs.
-- System Information:
Debian Release: lenny/sid
APT prefers
Package: mrxvt
Version: 0.5.3-2
Severity: minor
When I put something like this in .mrxvtrc:
Mrxvt.profile10.tabTitle: Tab0
Mrxvt.profile10.tabTitle: Tab10
Mrxvt.profile12.tabTitle: Tab11
Mrxvt.profile13.tabTitle: Tab12
Mrxvt.profile0.command: !comand0
Package: vzctl
Version: 3.0.22-2
Followup-For: Bug #459717
hn:/home/eyck# vzctl stop veguest
Stopping VE ...
VE was stopped
/usr/lib/vzctl/scripts/vps-functions: line 146: [: del: integer expression
expected
VE is unmounted
After replacing -eq with =:
hn:/home/eyck# vzctl start veguest
Package: vzctl
Version: 3.0.22-2
Severity: wishlist
In previous versions --name setting has been kept in name.conf file in
/etc/vz/names directory. In new vzctl it uses much cleaner symlinks like
this:
lrwxrwxrwx 1 root root 21 Jan 12 00:00 etchdev - /etc/vz/conf/777.conf
-rw-r--r-- 1 root root
Package: procps
Version: 1:3.2.7-3
Severity: wishlist
When hot-removing CPUs from the system, top exits with:
top: failed /proc/stat read
zsh: exit 1 top
similarly, hot-added cpus don't show up in top.
-- System Information:
Debian Release: 4.0
Architecture: i386 (i686)
Package: isync
Version: 1.0.3-3
Severity: normal
While trying to login with userspace containing space, I noticed that
while config works OK ( ie 'User firstname lastname ) is parsed
correctly, to server only firstname is being delivered.
-- System Information:
Debian Release: 4.0
APT prefers
Package: isync
Version: 1.0.3-3
Severity: normal
It looks like while writing mbsync config file, isync forgets for
username ( but strangely remembers to put them around password ).
Here's a patch to fix that:
283c283
fprintf( fp, User %s\n, cfg-user );
---
Package: linux-image-2.6.18-4-vserver-686
Severity: normal
The bug looks like this:
BUG: unable to handle kernel NULL pointer dereference at virtual address
00ac
printing eip:
c0132f84
*pde =
Oops: [#1]
SMP
This issue is fixed by:
http://people.linux-vserver.org/~dhozac/p/k/delta-NULL-dev-fix01.diff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: amavisd-new
Version: 2.4.2
Severity: important
My system is now broken thanks to:
Starting amavisd: Found incompatible config file flag!
Due to safety concerns, amavisd-new will not be started.
Refer to /usr/share/doc/amavisd-new/README.Debian for instructions.
invoke-rc.d: initscript
Package: proftpd
Version: 1.3.0
Severity: normal
We've got users logged on, and working with our server (transferring files,
checking directories, removing stuff etc), but their activity is not recorded in
logfiles. We tracked the problem to sessions running through logrotate session
-
logs
Package: rdesktop
Version: 1.5.0-1
Severity: minor
rdesktop segfaults after recent update to libx11-6, supposedly fixing
this:
xwin.c:2419
XInitImage(image);
XPutImage(g_display, bitmap, g_create_glyph_gc, image, 0, 0, 0, 0, width,
height);
to check for error codes would be nice (in this
Package: libx11-6
Version: 2:1.0.3-6
Severity: important
Upgrading to 1.0.3-7 brakes other software - causing segfaults in
XPutImage call, rdesktop is affected and unusable.
This seems to happen on machine with direct rendering disabled, the
same setup on accelerated Xorg works fine.
-- System
Upgrading to 1.0.3-7 brakes other software - causing segfaults in
XPutImage call, rdesktop is affected and unusable.
This seems to happen on machine with direct rendering disabled, the
same setup on accelerated Xorg works fine.
could you install libx11-6-dbg and get a backtrace with gdb
Package: util-vserver
Version: 0.30.212-1
Severity: normal
According to comments in /etc/default/util-vserver you need to set
BACKGROUND to 'on' to make vservers startup go to tty9.
In reality, /etc/init.d/util-vserver script checks is BACKGROUND is set
to 'yes', and startup goes to tty8, not
Package: qpsmtpd
Version: 0.32-2
Severity: important
Here:
my ($QPHOME) = ($0 =~ m!(.*?)/([^/]+)$!);
$QPHOME should end be something like that:
$QPHOME=/var/spool/qpsmtpd/;
instead, this results in:
... using /usr/bin/config/denysoft_greylist.dbm as greylisting database
-- System
Package: litmus
Version: 0.9.4-2
Severity: important
- running `basic':
0. init.. pass
1. begin. FAIL (No SSL support, reconfigure using --with-ssl)
- summary for `basic': of 2 tests run: 1 passed, 1 failed. 50.0% See
debug.log for network/debug traces.
[niedziela, 16 kwiecieĊ 2006], Gerrit Pape napisaĊ(a):
On Tue, Mar 21, 2006 at 08:39:56AM +, Gerrit Pape wrote:
eyck.debian, can you try the steps to reproduce I did in my last mail,
does that fail for you? What if you rebuild the package on your current
sarge system, does it work
Package: dropbear
Version: 0.45-2sarge0
Severity: grave
Justification: renders package unusable
From the client, attempts to connect look like this:
RSA_public_decrypt failed: error:0407006A:rsa
routines:RSA_padding_check_PKCS1_type_1:block type is not 01
debug1: ssh_rsa_verify: signature
37 matches
Mail list logo
