Bug#595527: siege: [error] descriptor table full sock.c:108: Too many open files
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
Bug#595527: [error] descriptor table full sock.c:108: Too many open files
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 = false connection = close concurrent = 2000 time = 30M delay = 1 internet = false benchmark = true accept-encoding = gzip spinner = true zero-data-ok = false And the output: stephane@darkangel:~$ siege -v https://10.4.2.192/html/cod7_360_all.html ** SIEGE 2.70 ** Preparing 2000 concurrent users for battle. The server is now under siege... [error] descriptor table full sock.c:108: Too many open files [error] descriptor table full sock.c:108: Too many open files [snip] [error] descriptor table full sock.c:108: Too many open files libgcc_s.so.1 must be installed for pthread_cancel to work libgcc_s.so.1 must be installed for pthread_cancel to work [error] descriptor table full sock.c:108: Too many open files libgcc_s.so.1 must be installed for pthread_cancel to work libgcc_s.so.1 must be installed for pthread_cancel to work Aborted I'd be happy to provide more if you want. Cheers, Steph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596343: other issue
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 slapd Stopping OpenLDAP: slapd. Creating initial configuration... Loading the initial configuration from the ldif file () failed with the following error while running slapadd: ldif_read_record: include file:///etc/ldap/schema/core.ldif failed Surely enough, there was no schemas there, so my quick fix was just to rsync the ones we had from another squeeze (earlier version using 2.4.17 before your migration to /etc/ldap/slapd.d/) and that worked: ldap:~# dpkg-reconfigure slapd Stopping OpenLDAP: slapd. Creating initial configuration... done. Creating LDAP directory... done. Starting OpenLDAP: slapd. Cheers, Steph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596343: other issue
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 autoconfiguration. So no, that's not related to this bug. Alright, thanks for your reply. Steph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#591473: linux-image-2.6.32-5-amd64: kernel panics on reboot or when nic has no link
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 tests i did yesterday, it was showing debug symbols concerning ACPI mostly. Cheers, Steph -- Mail sent under Debian GNU/Linux http://frlinux.net - Site d'aide a Linux en Francais http://frlinux.net/files/frlinux_public_key.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#591473: linux-image-2.6.32-5-amd64: kernel panics on reboot or when nic has no link
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
Bug#589854: fixed
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? Contact listmas...@lists.debian.org
Bug#420560: linux-image-2.6.18-4-xen-686: Upgrade from 2.6.18.3 to 2.6.18.4-xen gives kernel panic
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 booting kernel). Using 2.6.18.3 still from the Debian packages actually works and boots fine (this report is currently written on it using 2.6.18.3). I think it might be related to initramfs-tools possibly. Please let me know if you need any other information about this. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-xen-686 Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-4-xen-686 depends on: ii initramfs-tools 0.85gtools for generating an initramfs ii linux-modules-2.6.18-4- 2.6.18.dfsg.1-12 Linux 2.6.18 modules on i686 Versions of packages linux-image-2.6.18-4-xen-686 recommends: ii libc6-xen 2.3.6.ds1-13 GNU C Library: Shared libraries [X -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#420560: linux-image-2.6.18-4-xen-686: Upgrade from 2.6.18.3 to 2.6.18.4-xen gives kernel panic
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/Linux http://frlinux.net - Site d'aide a Linux en Francais http://frlinux.net/files/frlinux_public_key.asc
Bug#401249: [Pkg-xen-devel] Bug#401249: xen-utils-common: xenbr0 not being created
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 open event channel interface (19 = No such device)
FATAL: Failed to open evtchn device: No such device
Here is a strace :
strace -f /usr/lib/xen-3.0.3-1/bin/xenstored
execve(/usr/lib/xen-3.0.3-1/bin/xenstored,
[/usr/lib/xen-3.0.3-1/bin/xenstor...], [/* 19 vars */]) = 0
uname({sys=Linux, node=golem, ...}) = 0
brk(0) = 0x805a000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xb7f15000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or
directory)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xb7f14000
open(/usr/lib/xen-3.0.3-1/lib/tls/i686/cmov/libxenctrl.so, O_RDONLY) =
-1 ENOENT (No such file or directory)
stat64(/usr/lib/xen-3.0.3-1/lib/tls/i686/cmov, 0xbfebcaa8) = -1 ENOENT
(No such file or directory)
open(/usr/lib/xen-3.0.3-1/lib/tls/i686/libxenctrl.so, O_RDONLY) = -1
ENOENT (No such file or directory)
stat64(/usr/lib/xen-3.0.3-1/lib/tls/i686, 0xbfebcaa8) = -1 ENOENT (No
such file or directory)
open(/usr/lib/xen-3.0.3-1/lib/tls/cmov/libxenctrl.so, O_RDONLY) = -1
ENOENT (No such file or directory)
stat64(/usr/lib/xen-3.0.3-1/lib/tls/cmov, 0xbfebcaa8) = -1 ENOENT (No
such file or directory)
open(/usr/lib/xen-3.0.3-1/lib/tls/libxenctrl.so, O_RDONLY) = -1 ENOENT
(No such file or directory)
stat64(/usr/lib/xen-3.0.3-1/lib/tls, 0xbfebcaa8) = -1 ENOENT (No such
file or directory)
open(/usr/lib/xen-3.0.3-1/lib/i686/cmov/libxenctrl.so, O_RDONLY) = -1
ENOENT (No such file or directory)
stat64(/usr/lib/xen-3.0.3-1/lib/i686/cmov, 0xbfebcaa8) = -1 ENOENT (No
such file or directory)
open(/usr/lib/xen-3.0.3-1/lib/i686/libxenctrl.so, O_RDONLY) = -1 ENOENT
(No such file or directory)
stat64(/usr/lib/xen-3.0.3-1/lib/i686, 0xbfebcaa8) = -1 ENOENT (No such
file or directory)
open(/usr/lib/xen-3.0.3-1/lib/cmov/libxenctrl.so, O_RDONLY) = -1 ENOENT
(No such file or directory)
stat64(/usr/lib/xen-3.0.3-1/lib/cmov, 0xbfebcaa8) = -1 ENOENT (No such
file or directory)
open(/usr/lib/xen-3.0.3-1/lib/libxenctrl.so, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\320\33..., 512)
= 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=46772, ...}) = 0
mmap2(NULL, 136580, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0)
= 0xb7ef2000
mmap2(0xb7efd000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xb) = 0xb7efd000
mmap2(0xb7efe000, 87428, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7efe000
close(3)= 0
open(/usr/lib/xen-3.0.3-1/lib/libc.so.6, O_RDONLY) = -1 ENOENT (No such
file or directory)
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=20356, ...}) = 0
mmap2(NULL, 20356, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7eed000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/lib/tls/i686/cmov/libc.so.6, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\240O\1..., 512)
= 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=1253868, ...}) = 0
mmap2(NULL, 1259676, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0)
= 0xb7db9000
mmap2(0xb7ee3000, 28672, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x12a) = 0xb7ee3000
mmap2(0xb7eea000, 10396, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7eea000
close(3)= 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xb7db8000
mprotect(0xb7ee3000, 20480, PROT_READ) = 0
set_thread_area({entry_number:-1 - 6, base_addr:0xb7db86c0,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
limit_in_pages:1, seg_not_present:0, useable:1}) = 0
munmap(0xb7eed000, 20356) = 0
mkdir(/var/run/xenstored, 0755) = -1 EEXIST (File exists)
mkdir(/var/lib/xenstored, 0755) = -1 EEXIST (File exists)
clone(Process 3389 attached
child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0xb7db8708) = 3389
[pid 3388] exit_group(0) = ?
Process 3388 detached
setsid()= 3389
clone(Process 3390 attached
child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0xb7db8708) = 3390
[pid 3389] exit_group(0) = ?
Process 3389 detached
chdir(/) = 0
umask(0)= 022
brk(0) = 0x805a000
brk(0x807b000) = 0x807b000
socket(PF_FILE, SOCK_STREAM, 0) = 3
socket(PF_FILE, SOCK_STREAM, 0) = 4
Bug#401249: [Pkg-xen-devel] Bug#401249: xen-utils-common: xenbr0 not being created
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 :
/usr/lib/xen-3.0.3-1/bin/xenstored
ERROR: Could not open event channel interface (19 = No such device)
FATAL: Failed to open evtchn device: No such device
An strace seems to indicate that it cannot find quite a few files
including : /usr/lib/xen-3.0.3-1/lib/libc.so.6
strace /usr/lib/xen-3.0.3-1/bin/xenstored
execve(/usr/lib/xen-3.0.3-1/bin/xenstored,
[/usr/lib/xen-3.0.3-1/bin/xenstor...], [/* 16 vars */]) = 0
uname({sys=Linux, node=golem, ...}) = 0
brk(0) = 0x805a000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7ef
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or
directory)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7eef000
open(/usr/lib/xen-3.0.3-1/lib/tls/i686/cmov/libxenctrl.so, O_RDONLY) =
-1 ENOENT (No such file or directory)
stat64(/usr/lib/xen-3.0.3-1/lib/tls/i686/cmov, 0xbfe5daf8) = -1 ENOENT
(No such file or directory)
open(/usr/lib/xen-3.0.3-1/lib/tls/i686/libxenctrl.so, O_RDONLY) = -1
ENOENT (No such file or directory)
stat64(/usr/lib/xen-3.0.3-1/lib/tls/i686, 0xbfe5daf8) = -1 ENOENT (No
such file or directory)
open(/usr/lib/xen-3.0.3-1/lib/tls/cmov/libxenctrl.so, O_RDONLY) = -1
ENOENT (No such file or directory)
stat64(/usr/lib/xen-3.0.3-1/lib/tls/cmov, 0xbfe5daf8) = -1 ENOENT (No
such file or directory)
open(/usr/lib/xen-3.0.3-1/lib/tls/libxenctrl.so, O_RDONLY) = -1 ENOENT
(No such file or directory)
stat64(/usr/lib/xen-3.0.3-1/lib/tls, 0xbfe5daf8) = -1 ENOENT (No such
file or directory)
open(/usr/lib/xen-3.0.3-1/lib/i686/cmov/libxenctrl.so, O_RDONLY) = -1
ENOENT (No such file or directory)
stat64(/usr/lib/xen-3.0.3-1/lib/i686/cmov, 0xbfe5daf8) = -1 ENOENT (No
such file or directory)
open(/usr/lib/xen-3.0.3-1/lib/i686/libxenctrl.so, O_RDONLY) = -1
ENOENT (No such file or directory)
stat64(/usr/lib/xen-3.0.3-1/lib/i686, 0xbfe5daf8) = -1 ENOENT (No such
file or directory)
open(/usr/lib/xen-3.0.3-1/lib/cmov/libxenctrl.so, O_RDONLY) = -1
ENOENT (No such file or directory)
stat64(/usr/lib/xen-3.0.3-1/lib/cmov, 0xbfe5daf8) = -1 ENOENT (No such
file or directory)
open(/usr/lib/xen-3.0.3-1/lib/libxenctrl.so, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\320\33...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=46772, ...}) = 0
mmap2(NULL, 136580, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0xb7ecd000
mmap2(0xb7ed8000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xb) = 0xb7ed8000
mmap2(0xb7ed9000, 87428, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7ed9000
close(3)= 0
open(/usr/lib/xen-3.0.3-1/lib/libc.so.6, O_RDONLY) = -1 ENOENT (No
such file or directory)
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=20356, ...}) = 0
mmap2(NULL, 20356, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7ec8000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/lib/tls/i686/cmov/libc.so.6, O_RDONLY) = -1 ENOENT (No such file
or directory)
open(/lib/tls/i686/cmov/libc.so.6, O_RDONLY) = -1 ENOENT (No such file
or directory)
stat64(/lib/tls/i686/cmov, 0xbfe5dadc) = -1 ENOENT (No such file or
directory)
open(/lib/tls/i686/libc.so.6, O_RDONLY) = -1 ENOENT (No such file or
directory)
stat64(/lib/tls/i686, 0xbfe5dadc) = -1 ENOENT (No such file or
directory)
open(/lib/tls/cmov/libc.so.6, O_RDONLY) = -1 ENOENT (No such file or
directory)
stat64(/lib/tls/cmov, 0xbfe5dadc) = -1 ENOENT (No such file or
directory)
open(/lib/tls/libc.so.6, O_RDONLY)= -1 ENOENT (No such file or
directory)
stat64(/lib/tls, 0xbfe5dadc) = -1 ENOENT (No such file or
directory)
open(/lib/i686/cmov/libc.so.6, O_RDONLY) = -1 ENOENT (No such file or
directory)
stat64(/lib/i686/cmov, 0xbfe5dadc)= -1 ENOENT (No such file or
directory)
open(/lib/i686/libc.so.6, O_RDONLY) = -1 ENOENT (No such file or
directory)
stat64(/lib/i686, 0xbfe5dadc) = -1 ENOENT (No such file or
directory)
open(/lib/cmov/libc.so.6, O_RDONLY) = -1 ENOENT (No such file or
directory)
stat64(/lib/cmov, 0xbfe5dadc) = -1 ENOENT (No such file or
directory)
open(/lib/libc.so.6, O_RDONLY)= 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220T\1...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1147736, ...}) = 0
mmap2(NULL, 1157428, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0xb7dad000
mmap2(0xb7ebe000, 28672, PROT_READ|PROT_WRITE,
Bug#401249: xen-utils-common: xenbr0 not being created
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_thread
self.finish_request(request, client_address)
File SocketServer.py, line 254, in finish_request
self.RequestHandlerClass(request, client_address, self)
File SocketServer.py, line 521, in __init__
self.handle()
File BaseHTTPServer.py, line 316, in handle
self.handle_one_request()
File BaseHTTPServer.py, line 310, in handle_one_request
method()
File /usr/lib/xen-3.0.3-1/lib/python/xen/util/xmlrpclib2.py, line 66, in
do_POST
self.send_response(200)
File BaseHTTPServer.py, line 367, in send_response
self.wfile.write(%s %d %s\r\n %
File socket.py, line 248, in write
self.flush()
File socket.py, line 235, in flush
self._sock.sendall(buffer)
error: (32, 'Broken pipe')
/var/log/xen/xend.log:
[2006-12-02 02:26:50 xend 2941] INFO (__init__:1072) Xend Daemon started
[2006-12-02 02:26:50 xend 2941] INFO (__init__:1072) Xend changeset: Thu Sep 21
17:56:14 2006 +0100 .
[2006-12-02 02:26:50 xend 2941] ERROR (__init__:1072) Exception starting xend
((111, 'Connection refused'))
Traceback (most recent call last):
File /usr/lib/xen-3.0-unstable-1/lib/python/xen/xend/server/SrvDaemon.py,
line 291, in run
servers = SrvServer.create()
File /usr/lib/xen-3.0-unstable-1/lib/python/xen/xend/server/SrvServer.py,
line 108, in create
root.putChild('xend', SrvRoot())
File /usr/lib/xen-3.0-unstable-1/lib/python/xen/xend/server/SrvRoot.py,
line 40, in __init__
self.get(name)
File /usr/lib/xen-3.0-unstable-1/lib/python/xen/web/SrvDir.py, line 82, in
get
val = val.getobj()
File /usr/lib/xen-3.0-unstable-1/lib/python/xen/web/SrvDir.py, line 52, in
getobj
self.obj = klassobj()
File
/usr/lib/xen-3.0-unstable-1/lib/python/xen/xend/server/SrvDomainDir.py, line
39, in __init__
self.xd = XendDomain.instance()
File /usr/lib/xen-3.0-unstable-1/lib/python/xen/xend/XendDomain.py, line
646, in instance
inst.init()
File /usr/lib/xen-3.0-unstable-1/lib/python/xen/xend/XendDomain.py, line
71, in init
xstransact.Mkdir(VMROOT)
File
/usr/lib/xen-3.0-unstable-1/lib/python/xen/xend/xenstore/xstransact.py, line
345, in Mkdir
complete(path, lambda t: t.mkdir(*args))
File
/usr/lib/xen-3.0-unstable-1/lib/python/xen/xend/xenstore/xstransact.py, line
351, in complete
t = xstransact(path)
File
/usr/lib/xen-3.0-unstable-1/lib/python/xen/xend/xenstore/xstransact.py, line
20, in __init__
self.transaction = xshandle().transaction_start()
File /usr/lib/xen-3.0-unstable-1/lib/python/xen/xend/xenstore/xsutil.py,
line 18, in xshandle
xs_handle = xen.lowlevel.xs.xs()
Error: (111, 'Connection refused')
[2006-12-02 02:26:50 xend 2940] INFO (__init__:1072) Xend exited with status 1.
I have another Debian sid which I installed last week and does not show that
behavior.
Just in case i am adding here all the xen packages i have installed :
ii libc6-xen 2.3.6.ds1-8 GNU C
Library: Shared libraries [Xen version
ii linux-image-2.6.18-2-xen-686 2.6.18-5Linux
2.6.18 image on PPro/Celeron/PII/PIII/
ii linux-modules-2.6.18-2-xen-686 2.6.18-5Linux
2.6.18 modules on PPro/Celeron/PII/PII
ii xen-hypervisor-3.0-unstable-1-i386 3.0-unstable+hg11561-1 The Xen
Hypervisor on i386-class
rc xen-hypervisor-3.0.3-1-i3863.0.3-0-2 The Xen
Hypervisor on i386
ii xen-ioemu-3.0-unstable 3.0-unstable+hg11561-1 XEN
administrative tools
ii xen-ioemu-3.0.3-1 3.0.3-0-2 XEN
administrative tools
ii xen-tools 2.8-2 Tools to
manage debian XEN virtual servers
ii xen-utils-3.0-unstable-1 3.0-unstable+hg11561-1 XEN
administrative tools
ii xen-utils-3.0.3-1 3.0.3-0-2 XEN
administrative tools
ii xen-utils-common 3.0.3-0-2 XEN
administrative tools - common files
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-2-xen-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages xen-utils-common depends on:
ii lsb-base 3.1-22 Linux Standard Base 3.1 init scrip
ii udev 0.103-1/dev/ and hotplug management daemo
xen-utils-common recommends no packages.
-- no debconf information
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to
Bug#385574: linux-image-2.6.16-2-xen-686: same issue (kernel panic) when booting up latest xen kernel
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 policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.16-2-xen-686 depends on: ii initramfs-tools [linux-initra 0.77b tools for generating an initramfs ii linux-modules-2.6.16-2-xen-68 2.6.16-18 Linux kernel modules 2.6.16 image ii yaird [linux-initramfs-tool] 0.0.12-18 Yet Another mkInitRD Versions of packages linux-image-2.6.16-2-xen-686 recommends: ii libc6-xen2.3.6.ds1-4 GNU C Library: Shared libraries [X -- no debconf information -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385574: Info received (linux-image-2.6.16-2-xen-686: same issue (kernel panic) when booting up latest xen kernel)
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 of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#372523: linux-image-2.6.16-2-xen-686: kernel panic on software raid (md0)
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 then sees the two drives as hde and hdg, which doesn't really make sense. The server is a Dell PowerEdge 650 which has been stripped of all SCSI drives and being used with IDE instead. 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. Now, why would the Debian installer see them as hda and hdc puzzles me a bit. I hope that will help you out, i'm surely not the only one wanting to install Xen on such a configuration. Steph -- Mail sent under Debian GNU/Linux http://frlinux.net - Site d'aide a Linux en Francais http://frlinux.net/files/frlinux_public_key.asc
Bug#372523: linux-image-2.6.16-2-xen-686: kernel panic on software raid (md0)
-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 question is: what is being seen as the primary IDE controller in this case (which claims hda-hdd). The IDE controllers on the box are : 00:05.0 IDE interface: Silicon Image, Inc. PCI0680 Ultra ATA-133 Host Controller (rev 02) 00:0f.1 IDE interface: Broadcom CSB6 RAID/IDE Controller (rev a0) On normal debian install/kernel, the broadcom gets loaded first. On the Xen kernel; the Sil controller gets in first. Interestingly, the only way i got the Xen kernel to boot was to use yaird rather than the standard mkinitrd, that is the only one which compiles a proper list of my modules. This is also the reason behind the erratum for d-i listed on: http://www.us.debian.org/devel/debian-installer/errata Nice one, i had forgotten about that one, that would indeed explain the behavior. I have to paste this in, this is the boot from the Xen kernel : SiI680: IDE controller at PCI slot :00:05.0 SiI680: chipset revision 2 SiI680: BASE CLOCK == 133 SiI680: 100% native mode on irq 16 ide0: MMIO-DMA , BIOS settings: hda:pio, hdb:pio ide1: MMIO-DMA , BIOS settings: hdc:pio, hdd:pio Probing IDE interface ide0... hda: SAMSUNG SP2014N, ATA DISK drive ide0 at 0xf4802080-0xf4802087,0xf480208a on irq 16 Probing IDE interface ide1... hdc: SAMSUNG SP2014N, ATA DISK drive [snip] SvrWks CSB6: IDE controller at PCI slot :00:0f.1 SvrWks CSB6: chipset revision 160 SvrWks CSB6: not 100% native mode: will probe irqs later ide2: BM-DMA at 0x08b0-0x08b7, BIOS settings: hde:DMA, hdf:pio ide3: BM-DMA at 0x08b8-0x08bf, BIOS settings: hdg:pio, hdh:pio Probing IDE interface ide2... hde: TEAC CD-ROM CD-224E, ATAPI CD/DVD-ROM drive It actually booted up properly BUT (that's the important bit here), GRUB wanted this to be able to start : title Xen 3.0 / XenLinux 2.6 kernel /xen-3.0-i386.gz noreboot module /vmlinuz-2.6.16-2-xen-686 root=/dev/hde1 ro module /initrd.img-2.6.16-2-xen-686 Steph - -- Mail sent on Gentoo Linux (http://www.gentoo.org) http://frlinux.net - [EMAIL PROTECTED] public key : http://frlinux.net/files/frlinux_public_key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFElv7xplbM2wjOZgMRAkp3AJ9P+Hi/Fm50tE4NBBhSVxDi0qMkpwCgs1zh dy6ScXWtuJDlVod6JDI/I7s= =yWS5 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#372523: linux-image-2.6.16-2-xen-686: kernel panic on software raid (md0)
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 : title Xen 3.0 / XenLinux 2.6 root(hd0,0) kernel /xen-3.0-i386.gz noreboot module /vmlinuz-2.6.16-2-xen-686 root=/dev/md0 ro module /initrd.img-2.6.16-2-xen-686 It unfortunately dies straight when it tries to find the root RAID partition. This is my partitions layout : /dev/md0 4.6G 134M 4.3G 4% / tmpfs 443M 0 443M 0% /dev/shm /dev/hda1 177M 13M 155M 8% /boot /dev/md3 897M 8.1M 841M 1% /home /dev/md5 158G 272K 158G 1% /mnt/xen /dev/md4 449M 8.1M 417M 2% /tmp /dev/md1 9.2G 313M 8.4G 4% /usr /dev/md2 8.3G 233M 7.7G 3% /var Is there a way around this ? Thanks, Steph -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.16-2-xen-686 depends on: ii initramfs-tools [linux-initra 0.60 tools for generating an initramfs ii linux-modules-2.6.16-2-xen-68 2.6.16-14 Linux kernel modules 2.6.16 image ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.16-2-xen-686 recommends: ii libc6-xen 2.3.6-15 GNU C Library: Shared libraries [X -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#372523: linux-image-2.6.16-2-xen-686: kernel panic on software raid (md0)
-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 the standard image does handle all my soft raid properly. Steph - -- Mail sent on Gentoo Linux (http://www.gentoo.org) http://frlinux.net - [EMAIL PROTECTED] public key : http://frlinux.net/files/frlinux_public_key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEifaCplbM2wjOZgMRAiWuAJ4gldDfQd8njbtHlbgUYzb07VXyzACgoH46 ZoKshMwaGa1P1Y/4KnGpy74= =5c7x -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357025: same udev issue with vconfig and brctl
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 GNU/Linux http://frlinux.net - Site d'aide a Linux en Francais http://frlinux.net/files/frlinux_public_key.asc
Bug#357025: same udev issue with vconfig and brctl
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.091-1 which seems to confuse our network setup. We use this machine as a bridging firewall and it keeps creating temporary interfaces (like eth0.3_temp). The real interfaces (like eth0.3) then get a 00:00:00:00:00 MAC address rather than the real one and the temporary interface then gets the real MAC. This is the kind of logs were are getting in /var/log/daemon : May 3 10:03:30 cyclops udevd-event[10627]: rename_net_if: error changing net interface name br3_temp to eth0: timeout May 3 10:03:30 cyclops udevd-event[10645]: rename_net_if: error changing net interface name br4_temp to eth0: timeout May 3 10:03:30 cyclops udevd-event[10664]: rename_net_if: error changing net interface name br5_temp to eth0: timeout May 3 10:03:30 cyclops udevd-event[10683]: rename_net_if: error changing net interface name br6_temp to eth0: timeout May 3 10:03:30 cyclops udevd-event[10740]: rename_net_if: error changing net interface name br8_temp to eth0: timeout May 3 10:03:30 cyclops udevd-event[10759]: rename_net_if: error changing net interface name br9_temp to eth0: timeout May 3 10:03:30 cyclops udevd-event[10816]: rename_net_if: error changing net interface name br11_temp to eth0: timeout May 3 10:03:30 cyclops udevd-event[10874]: rename_net_if: error changing net interface name br13_temp to eth0: timeout May 3 10:03:30 cyclops udevd-event[10892]: rename_net_if: error changing net interface name br14_temp to eth0: timeout May 3 10:03:30 cyclops udevd-event[10911]: rename_net_if: error changing net interface name br15_temp to eth0: timeout May 3 10:03:30 cyclops udevd-event[10930]: rename_net_if: error changing net interface name br16_temp to eth0: timeout May 3 10:03:31 cyclops udevd-event[10949]: rename_net_if: error changing net interface name br17_temp to eth0: timeout May 3 10:03:31 cyclops udevd-event[10968]: rename_net_if: error changing net interface name br18_temp to eth0: timeout May 3 10:07:20 cyclops udevd-event[11385]: rename_net_if: error changing net interface name eth0.7 to eth0: Device or resource busy May 3 10:07:20 cyclops udevd-event[11388]: rename_net_if: error changing net interface name eth1.7 to eth1: Device or resource busy May 3 10:07:20 cyclops udevd-event[11454]: rename_net_if: error changing net interface name eth0.12 to eth0: Device or resource busy May 3 10:07:20 cyclops udevd-event[11457]: rename_net_if: error changing net interface name eth1.12 to eth1: Device or resource busy May 3 10:07:52 cyclops udevd-event[11383]: rename_net_if: error changing net interface name br7_temp to eth0: timeout May 3 10:07:52 cyclops udevd-event[11423]: rename_net_if: error changing net interface name eth0.10_temp to eth0: timeout May 3 10:07:52 cyclops udevd-event[11436]: rename_net_if: error changing net interface name eth1.10_temp to eth1: timeout May 3 10:07:52 cyclops udevd-event[11452]: rename_net_if: error changing net interface name br12_temp to eth0: timeout Steph -- Package-specific info: -- /etc/udev/rules.d/: /etc/udev/rules.d/: total 8 lrwxrwxrwx 1 root root 20 2005-12-20 15:29 020_permissions.rules - ../permissions.rules lrwxrwxrwx 1 root root 19 2005-12-20 15:29 cd-aliases.rules - ../cd-aliases.rules lrwxrwxrwx 1 root root 13 2005-12-20 15:29 udev.rules - ../udev.rules lrwxrwxrwx 1 root root 25 2006-03-30 09:09 z20_persistent-input.rules - ../persistent-input.rules lrwxrwxrwx 1 root root 19 2005-12-20 15:29 z20_persistent.rules - ../persistent.rules -rw-r--r-- 1 root root 4738 2006-04-24 14:53 z25_persistent-net.rules lrwxrwxrwx 1 root root 33 2006-04-24 14:52 z45_persistent-net-generator.rules - ../persistent-net-generator.rules lrwxrwxrwx 1 root root 12 2005-12-20 15:29 z50_run.rules - ../run.rules lrwxrwxrwx 1 root root 16 2005-12-20 15:29 z55_hotplug.rules - ../hotplug.rules lrwxrwxrwx 1 root root 17 2005-12-20 15:29 z70_hotplugd.rules - ../hotplugd.rules -- /sys/: /sys/block/ram0/dev /sys/block/ram10/dev /sys/block/ram11/dev /sys/block/ram12/dev /sys/block/ram13/dev /sys/block/ram14/dev /sys/block/ram15/dev /sys/block/ram1/dev /sys/block/ram2/dev /sys/block/ram3/dev /sys/block/ram4/dev /sys/block/ram5/dev /sys/block/ram6/dev /sys/block/ram7/dev /sys/block/ram8/dev /sys/block/ram9/dev /sys/block/sda/dev /sys/block/sda/sda1/dev /sys/block/sda/sda2/dev /sys/block/sda/sda3/dev /sys/block/sda/sda4/dev /sys/block/sda/sda5/dev /sys/block/sda/sda6/dev /sys/block/sda/sda7/dev /sys/block/sda/sda8/dev /sys/class/input/event0/dev /sys/class/input/event1/dev /sys/class/input/mice/dev /sys/class/misc/device-mapper/dev /sys/class/misc/hpet/dev /sys/class/misc/psaux/dev /sys/class/misc/rtc/dev /sys/class/misc/watchdog/dev /sys/class/usb_device/usbdev1.1/dev
