Package: chrony
Version: 4.0-8+deb11u2
Severity: important
Dear Maintainer,
please consider adding support for 'refclock' in /etc/chrony/sources.d.
Some compute providers (Azure, Hetzner, KVM) support PTP as a
high-precision alternative to NTP but that feature requires to
configure a refclock
Am 30.01.2011 23:57, schrieb Mark Hindley:
Could you apply this patch to /usr/share/apt-cacher/apt-cacher-lib.pl
and see if it helps if you have chmod /var/cache/apt-cacher to
root:root.
This is the result:
# chown root:root /var/cache/apt-cacher
# /etc/init.d/apt-cacher stop
Package: apt-cacher
Version: 1.6.12
Severity: important
Some requests to the apt-cacher fail with the error message
Fri Jan 14 13:15:40 2011|info [8539]: Warning: apt-cacher failed to connect to
libcurl
Fri Jan 14 13:15:40 2011|error [8543]: Unable to create libcurl socket
Hi Mark!
Am 30.01.2011 16:55, schrieb Mark Hindley:
Some requests to the apt-cacher fail with the error message
Only some? Which don't?
Yes, only some requests failed. I haven't found a rule but I can provide
you the error and access log files.
Were they root:root before or something else?
Am 30.01.2011 19:54, schrieb Mark Hindley:
Yes, I think so. When (approximately!) was your original apt-cacher
install? I wonder if it was before the option to run as www-data was
introduced. That was also before I was maintainer and I don't have the
sources, so I am a bit in the dark.
Hi Ian,
Am 05.01.2011 14:11, schrieb Ian Campbell:
Netback is supposed to drop such invalid packets, however I've just
found a patch in my .git/patches, dated August 2009, to do this which I
forgot to send upstream. I'll do that now!
Shall I still test something or just wait for the fix?
I
Hi,
Am 05.01.2011 14:57, schrieb Ian Campbell:
Per my previous mail please can you let me know the details of the
Windows driver versions you are using, where you got them from etc.
PV drivers are Citrix WHQL server for XenServer 5.5, don't know download
source anymore (looked for it in
Hi,
Am 05.01.2011 17:22, schrieb Ian Campbell:
I'd strongly recommend upgrading to something newer, such as the drivers
supplied with the XCP 1.0 beta. The beta designation does not apply to
the Windows driver component of this release, they are a GA version of
the drivers.
Hi Ian,
I've tried with 2.6.32-28 but problem persists. So we have a problem
with symptoms similar to #596802. I'll attach the oops details.
Regards,
Stephan
Jan 4 17:46:33 n0020 kernel: [ 82.100424] device vif1.0 entered promiscuous
mode
Jan 4 17:46:33 n0020 kernel: [ 82.103545] br0:
Hello,
Am 04.01.2011 18:33, schrieb Ian Campbell:
I don't suppose you feel inclined to bisect between -23 and -28 to find
the first broken version, do you? (http://snapshot.debian.org/ is your
friend here)
I've checked...
-23: oops
-24: oops
-25: oops
-26: oops
-27: oops
-28: oops
-29: oops
Hi Ian!
Am 02.01.2011 20:27, schrieb Ian Campbell:
Did -28 work OK? Otherwise what was the last known good kernel?
The -29 kernel was the one that was installed when I've setup Squeeze.
So, there was never a different kernel on that system. Anyway... I can
try -28 and see what happens.
The
Package: linux-2.6
Version: 2.6.32-29
Severity: important
The bug reported in #596802 seems to have reappeared in kernel 2.6.32-29.
Problem arises when network traffic starts in freshly started HVM domain
(W2k8R2, Citrix WHQL drivers). I've already upgraded the e1000e module from the
one in
Hi all,
Am 22.05.2010 19:42, schrieb Moritz Muehlenhoff:
2.6.32.12 has introduced lots of xfs bugfixes. Please try the current
2.6.32-13 kernel from unstable. If the error can still be reproduced
it should be reported upstream at bugzilla.kernel.org
Looks like my issue has been solved with
Package: milter-greylist
Version: 3.0-3.1
Severity: normal
Last night my milter-greylist crashed with a segfault:
Mar 15 01:53:33 n0034 kernel: [55124.848954] milter-greylist[1662]: segfault at
130 ip 7fd0a8e33900 sp 420030f0 error 4 in libmilter.so.1.0.1[7fd0a8e28000+f000]
When restarting
Hi all,
Am 23.02.2010 11:35, schrieb maximilian attems:
xfsdump version is not specified. Stefan could you add that info?
output of:
dpkg -l xfsdump
Here we go...
# dpkg -l xfsdump
Desired=Unknown/Install/Remove/Purge/Hold
|
No issues so far with 2.6.32. xfsdump to tape seems to work better now,
i.e. no panics.
I think we can close this bug.
smime.p7s
Description: S/MIME Cryptographic Signature
Ooops... just seconds after my mail the server panic'd while xfsdumping
to tape:
Kernel panic - not syncing: xfs_fs_destroy_inode: cannot reclaim
0x8800642fcd80
Pid: 47, comm: kswapd0 Not tainted 2.6.32-2-amd64 #1
Call trace:
[...] ? panic+0x86/0x141
[...] ? __up_write+0x12/0x45
[...]
Sorry, cannot find an updated 2.6.30-2-amd64 on unstable. Do you mean
2.6.32-2-amd64?
smime.p7s
Description: S/MIME Cryptographic Signature
18 matches
Mail list logo
