Yes it fixes it for me too.
Cheers,
Steph
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I get this behavior too, using siege 2.70-1+b1 on wheezy. Here are my settings:
siege -v https://server/page.html
Here are my settings:
~$ grep -v "#" .siegerc |grep -v "^$"
logfile = $(HOME)/siege.log
verbose = true
show-logfile = true
logging = true
protocol = HTTP/1.1
chunked = true
cache =
On 09/13/10 17:16, Steve Langasek wrote:
Well, those are conffiles belonging to the slapd package; you can remove
them (as you appear to have done), but if you do so, you'll have to provide
your own schemas in their place. And if you remove core.ldif, your setup is
incompatible with the package
Hello, I am not sure this is related but found another issue. What we do
at the moment, is install the new slapd package on a replica, then
reconfigure it to use our stuff (some extra schemas and using BDB rather
than HDB).
When doing a reconfigure, i am now getting this:
ldap:~# dpkg-reconfigure
On 08/03/10 16:08, Ben Hutchings wrote:
Please test the current version from unstable.
Hello, i can confirm that fixes it, thanks!
Steph
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Tue, August 3, 2010 3:53 pm, Ben Hutchings wrote:
> Are there VLAN interfaces configured? If so this is probably bug #585770,
> which I introduced in 2.6.32-15 and fixed in -16.
Yes, we use vlans, they all connect to a trunk interface. So do you need a
screenshot still? Last I saw from the t
This version of grub-pc (20100722) fixed it for me. I have mapper
devices on my laptop (encrypted partitions) and the previous grub-pc
(20100710) was failing for me.
Thanks!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contac
On Mon, April 23, 2007 10:07 am, Bastian Blank wrote:
> And it says what?
Sorry it says :
*** LOADING DOMAIN 0 ***
PAE mode mismatch between Xen and DOM0 (xen:no, dom0:yes)
***
Panic on CPU 0:
Could not set up DOM0 guest OS
***
Reboot in five seconds...
Steph
--
Mail sent under Debian GNU/Li
Package: linux-image-2.6.18-4-xen-686
Version: 2.6.18.dfsg.1-12
Severity: grave
Justification: renders package unusable
I upgraded a server from unstable (last updated about 3 months ago) to
etch and trying to use the latest kernel fails with a kernel panic (ooops
within the first 30 lines of the
On Sat, December 2, 2006 8:10 am, Bastian Blank wrote:
> So it fails to connect to the xenstored. Please start it by hand and
> show why it dies.
Hello again, this is what i get (i just upgraded to latest packages of Xen
today from sid) :
/usr/lib/xen-3.0.3-1/bin/xenstored
ERROR: Could not op
Bastian Blank wrote:
This have nothing to do with the mentioned xenbr0 in the subject.
It does, because right now, the box doesn't have a xenbr0 interface,
neither a vifX one.
So it fails to connect to the xenstored. Please start it by hand and
show why it dies.
Yup, this is what i get :
Package: xen-utils-common
Version: 3.0.3-0-2
Severity: important
I have installed all the packages I can think of to get Xen going
and it still fails with the following :
/var/log/xen/xend-debug.log:
Exception starting xend: (111, 'Connection refused')
er.py", line 463, in process_request_thr
As someone suggested, i upgraded to kernel 2.6.17-xen and also these
two packages below which fixed it for me :
xen-hypervisor-3.0-unstable-1-i386 3.0-unstable+hg11292-2
xen-utils-3.0-unstable-1 3.0-unstable+hg11292-2
Steph
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Package: linux-image-2.6.16-2-xen-686
Version: 2.6.16-18
Followup-For: Bug #385574
I have the same behavior here, latest Xen kernel from sid with last rev of xen
utilities from sid and it kernel panics.
Steph
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frans Pop wrote:
> On Monday 19 June 2006 18:23, FRLinux wrote:
>> The IDE controller seems to be a secondary controller from the looks of
>> it therefore explaining that devices are being *moved* to hde and hdg.
>
> The quest
Hello,
I actually found what the problem is, and i wonder if it is related to
your kernel settings. When i perform an install of Debian, the installer
sees two IDE drives as hda and hdc (they are indeed connected as primary
and secondary master) and a CDrom drive.
When your Xen kernel boots, it t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bastian Blank wrote:
> What does it break?
Evening,
It does render the whole system unusable since it cannot find RAID.
> Why do you expect that a xen image may boot different from a standard
> one?
That's it, i don't expect it to be different and
Package: linux-image-2.6.16-2-xen-686
Version: 2.6.16-14
Severity: critical
Justification: breaks the whole system
Hello,
I have been using this article to set up and install my new Xen server (nice
article btw) : http://www.debian-administration.org/articles/396
I did set up grub this way :
Hello,
sorry for not getting back to you earlier on. I just got a chance to fix
this. I applied the first fix you were advising on :
rm -rf /etc/udev/rules.d/z45_persistent-net-generator.rules
/etc/udev/rules.d/z25_persistent-net.rules
This worked fine.
Cheers,
Steph
--
Mail sent under Debian G
Subject: same udev issue with vconfig and brctl
Followup-For: Bug #357025
Package: udev
Version: 0.076-6
*** Please type your report below this line ***
Hello,
We experienced the same issue here. I have currently rolled back our
machine to a 2.6.14-2 kernel
image and udev 0.076-6 rather than 0.0
20 matches
Mail list logo
