Hi Gunnar, hi Luigi, hi securiy@d.o!
I reported http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690817 on Oct. 18th
and Gunnar replied quickly with a patch. Since then the last message for this
bug is pending/uploaded/delayed. In the meanwhile drupal7 7.14-1.1 is in
unstable.
So, is that bug
Am 23.02.2013 um 16:37 schrieb Luigi Gangitano :
> 7.14-2 has just been uploaded, acknowledging your NMUs and adding the latest
> security fix.
Thanks to both of you for dealing with and finally fixing this issue! :-)
--
Ciao...// Fon: 0381-2744150
Ingo \X/
Am 26.02.2013 um 19:19 schrieb Ian Campbell :
>> Since the update last weekind in stable/squeeze I'm experiencing
>> problems with running Xen on amd64 and multiple domUs losing their
>> network connection/VIFs.
> The hypervisors involvement in the specifics of the networking is pretty
> minima
Am 26.02.2013 um 19:19 schrieb Ian Campbell :
> So, was the hypervisor upgrade also accompanied by a kernel update, in
> either the dom0 or guest domains? If so what versions were involved and
> where?
Additionally to the last mail:
After running two days stable with the downgraded packages, I'
Am 28.02.2013 um 11:28 schrieb Ian Campbell :
> I am 99% positive it will turn out to be the kernel, but please do let
> us know.
Shortly before 18:00 today I reinstalled
linux-image-2.6.32-5-xen-amd64_2.6.32-48_amd64.deb as kernel and it took only
2.5 hours to trigger the issue.
The hyperviso
Am 28.02.2013 um 11:28 schrieb Ian Campbell :
>> All domUs are still running the updated kernel packages (pre
>> DSA-2632-1), the dom0 the downgraded kernel package.
linux-image-2.6.32-5-xen-amd64 2.6.32-48squeeze1 triggered the problem within
30 mins. ;-)
> When you reach a conclusion (assum
Am 04.07.2013 um 05:42 schrieb Ben Hutchings :
> My understanding is that disabling scatter/gather on netfront in domU
> (ethtool -K eth0 sg off) will prevent it from triggering these bugs, but
> at a substantial performance impact. In practice, disabling TSO in domU
> (ethtool -K eth0 tso off) s
Am 22.07.2013 um 20:48 schrieb David Prévot :
>> Turned on maintenance mode
>> Failed to update database structure (MDB2 Error: syntax error […]
>> I guess this needs to be taken to upstream.
> Actually this one is Debian-specific: upstream “fixed” the
> php-mdb2-driver-pgsql they’re shipping, so
On 26.10.2011 09:01, Holger Levsen wrote:
I use roundcube with suhosin, but not 0.6 yet. What do you mean by
"out of
nowhere"?
Ha! Just discovered: it's working again. BUT: when I used reportbug-ng
this morning to report the bug, it started iceweasel - and I use
iceweasel to sort my mails i
On Wed, Oct 26, 2011 at 09:01:07AM +0200, Holger Levsen wrote:
> I use roundcube with suhosin, but not 0.6 yet. What do you mean by "out of
> nowhere"?
Well, I was at work, enjoying a working roundcube and reading my mails and
then, as far as I remember, I reloaded the Inbox and it said "Loading
On 26.10.2011 19:48, Vincent Bernat wrote:
Ingo, you reported the bug against 0.6. Is it really the version that
is
affected by the problem? It seems already patched.
Well, yes, I wrote the bug report on the same machine where RC is
running.
The message in question is most likely this one:
Am 26.10.2011 um 22:40 schrieb Vincent Bernat:
> Now that the message is in another folder, you don't have the problem
> any more, even if you visit this folder? Does the problem comes back if
> you move the message to inbox?
When I access my Debian-Devel folder the problem occurs in that fol
Hi!
After contributing to this bug on Thursday, my server kept crashing on Friday
several times, even within 5 minutes after rebooting. Really, really annoying.
However I managed to deactivate my IPv6 routing on the Xen bridge. @Jan: can
you please, if possible, if this helps for you, too?
Afte
Hi!
In an effort to avoid crashes due to this bug, I installed 4.5.0-0.bpo.1-amd64
last week. The server ran in the last week quite well with activated IPv6,
but today it crashed two times within 30 mins.
Please find attached the syslog output send out via netconsole...
--
Ciao...
Hi!
I can confirm this bug as well, but I can't confirm Kamils guess that it's
related to resolving your own zone. Instead I search my logs and found this:
Sep 26 08:59:37 muaddib named[31237]: success resolving 'www.kanirope.de/A' (in
'kanirope.de'?) after reducing the advertised ED
NS UDP pa
Am 10.02.2016 um 19:35 schrieb Andreas Metzler :
> On 2016-02-10 Andreas Metzler wrote:
> [...]
> Nevermind, abbreviation thinko. You wrote SNI and I read SAN.
> Sorry for the noise.
I’ve just tested with the current version of planet-venus in unstable and the
problem still exist.
When doing a "
Hi!
I experienced issues with mounting glusterfs storage after I upgraded some
clients from Jessie to Stretch, although I’m not using Infiniband at all:
[2017-06-24 12:51:53.240389] I [MSGID: 100030] [glusterfsd.c:2454:main]
0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.
Hi Marco!
With the help of Kees in Linux echomail area I found out that the following
config option causes the segfault:
options(time Any-2359) NoHold
When commenting this out, ifcico is working as expected. As this is not an easy
to find error, I’d like to recommend to ch
On 25.07.2016 12:23, Wei Liu wrote:
First, thank you for replying! Very much appreciated! :)
I did skim your emails. But the oops was happening in memcpy+0x6 which
indicated it came back to the origin question why would it got an
exception there.
Just by staring at the code doesn't get me anyw
On 02.08.2016 11:20, Wei Liu wrote:
On Fri, Jul 29, 2016 at 10:17:22PM +0200, Ingo Jürgensmann wrote:
What is also interesting is that you seem to be running some sort of
ip accounting software (pmacctd) which also segfault'ed.
Yeah, it is segfaulting, because the database (in a domU VM)
Am 20.12.2016 um 18:24 schrieb Baruch Even :
> Can you please run it under gdb and capture the output of the command:
> bt
> bt full
Reading symbols from /usr/sbin/gpart...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/sbin/gpart -f /dev/lv/Elite3
Program received signal SI
Am 29.11.2016 um 10:08 schrieb Wei Liu :
>> http://paste.debian.net/895464/
> Entry not found -- maybe it expired... Sorry.
Here it is:
Nov 14 09:19:52 31.172.31.251 [39677.027813] BUG: unable to handle kernel
Nov 14 09:19:52 31.172.31.251 at 880002b4c06e
Nov 14 09:19:52 31.172.31.251 [396
On 01.12.2016 14:26, Wei Liu wrote:
This is still the same kernel log that was sent some time ago.
So, if you have built Xen with debug=y, could you try to set Xen log
level to the highest and capture "xl dmesg" when guest crashes?
It's not the guest that crashes, it's dom0. So when the host c
Hi!
Just wanted to give some feedback that the solution provided by Jan is
working for me.
Thanks! :-)
--
Ciao...// Fon: 0381-2744150
Ingo \X/ http://blog.windfluechter.net
Please don't share this address with Facebook or Google!
gpg pubkey: http://www.juer
On Tue, 2 Feb 2010 16:46:10 +0100, Mark Purcell wrote:
> On Monday 28 December 2009 14:03:08 Debian Bug Tracking System wrote:
>> Hopefully this issue will be end-user proof fixed by upstream in a
newer
>> version. ;-)
> Version 1.1.0 now warns if 100% isn't really 100%..
Great! Thanks! :-)
--
25 matches
Mail list logo
