Bug#758606: After closing shutter it's in start menu of Gnome Tweak tool to delete it manually (Jessie)

2014-10-17 Thread weiterleitungen . web2 . 0
Hey,

1. dpkg -s gnome-tweak-tool | grep Version
Version: 3.14.0-1
2. This problem began after the first installation. So it was not after an
update. Yes, it's always reproducible.

Regards

2014-10-15 0:38 GMT+02:00 Tomasz Nitecki t...@tnnn.pl:

 tags 758606 + moreinfo
 thanks


 Hey,

 Can you please provide us with some more information:

 1. Which version of Gnome Tweak Tool and Shutter are you using? (You can
 check that by running 'dpkg -s package | grep Version').

 2. Can you tell us when did this problem begin to manifest itself? Was
 it after an update? Is it always reproducible?

 When responding, please remember to cc 758...@bugs.debian.org (your
 response will be visible on the public, web browsable bug tracker at [1]).

 Thanks for your report!


 Regards,
 T.

 [1] https://bugs.debian.org/758606




Re: [libvirt] increase number of libvirt threads by starting tansient guest doamin - is it a bug?

2014-10-07 Thread web2
 Hi,

i have found the time and tested Xen-4.4.1 with libvirt-1.2.6 and the problem 
with the threads are disappered. But now i see after every restore of an xen-vm 
(windows-xp hvm) an openfile-handle (via lsof -p `pgrep libvirtd`) to an file 
in /var/lib/xen with the name qemu-resume.vm-id and what me real make 
confusion is that the entry is marked as deleted.If i look in the directory, 
the file is really no more their, but libvirt have still have an handle to that 
none existing file!?!

I know that Xen create such a file before they startet the vm, and i also 
know that xen delete that file , but i don´t understand while it is listed 
under the openfiles of libvirtd after the vm is started/destroyed???

all the best
max
 
ursprüngliche Nachricht-
Von: web2 usterman...@web.de 
An: Jim Fehlig jfeh...@suse.com , web2 usterman...@web.de 
Kopie: Michal Privoznik mpriv...@redhat.com , libvirt-users redhat.com 
, libvirt-list redhat.com 
Datum: Thu, 2 Oct 2014 07:49:03 +
-
 
 
 
 
 ursprüngliche Nachricht-
 Von: Jim Fehlig jfeh...@suse.com 
 An: web2 usterman...@web.de 
 Kopie: Michal Privoznik mpriv...@redhat.com , libvirt-users redhat.com 
 
 , libvirt-list redhat.com 
 Datum: Wed, 01 Oct 2014 21:38:05 -0600
 -
 
 
 web2 wrote:
 Hi
 
 ursprüngliche Nachricht-
 Von: Michal Privoznik mpriv...@redhat.com 
 An: web2 usterman...@web.de , libvirt-users redhat.com 
 , libvirt-list redhat.com 
 Datum: Wed, 01 Oct 2014 18:12:45 +0200
 -
 
 
 
 On 01.10.2014 10:31, web2 wrote:
 
 Hello,

 sorry for my later answer.

 so, after i started libvirtd (no vm´s running) and attach gdb i get 
 the 
 following threads

 (gdb) info thread
 Id Target Id Frame
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
 85
 
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
 85
 
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
 85
 
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
 85
 
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
 85
 
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
 85
 
 5 Thread 0x7f18fbf48700 (LWP 20701) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
 85
 
 4 Thread 0x7f18fb747700 (LWP 20702) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
 85
 
 3 Thread 0x7f18faf46700 (LWP 20703) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
 85
 
 2 Thread 0x7f18fa745700 (LWP 20704) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
 85
 
 * 1 Thread 0x7f190892f840 (LWP 20694) libvirtd 
 0x7f190677d7cd in 
 poll () at ../sysdeps/unix/syscall-template.S:81

 if i restore an persistent domain, i see the following in gdb:

 Detaching after fork from child process 20880.
 Detaching after fork from child process 20882.
 [New Thread 0x7f190893d700 (LWP 20883)]
 Detaching after fork from child process 20890.
 Detaching after fork from child process 20906.

 (gdb) info thread
 Id Target Id Frame
 12 Thread 0x7f190893d700 (LWP 20883) libvirtd 
 0x7f1906e6684d in 
 read () at ../sysdeps/unix/syscall-template.S:81
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
 85
 
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
 85
 
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
 85
 
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
 85
 
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
 85
 
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 
 ../nptl/sysdeps/unix/sysv/linux

Re: [libvirt-users] [libvirt] increase number of libvirt threads by starting tansient guest doamin - is it a bug?

2014-10-02 Thread web2
 
 
ursprüngliche Nachricht-
Von: Jim Fehlig jfeh...@suse.com 
An: web2 usterman...@web.de 
Kopie: Michal Privoznik mpriv...@redhat.com , libvirt-users redhat.com 
, libvirt-list redhat.com 
Datum: Wed, 01 Oct 2014 21:38:05 -0600
-
 
 
 web2 wrote:
 Hi
 
 ursprüngliche Nachricht-
 Von: Michal Privoznik mpriv...@redhat.com 
 An: web2 usterman...@web.de , libvirt-users redhat.com 
 , libvirt-list redhat.com 
 Datum: Wed, 01 Oct 2014 18:12:45 +0200
 -
 
 
 
 On 01.10.2014 10:31, web2 wrote:
 
 Hello,

 sorry for my later answer.

 so, after i started libvirtd (no vm´s running) and attach gdb i get the 
 following threads

 (gdb) info thread
 Id Target Id Frame
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 5 Thread 0x7f18fbf48700 (LWP 20701) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 4 Thread 0x7f18fb747700 (LWP 20702) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 3 Thread 0x7f18faf46700 (LWP 20703) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 2 Thread 0x7f18fa745700 (LWP 20704) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 * 1 Thread 0x7f190892f840 (LWP 20694) libvirtd 
 0x7f190677d7cd in 
 poll () at ../sysdeps/unix/syscall-template.S:81

 if i restore an persistent domain, i see the following in gdb:

 Detaching after fork from child process 20880.
 Detaching after fork from child process 20882.
 [New Thread 0x7f190893d700 (LWP 20883)]
 Detaching after fork from child process 20890.
 Detaching after fork from child process 20906.

 (gdb) info thread
 Id Target Id Frame
 12 Thread 0x7f190893d700 (LWP 20883) libvirtd 
 0x7f1906e6684d in 
 read () at ../sysdeps/unix/syscall-template.S:81
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 5 Thread 0x7f18fbf48700 (LWP 20701) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 4 Thread 0x7f18fb747700 (LWP 20702) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 3 Thread 0x7f18faf46700 (LWP 20703) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 2 Thread 0x7f18fa745700 (LWP 20704) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 * 1 Thread 0x7f190892f840 (LWP 20694) libvirtd 
 0x7f190677d7cd in 
 poll () at ../sysdeps/unix/syscall-template.S:81

 if i now destroy this vm i get the following:


 (gdb) info thread
 Id Target Id Frame
 12 Thread 0x7f190893d700 (LWP 20883) libvirtd 
 0x7f1906e6684d in 
 read () at ../sysdeps/unix/syscall-template.S:81
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 10 Thread

Re: [libvirt] increase number of libvirt threads by starting tansient guest doamin - is it a bug?

2014-10-02 Thread web2
 
 
ursprüngliche Nachricht-
Von: Jim Fehlig jfeh...@suse.com 
An: web2 usterman...@web.de 
Kopie: Michal Privoznik mpriv...@redhat.com , libvirt-users redhat.com 
, libvirt-list redhat.com 
Datum: Wed, 01 Oct 2014 21:38:05 -0600
-
 
 
 web2 wrote:
 Hi
 
 ursprüngliche Nachricht-
 Von: Michal Privoznik mpriv...@redhat.com 
 An: web2 usterman...@web.de , libvirt-users redhat.com 
 , libvirt-list redhat.com 
 Datum: Wed, 01 Oct 2014 18:12:45 +0200
 -
 
 
 
 On 01.10.2014 10:31, web2 wrote:
 
 Hello,

 sorry for my later answer.

 so, after i started libvirtd (no vm´s running) and attach gdb i get the 
 following threads

 (gdb) info thread
 Id Target Id Frame
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 5 Thread 0x7f18fbf48700 (LWP 20701) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 4 Thread 0x7f18fb747700 (LWP 20702) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 3 Thread 0x7f18faf46700 (LWP 20703) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 2 Thread 0x7f18fa745700 (LWP 20704) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 * 1 Thread 0x7f190892f840 (LWP 20694) libvirtd 
 0x7f190677d7cd in 
 poll () at ../sysdeps/unix/syscall-template.S:81

 if i restore an persistent domain, i see the following in gdb:

 Detaching after fork from child process 20880.
 Detaching after fork from child process 20882.
 [New Thread 0x7f190893d700 (LWP 20883)]
 Detaching after fork from child process 20890.
 Detaching after fork from child process 20906.

 (gdb) info thread
 Id Target Id Frame
 12 Thread 0x7f190893d700 (LWP 20883) libvirtd 
 0x7f1906e6684d in 
 read () at ../sysdeps/unix/syscall-template.S:81
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 5 Thread 0x7f18fbf48700 (LWP 20701) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 4 Thread 0x7f18fb747700 (LWP 20702) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 3 Thread 0x7f18faf46700 (LWP 20703) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 2 Thread 0x7f18fa745700 (LWP 20704) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 * 1 Thread 0x7f190892f840 (LWP 20694) libvirtd 
 0x7f190677d7cd in 
 poll () at ../sysdeps/unix/syscall-template.S:81

 if i now destroy this vm i get the following:


 (gdb) info thread
 Id Target Id Frame
 12 Thread 0x7f190893d700 (LWP 20883) libvirtd 
 0x7f1906e6684d in 
 read () at ../sysdeps/unix/syscall-template.S:81
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 
 10 Thread

Re: [libvirt-users] [libvirt] increase number of libvirt threads by starting tansient guest doamin - is it a bug?

2014-10-01 Thread web2
 Hello,

sorry for my later answer.

so, after i started libvirtd (no vm´s running) and attach gdb i get the 
following threads

(gdb) info thread
 Id Target Id Frame 
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 5 Thread 0x7f18fbf48700 (LWP 20701) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 4 Thread 0x7f18fb747700 (LWP 20702) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 3 Thread 0x7f18faf46700 (LWP 20703) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 2 Thread 0x7f18fa745700 (LWP 20704) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
* 1 Thread 0x7f190892f840 (LWP 20694) libvirtd 0x7f190677d7cd in poll () 
at ../sysdeps/unix/syscall-template.S:81

if i restore an persistent domain, i see the following in gdb:

Detaching after fork from child process 20880.
Detaching after fork from child process 20882.
[New Thread 0x7f190893d700 (LWP 20883)]
Detaching after fork from child process 20890.
Detaching after fork from child process 20906.

(gdb) info thread
 Id Target Id Frame 
 12 Thread 0x7f190893d700 (LWP 20883) libvirtd 0x7f1906e6684d in read () 
at ../sysdeps/unix/syscall-template.S:81
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 5 Thread 0x7f18fbf48700 (LWP 20701) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 4 Thread 0x7f18fb747700 (LWP 20702) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 3 Thread 0x7f18faf46700 (LWP 20703) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 2 Thread 0x7f18fa745700 (LWP 20704) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
* 1 Thread 0x7f190892f840 (LWP 20694) libvirtd 0x7f190677d7cd in poll () 
at ../sysdeps/unix/syscall-template.S:81

if i now destroy this vm i get the following:


(gdb) info thread
 Id Target Id Frame 
 12 Thread 0x7f190893d700 (LWP 20883) libvirtd 0x7f1906e6684d in read () 
at ../sysdeps/unix/syscall-template.S:81
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 5 Thread 0x7f18fbf48700 (LWP 20701) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at 

Re: [libvirt-users] [libvirt] increase number of libvirt threads by starting tansient guest doamin - is it a bug?

2014-10-01 Thread web2
 Hi,

if i test the restore/destroy of an KVM/QEMU vm on the same system (fedora core 
20 libvirtd 1.1.3.5), i can confirm what you say.
there are no threads which are created and then not closed!

so my problem/observation affects the interaction of libvirtd/xen.

all the best 
max
 
ursprüngliche Nachricht-
Von: Jim Fehlig jfeh...@suse.com 
An: usterman...@web.de 
Kopie: libvir-l...@redhat.com, libvirt-users@redhat.com 
Datum: Tue, 30 Sep 2014 18:44:17 -0600
-
 
 
 usterman...@web.de wrote:
 hello,

 if i start a transient guest doamin via virsh create abcd.xml i see an 
 additional libvirt thread and also some open files:

 pstree -h `pgrep libvirtd`
 libvirtd───11*[{libvirtd}]

 libvirtd 3016 root 21w REG 253,0 6044 1052094 
 /var/log/libvirt/libxl/abcd.log
 libvirtd 3016 root 22r FIFO 0,8 0t0 126124 pipe
 libvirtd 3016 root 23w FIFO 0,8 0t0 126124 pipe
 libvirtd 3016 root 24u REG 0,37 0 4 /proc/xen/privcmd
 libvirtd 3016 root 25u unix 0x8807d2c3ad80 0t0 126125 socket
 libvirtd 3016 root 26r FIFO 0,8 0t0 126127 pipe
 libvirtd 3016 root 27w FIFO 0,8 0t0 126127 pipe
 libvirtd 3016 root 28r FIFO 0,8 0t0 124783 pipe
 libvirtd 3016 root 29w FIFO 0,8 0t0 124783 pipe
 libvirtd 3016 root 30r FIFO 0,8 0t0 127140 pipe
 libvirtd 3016 root 31w FIFO 0,8 0t0 127140 pipe

 if i destroy these vm via virsh destroy abcd, i see that the additional 
 thread still exists and also the list of openfiles is the same.
 
 
 I don't see this behavior with current libvirt git master
 
 # pstree `pgrep libvirtd`
 libvirtd───10*[{libvirtd}]
 # virsh create ./test.xml
 Domain test created from ./test.xml
 # pstree `pgrep libvirtd`
 libvirtd───11*[{libvirtd}]
 # virsh destroy test
 Domain test destroyed
 # pstree `pgrep libvirtd`
 libvirtd───10*[{libvirtd}]
 
 All file descriptors opened when the domain was created were closed as well.
 
 What version of libvirt are you using?
 
 Regards,
 Jim
 
 

-- 




___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users

Re: [libvirt-users] [libvirt] increase number of libvirt threads by starting tansient guest doamin - is it a bug?

2014-10-01 Thread web2
 Hi
 
ursprüngliche Nachricht-
Von: Michal Privoznik mpriv...@redhat.com 
An: web2 usterman...@web.de , libvirt-users redhat.com 
, libvirt-list redhat.com 
Datum: Wed, 01 Oct 2014 18:12:45 +0200
-
 
 
 On 01.10.2014 10:31, web2 wrote:
 Hello,

 sorry for my later answer.

 so, after i started libvirtd (no vm´s running) and attach gdb i get the 
 following threads

 (gdb) info thread
 Id Target Id Frame
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 5 Thread 0x7f18fbf48700 (LWP 20701) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 4 Thread 0x7f18fb747700 (LWP 20702) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 3 Thread 0x7f18faf46700 (LWP 20703) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 2 Thread 0x7f18fa745700 (LWP 20704) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 * 1 Thread 0x7f190892f840 (LWP 20694) libvirtd 0x7f190677d7cd in 
 poll () at ../sysdeps/unix/syscall-template.S:81

 if i restore an persistent domain, i see the following in gdb:

 Detaching after fork from child process 20880.
 Detaching after fork from child process 20882.
 [New Thread 0x7f190893d700 (LWP 20883)]
 Detaching after fork from child process 20890.
 Detaching after fork from child process 20906.

 (gdb) info thread
 Id Target Id Frame
 12 Thread 0x7f190893d700 (LWP 20883) libvirtd 0x7f1906e6684d in 
 read () at ../sysdeps/unix/syscall-template.S:81
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 5 Thread 0x7f18fbf48700 (LWP 20701) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 4 Thread 0x7f18fb747700 (LWP 20702) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 3 Thread 0x7f18faf46700 (LWP 20703) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 2 Thread 0x7f18fa745700 (LWP 20704) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 * 1 Thread 0x7f190892f840 (LWP 20694) libvirtd 0x7f190677d7cd in 
 poll () at ../sysdeps/unix/syscall-template.S:81

 if i now destroy this vm i get the following:


 (gdb) info thread
 Id Target Id Frame
 12 Thread 0x7f190893d700 (LWP 20883) libvirtd 0x7f1906e6684d in 
 read () at ../sysdeps/unix/syscall-template.S:81
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S

Re: [libvirt] increase number of libvirt threads by starting tansient guest doamin - is it a bug?

2014-10-01 Thread web2
 Hi Jim,

i use libvirt 1.1.3.5 on fedora core 20, the vm´s i startet are xen-vm´s.

i also take a look on libvirt 1.1.2 on an openSuSE 13.1 und also on libvirt 
1.0.2 on an OpenSuSE 12.3 and i didn´t see threads that are created and not 
closed . But on the openSuSE-Systems the vm´s are KVM/qemu.

on the fedora-system i will attach gdb to the libvirtd-process, and hope to see 
what´s doing on.

all the best
max

 
ursprüngliche Nachricht-
Von: Jim Fehlig jfeh...@suse.com 
An: usterman...@web.de 
Kopie: libvir-list@redhat.com, libvirt-us...@redhat.com 
Datum: Tue, 30 Sep 2014 18:44:17 -0600
-
 
 
 usterman...@web.de wrote:
 hello,

 if i start a transient guest doamin via virsh create abcd.xml i see an 
 additional libvirt thread and also some open files:

 pstree -h `pgrep libvirtd`
 libvirtd───11*[{libvirtd}]

 libvirtd 3016 root 21w REG 253,0 6044 1052094 
 /var/log/libvirt/libxl/abcd.log
 libvirtd 3016 root 22r FIFO 0,8 0t0 126124 pipe
 libvirtd 3016 root 23w FIFO 0,8 0t0 126124 pipe
 libvirtd 3016 root 24u REG 0,37 0 4 /proc/xen/privcmd
 libvirtd 3016 root 25u unix 0x8807d2c3ad80 0t0 126125 socket
 libvirtd 3016 root 26r FIFO 0,8 0t0 126127 pipe
 libvirtd 3016 root 27w FIFO 0,8 0t0 126127 pipe
 libvirtd 3016 root 28r FIFO 0,8 0t0 124783 pipe
 libvirtd 3016 root 29w FIFO 0,8 0t0 124783 pipe
 libvirtd 3016 root 30r FIFO 0,8 0t0 127140 pipe
 libvirtd 3016 root 31w FIFO 0,8 0t0 127140 pipe

 if i destroy these vm via virsh destroy abcd, i see that the additional 
 thread still exists and also the list of openfiles is the same.
 
 
 I don't see this behavior with current libvirt git master
 
 # pstree `pgrep libvirtd`
 libvirtd───10*[{libvirtd}]
 # virsh create ./test.xml
 Domain test created from ./test.xml
 # pstree `pgrep libvirtd`
 libvirtd───11*[{libvirtd}]
 # virsh destroy test
 Domain test destroyed
 # pstree `pgrep libvirtd`
 libvirtd───10*[{libvirtd}]
 
 All file descriptors opened when the domain was created were closed as well.
 
 What version of libvirt are you using?
 
 Regards,
 Jim
 
 

-- 




--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] increase number of libvirt threads by starting tansient guest doamin - is it a bug?

2014-10-01 Thread web2
 Hello,

sorry for my later answer.

so, after i started libvirtd (no vm´s running) and attach gdb i get the 
following threads

(gdb) info thread
 Id Target Id Frame 
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 5 Thread 0x7f18fbf48700 (LWP 20701) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 4 Thread 0x7f18fb747700 (LWP 20702) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 3 Thread 0x7f18faf46700 (LWP 20703) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 2 Thread 0x7f18fa745700 (LWP 20704) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
* 1 Thread 0x7f190892f840 (LWP 20694) libvirtd 0x7f190677d7cd in poll () 
at ../sysdeps/unix/syscall-template.S:81

if i restore an persistent domain, i see the following in gdb:

Detaching after fork from child process 20880.
Detaching after fork from child process 20882.
[New Thread 0x7f190893d700 (LWP 20883)]
Detaching after fork from child process 20890.
Detaching after fork from child process 20906.

(gdb) info thread
 Id Target Id Frame 
 12 Thread 0x7f190893d700 (LWP 20883) libvirtd 0x7f1906e6684d in read () 
at ../sysdeps/unix/syscall-template.S:81
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 5 Thread 0x7f18fbf48700 (LWP 20701) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 4 Thread 0x7f18fb747700 (LWP 20702) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 3 Thread 0x7f18faf46700 (LWP 20703) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 2 Thread 0x7f18fa745700 (LWP 20704) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
* 1 Thread 0x7f190892f840 (LWP 20694) libvirtd 0x7f190677d7cd in poll () 
at ../sysdeps/unix/syscall-template.S:81

if i now destroy this vm i get the following:


(gdb) info thread
 Id Target Id Frame 
 12 Thread 0x7f190893d700 (LWP 20883) libvirtd 0x7f1906e6684d in read () 
at ../sysdeps/unix/syscall-template.S:81
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 5 Thread 0x7f18fbf48700 (LWP 20701) libvirtd pthread_cond_wait@@GLIBC_2.3.2 
() at 

Re: [libvirt] increase number of libvirt threads by starting tansient guest doamin - is it a bug?

2014-10-01 Thread web2
 Hi
 
ursprüngliche Nachricht-
Von: Michal Privoznik mpriv...@redhat.com 
An: web2 usterman...@web.de , libvirt-users redhat.com 
, libvirt-list redhat.com 
Datum: Wed, 01 Oct 2014 18:12:45 +0200
-
 
 
 On 01.10.2014 10:31, web2 wrote:
 Hello,

 sorry for my later answer.

 so, after i started libvirtd (no vm´s running) and attach gdb i get the 
 following threads

 (gdb) info thread
 Id Target Id Frame
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 5 Thread 0x7f18fbf48700 (LWP 20701) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 4 Thread 0x7f18fb747700 (LWP 20702) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 3 Thread 0x7f18faf46700 (LWP 20703) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 2 Thread 0x7f18fa745700 (LWP 20704) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 * 1 Thread 0x7f190892f840 (LWP 20694) libvirtd 0x7f190677d7cd in 
 poll () at ../sysdeps/unix/syscall-template.S:81

 if i restore an persistent domain, i see the following in gdb:

 Detaching after fork from child process 20880.
 Detaching after fork from child process 20882.
 [New Thread 0x7f190893d700 (LWP 20883)]
 Detaching after fork from child process 20890.
 Detaching after fork from child process 20906.

 (gdb) info thread
 Id Target Id Frame
 12 Thread 0x7f190893d700 (LWP 20883) libvirtd 0x7f1906e6684d in 
 read () at ../sysdeps/unix/syscall-template.S:81
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 7 Thread 0x7f18fcf4a700 (LWP 20699) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 6 Thread 0x7f18fc749700 (LWP 20700) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 5 Thread 0x7f18fbf48700 (LWP 20701) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 4 Thread 0x7f18fb747700 (LWP 20702) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 3 Thread 0x7f18faf46700 (LWP 20703) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 2 Thread 0x7f18fa745700 (LWP 20704) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 * 1 Thread 0x7f190892f840 (LWP 20694) libvirtd 0x7f190677d7cd in 
 poll () at ../sysdeps/unix/syscall-template.S:81

 if i now destroy this vm i get the following:


 (gdb) info thread
 Id Target Id Frame
 12 Thread 0x7f190893d700 (LWP 20883) libvirtd 0x7f1906e6684d in 
 read () at ../sysdeps/unix/syscall-template.S:81
 11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 10 Thread 0x7f18fe74d700 (LWP 20696) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 9 Thread 0x7f18fdf4c700 (LWP 20697) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 8 Thread 0x7f18fd74b700 (LWP 20698) libvirtd 
 pthread_cond_wait@@GLIBC_2.3.2 () at 
 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S

[no subject]

2014-09-29 Thread web2
subscribe kvm-commits

--
To unsubscribe from this list: send the line unsubscribe kvm-commits in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[no subject]

2014-09-29 Thread web2
subscribe kvm


--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Apache 7, Logrotate

2013-10-28 Thread Web2 Solutions
Hallo Rainer,


   	   
   	Rainer Jung  
  27 Oct 2013 14:23
  Only
 for the access log: there's a property checkExists="true", thatwill
 close the file and reopen it if the access log valve detects thefile
 has been moved/renamed. That option could be more expensive thoughthen
 just using an appropriate value for fileDateFormat.

great! I did not know about it. Let me try it. So I'm left only with 
catalina.out.
Thank you!


  
Regards,Rainer
  

Michael

  
-To
 unsubscribe, e-mail: users-unsubscr...@tomcat.apache.orgFor 
additional commands, e-mail: users-h...@tomcat.apache.org
  
   	   
   	Konstantin Kolinko  
  25 Oct 2013 11:54
  2013/10/25 Web2 Solutions m...@web2-solutions.com:
Hallo All,

I've installed tomcat 7.0.42 and due heavy use my catalina.out and
localhost_access-jjj-mm-dd.txt grows quit big.

I've successfully configured logrotate to rotate both files. I've removed
the date from the access log.
So Tomcat now writes without rotating into localhost_access.txt

Logrotate now create a new file (localhost_access-dd-mm-dd.txt) and makes
localhost_access.txt empty.
But tomcat now writes into the new localhost_access-dd-mm-dd.txt instead of
the configured file (localhost_access.txt).

FYI:
You can configure the filename pattern so that it rotates more frequently,
e.g. every hour or every ten minutes.

What do I have todo so that tomcat continues to write into
localhost_access.txt  even after rotating?

Renaming the file is futile, because Tomcat (for access logs) or the
shell (for catalina.out)
has the file open and continues to write to it, regardless of the file name.

You can use copytruncate option of logrotate.

FYI: catalina.out is not a proper log file, but a redirection of
stdout (as managed in catalina.sh script that launches Tomcat java
process). If a system is configured properly, this file is usually
empty.

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


   	   
   	Web2 Solutions  
  25 Oct 2013 00:33
  Hallo All,

I've installed tomcat 7.0.42 and due heavy use my catalina.out and 
localhost_access-jjj-mm-dd.txt grows quit big.

I've successfully configured logrotate to rotate both files. I've 
removed the date from the access log.
So Tomcat now writes without rotating into localhost_access.txt

Logrotate now create a new file (localhost_access-dd-mm-dd.txt) and 
makes localhost_access.txt empty.
But tomcat now writes into the new localhost_access-dd-mm-dd.txt 
instead 
of the configured file (localhost_access.txt).

What do I have todo so that tomcat continues to write into 
localhost_access.txt  even after rotating?

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org






Re: Apache Tomcat 7, Logrotate

2013-10-25 Thread Web2 Solutions
Hallo David,




   	   
   	David N. Smith  
  25 Oct 2013 13:42
  I
 think here is where you get confused.  The "original (empty) file" is 
not the original file.  It is a new file that happens to have the same 
name as the the one that was renamed.  The true original file is the one
 that was renamed and tomcat continues to use it completely unaware of 
your rename.  

thx, I got that now. 


  
Configuring your apps to use a true logging system and 
configuring the log system to rotate is the best option.  Barring that, 
it get's tricky.  You might be able to get away with copying the log 
file to another and then truncating the original but I think that only 
really works on *nix based systems.  Windows if memory serves will pad 
the truncated file with empty space and append right were it left off.  
  

I'm on linux and I would test the moving renamed file to a 
new folder. How comes Tomcat does not have a layer for logrotate for 
this?!


  
There has been discussion on the list in the past about 
this if your interested in doing some searching.
  

Ok, I'll make a search.

  
--David
  


Thx,
Michael

  
-To
 unsubscribe, e-mail: users-unsubscr...@tomcat.apache.orgFor 
additional commands, e-mail: users-h...@tomcat.apache.org
  
   	   
   	Konstantin Kolinko  
  25 Oct 2013 11:54
  2013/10/25 Web2 Solutions m...@web2-solutions.com:
Hallo All,

I've installed tomcat 7.0.42 and due heavy use my catalina.out and
localhost_access-jjj-mm-dd.txt grows quit big.

I've successfully configured logrotate to rotate both files. I've removed
the date from the access log.
So Tomcat now writes without rotating into localhost_access.txt

Logrotate now create a new file (localhost_access-dd-mm-dd.txt) and makes
localhost_access.txt empty.
But tomcat now writes into the new localhost_access-dd-mm-dd.txt instead of
the configured file (localhost_access.txt).

FYI:
You can configure the filename pattern so that it rotates more frequently,
e.g. every hour or every ten minutes.

What do I have todo so that tomcat continues to write into
localhost_access.txt  even after rotating?

Renaming the file is futile, because Tomcat (for access logs) or the
shell (for catalina.out)
has the file open and continues to write to it, regardless of the file name.

You can use copytruncate option of logrotate.

FYI: catalina.out is not a proper log file, but a redirection of
stdout (as managed in catalina.sh script that launches Tomcat java
process). If a system is configured properly, this file is usually
empty.

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


   	   
   	Web2 Solutions  
  25 Oct 2013 00:33
  Hallo All,

I've installed tomcat 7.0.42 and due heavy use my catalina.out and 
localhost_access-jjj-mm-dd.txt grows quit big.

I've successfully configured logrotate to rotate both files. I've 
removed the date from the access log.
So Tomcat now writes without rotating into localhost_access.txt

Logrotate now create a new file (localhost_access-dd-mm-dd.txt) and 
makes localhost_access.txt empty.
But tomcat now writes into the new localhost_access-dd-mm-dd.txt 
instead 
of the configured file (localhost_access.txt).

What do I have todo so that tomcat continues to write into 
localhost_access.txt even after rotating?

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org






Apache 7, Logrotate

2013-10-24 Thread Web2 Solutions

Hallo All,

I've installed tomcat 7.0.42 and due heavy use my catalina.out and 
localhost_access-jjj-mm-dd.txt grows quit big.


I've successfully configured logrotate to rotate both files. I've 
removed the date from the access log.

So Tomcat now writes without rotating into localhost_access.txt

Logrotate now create a new file (localhost_access-dd-mm-dd.txt) and 
makes localhost_access.txt empty.
But tomcat now writes into the new localhost_access-dd-mm-dd.txt instead 
of the configured file (localhost_access.txt).


What do I have todo so that tomcat continues to write into 
localhost_access.txt  even after rotating?


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: CSRF verification failed. Request aborted.

2011-10-22 Thread web2 . 0+google
On Sat, 22 Oct 2011 19:21:59 +0100
Kayode Odeyemi  wrote:

> I am accessing my view from a Drupal application that sends in data
> via POST. I'm not using any REST API such as
> piston, django-tastypie.
> 
> A few days ago, I'm smiling and happy that it all worked. Today, it's
> a different story. I'm currently getting:
> 
> Forbidden (403)
> 
> CSRF verification failed. Request aborted.

Of course. Drupal cannot know about the CSRF token it has to send.

You'd need to disable the CSRF-Check for that view.
You can use the csrf_exempt decorator for example, found in the
django.views.decorators.csrf module.

Regards,
ch3ka

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.



Re: I hope they are restoring compatibility with microbadges on older computers/browsers...

2010-03-08 Thread Web2-programmer
I believe FF3.6 is the most thoroughly planned browser created.
If you don't like the look of the FF3 compared with Ff2, I believe
there is an add-on that can make it look vintage.
In fact, I just saw a discussion on the geek before they shut down for
the night  about some safety features, web2.0 development tools, BGG
add-ons for FF/chrome/Opera etc. Something Pimp your browser
something something in the geeklists, might be worth taking a look.
I highly recommend opera, but few seem to like it since Chrome came
out - often times the IT people at work are very susceptible to
installing better browsers than IE (especially IE6!!!, some companies
are clearly inviting viruses) when presented with good evidence why a
change might be great.

G'night everyone.
Dan.



On Mar 3, 10:57 pm, Duglis dug...@gmail.com wrote:
 I hope they are restoring compatibility with microbadges on older
 computers/browsers...flag viewing too, etc.

 The newer browsers wont' work with my OS. That would make all but  5
 of my microbadges purchases worthless for me. :(

 that's alot of GG :(

 anyway, good luck with fixing whatever you are fixing!

 Maarten D. de Jong
View profile
 More options Mar 4, 12:06 am
From: Maarten D. de Jong irm...@gmail.com
Date: Thu, 4 Mar 2010 00:06:40 -0800 (PST)
Local: Thurs, Mar 4 2010 12:06 am
Subject: Re: I hope they are restoring compatibility with microbadges
on older computers/browsers...
Reply | Reply to author | Forward | Print | Individual message | Show
original | Report this message | Find messages by this author
For me a reason to hold on to Firefox 2 instead of going to FF3 was
the terrible Awfulbar:


-- 
You received this message because you are subscribed to the Google Groups BGG 
Down group.
To post to this group, send email to bgg_d...@googlegroups.com.
To unsubscribe from this group, send email to 
bgg_down+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/bgg_down?hl=en.



See on your Google homepage

2008-12-13 Thread web2 . danipermana
Your friend, web2.daniperm...@gmail.com, has sent you the following Google  
Gadget and included this message:


See  on your Google homepage »



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
SAPNEEDS group.
To post to this group, send email to sapneeds@googlegroups.com
To unsubscribe from this group, send email to 
sapneeds+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sapneeds?hl=en
-~--~~~~--~~--~--~---



Re: [PHP] mail function problem

2007-07-05 Thread web2

Chris a écrit :

web2 wrote:

Chris a écrit :



Try this:
?
$email = [EMAIL PROTECTED];
$headers  = From: .$email.\r\n;
$headers .= X-Mailer: PHP/.phpversion().\r\n;
if(mail([EMAIL PROTECTED],essai,test,$headers)) {
   echo OK: .ini_get('sendmail_path');
} else {
   echo NOK: .ini_get('sendmail_path');
}
?

   Note


Same result : NOK /usr/lib/sendmail -t -i
I think the problem is not in the test script.




Is that the right path? Normally it's /usr/sbin/sendmail not /usr/lib .


Yes, /usr/sbin/sendmail is a link to /usr/lib/sendmail.

I've made tests and with the php binary (php -f myscript.php), the 
mail is send.

It only doesn't work with the apache module (libphp5.so)...

So, it confirms that the script and the PHP configuration (php.ini) 
are OK.


Are you running SeLinux by any chance? Check your /var/log/messages 
and/or /var/log/syslog to see if they provide any answers.


I'm not running SeLinux, I'm using Solaris 10 (AMD64), and I've checked 
syslog and messages but there's nothing...


--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] mail function problem

2007-07-04 Thread web2

Chris a écrit :



Try this:
?
$email = [EMAIL PROTECTED];
$headers  = From: .$email.\r\n;
$headers .= X-Mailer: PHP/.phpversion().\r\n;
if(mail([EMAIL PROTECTED],essai,test,$headers)) {
   echo OK: .ini_get('sendmail_path');
} else {
   echo NOK: .ini_get('sendmail_path');
}
?

   Note


Same result : NOK /usr/lib/sendmail -t -i
I think the problem is not in the test script.




Is that the right path? Normally it's /usr/sbin/sendmail not /usr/lib .


Yes, /usr/sbin/sendmail is a link to /usr/lib/sendmail.

I've made tests and with the php binary (php -f myscript.php), the mail 
is send.

It only doesn't work with the apache module (libphp5.so)...

So, it confirms that the script and the PHP configuration (php.ini) are OK.

If you have any solutions...

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] mail function problem

2007-07-03 Thread web2

Daniel Brown a écrit :

On 7/2/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

Daniel Brown a écrit :
 On 7/2/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 I've already checked :

 - the mail logs : no mail send

 - and the apache error and access logs : nothing except this :

 192.168.0.1 - - [02/Jul/2007:14:07:22 +0200] GET /~ee/mail.php
 HTTP/1.1 200 49291 - Mozilla/5.0 (Windows; U; Windows NT 5.1; fr;
 rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
 192.168.0.1 - - [02/Jul/2007:14:07:22 +0200] GET
 /~ee/mail.php?=PHPE9568F34-D428-11d2-A769-00AA001ACF42 
HTTP/1.1 200
 2524 http://mysite.domain.do/~ee/mail.php; Mozilla/5.0 
(Windows;

 U; Windows NT 5.1; fr; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
 192.168.0.1 - - [02/Jul/2007:14:07:22 +0200] GET
 /~ee/mail.php?=SUHO8567F54-D428-14d2-A769-00DA302A5F18 
HTTP/1.1 200
 2813 http://mysite.domain.do/~ee/mail.php; Mozilla/5.0 
(Windows;

 U; Windows NT 5.1; fr; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
 192.168.0.1 - - [02/Jul/2007:14:07:22 +0200] GET
 /~ee/mail.php?=PHPE9568F35-D428-11d2-A769-00AA001ACF42 
HTTP/1.1 200
 2146 http://mysite.domain.do/~ee/mail.php; Mozilla/5.0 
(Windows;

 U; Windows NT 5.1; fr; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4



 Chris a écrit :
  [EMAIL PROTECTED] wrote:
  Hi,
 
  I'm running PHP 5.2.3 on Solaris 10 (AMD64).
 
  My mail function doesn't send any mail, the return value of mail
  function is false...
  But sendmail_path value is OK in php.ini, and I've tried to send a
  mail with sendmail on console with the same user (the apache 
user),

  and everything's ok...
 
  Does anyone have solution ?
 
  Check your mail logs and your apache logs to see if any errors are
  showing up.
 

 --
 PHP General Mailing List (http://www.php.net/)
 To unsubscribe, visit: http://www.php.net/unsub.php



Is it possible for you to provide your code so that we can take a
 look at it for you?


Yes, my PHP test code is :

?
ini_set(display_errors, true);
ini_set(error_reporting, E_ALL);
$Email=[EMAIL PROTECTED];
$headers = From:  . $Email . \r\nX-Mailer: PHP/ . phpversion();
if ( mail([EMAIL PROTECTED] , essai , test, $headers) )
echo OK : .ini_get('sendmail_path');
else
echo NOK : .ini_get('sendmail_path');
?



Try this:
?
$email = [EMAIL PROTECTED];
$headers  = From: .$email.\r\n;
$headers .= X-Mailer: PHP/.phpversion().\r\n;
if(mail([EMAIL PROTECTED],essai,test,$headers)) {
   echo OK: .ini_get('sendmail_path');
} else {
   echo NOK: .ini_get('sendmail_path');
}
?

   Note


Same result : NOK /usr/lib/sendmail -t -i
I think the problem is not in the test script.

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] mail function problem

2007-07-02 Thread web2

I've already checked :

- the mail logs : no mail send

- and the apache error and access logs : nothing except this :

192.168.0.1 - - [02/Jul/2007:14:07:22 +0200] GET /~ee/mail.php 
HTTP/1.1 200 49291 - Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; 
rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
192.168.0.1 - - [02/Jul/2007:14:07:22 +0200] GET 
/~ee/mail.php?=PHPE9568F34-D428-11d2-A769-00AA001ACF42 HTTP/1.1 200 
2524 http://mysite.domain.do/~ee/mail.php; Mozilla/5.0 (Windows; 
U; Windows NT 5.1; fr; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
192.168.0.1 - - [02/Jul/2007:14:07:22 +0200] GET 
/~ee/mail.php?=SUHO8567F54-D428-14d2-A769-00DA302A5F18 HTTP/1.1 200 
2813 http://mysite.domain.do/~ee/mail.php; Mozilla/5.0 (Windows; 
U; Windows NT 5.1; fr; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
192.168.0.1 - - [02/Jul/2007:14:07:22 +0200] GET 
/~ee/mail.php?=PHPE9568F35-D428-11d2-A769-00AA001ACF42 HTTP/1.1 200 
2146 http://mysite.domain.do/~ee/mail.php; Mozilla/5.0 (Windows; 
U; Windows NT 5.1; fr; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4




Chris a écrit :

[EMAIL PROTECTED] wrote:

Hi,

I'm running PHP 5.2.3 on Solaris 10 (AMD64).

My mail function doesn't send any mail, the return value of mail 
function is false...
But sendmail_path value is OK in php.ini, and I've tried to send a 
mail with sendmail on console with the same user (the apache user), 
and everything's ok...


Does anyone have solution ?


Check your mail logs and your apache logs to see if any errors are 
showing up.




--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] mail function problem

2007-07-02 Thread web2

Daniel Brown a écrit :

On 7/2/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

I've already checked :

- the mail logs : no mail send

- and the apache error and access logs : nothing except this :

192.168.0.1 - - [02/Jul/2007:14:07:22 +0200] GET /~ee/mail.php
HTTP/1.1 200 49291 - Mozilla/5.0 (Windows; U; Windows NT 5.1; fr;
rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
192.168.0.1 - - [02/Jul/2007:14:07:22 +0200] GET
/~ee/mail.php?=PHPE9568F34-D428-11d2-A769-00AA001ACF42 HTTP/1.1 200
2524 http://mysite.domain.do/~ee/mail.php; Mozilla/5.0 (Windows;
U; Windows NT 5.1; fr; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
192.168.0.1 - - [02/Jul/2007:14:07:22 +0200] GET
/~ee/mail.php?=SUHO8567F54-D428-14d2-A769-00DA302A5F18 HTTP/1.1 200
2813 http://mysite.domain.do/~ee/mail.php; Mozilla/5.0 (Windows;
U; Windows NT 5.1; fr; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
192.168.0.1 - - [02/Jul/2007:14:07:22 +0200] GET
/~ee/mail.php?=PHPE9568F35-D428-11d2-A769-00AA001ACF42 HTTP/1.1 200
2146 http://mysite.domain.do/~ee/mail.php; Mozilla/5.0 (Windows;
U; Windows NT 5.1; fr; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4



Chris a écrit :
 [EMAIL PROTECTED] wrote:
 Hi,

 I'm running PHP 5.2.3 on Solaris 10 (AMD64).

 My mail function doesn't send any mail, the return value of mail
 function is false...
 But sendmail_path value is OK in php.ini, and I've tried to send a
 mail with sendmail on console with the same user (the apache user),
 and everything's ok...

 Does anyone have solution ?

 Check your mail logs and your apache logs to see if any errors are
 showing up.


--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




   Is it possible for you to provide your code so that we can take a
look at it for you?



Yes, my PHP test code is :

?
ini_set(display_errors, true);
ini_set(error_reporting, E_ALL);
$Email=[EMAIL PROTECTED];
$headers = From:  . $Email . \r\nX-Mailer: PHP/ . phpversion();
if ( mail([EMAIL PROTECTED] , essai , test, $headers) )
echo OK : .ini_get('sendmail_path');
else
echo NOK : .ini_get('sendmail_path');
?

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



[PHP] mail function problem

2007-06-29 Thread web2

Hi,

I'm running PHP 5.2.3 on Solaris 10 (AMD64).

My mail function doesn't send any mail, the return value of mail 
function is false...
But sendmail_path value is OK in php.ini, and I've tried to send a mail 
with sendmail on console with the same user (the apache user), and 
everything's ok...


Does anyone have solution ?

Thanks for help.

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP-INSTALL] PHP 5.2.3 module on Solaris 10 (AMD64)

2007-06-14 Thread web2

I've found a solution :

Add these two lines :
LD_PRELOAD=/usr/lib/64/libmtmalloc.so.1
export LD_PRELOAD
in [APACHE_HOME]/bin/envvars

Hope it'll help.


AAcom Lists a écrit :

Salut,
it seems you are compiling the whole bunch in 64bit mode (file libphp5.so)
but you are linking php with a 32bit library (/usr/lib) in place of 
64bit (/usr/lib/64/libmtmalloc.so.1).
You must discover the place where this lib is used (a Makefile in php 
sources),

may be an extension,
and force -L/usr/lib/64 -R/usr/lib/64 before the -lmtmalloc

[EMAIL PROTECTED] a écrit :
I tried the latest version 5.2.3 on Solaris 10(AMD64) as a module on 
Apache 2.0.59.
After the compilation, and installation, I've tried to restart Apache 
and I have this error message :


Syntax error on line 232 of /www/apache-2.0.59/conf/httpd.conf:
Cannot load /www/apache2/modules/libphp5.so into server: ld.so.1: httpd:
fatal: /usr/lib/libmtmalloc.so.1: wrong ELF class: ELFCLASS32

For info, everything's ok with PHP 5.2.2.

Thanks for help


[PHP-INSTALL] PHP 5.2.3 module on Solaris 10 (AMD64)

2007-06-13 Thread web2
I tried the latest version 5.2.3 on Solaris 10(AMD64) as a module on 
Apache 2.0.59.
After the compilation, and installation, I've tried to restart Apache 
and I have this error message :


Syntax error on line 232 of /www/apache-2.0.59/conf/httpd.conf:
Cannot load /www/apache2/modules/libphp5.so into server: ld.so.1: httpd:
fatal: /usr/lib/libmtmalloc.so.1: wrong ELF class: ELFCLASS32

For info, everything's ok with PHP 5.2.2.

Thanks for help