search for: libpthreads

2018-01-17 17:32 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: > Sounds like qemuConnectGetAllDomainStats() forgot to unset the job on a > domain. Can you please attach gdb to libvirtd and run 't a a bt' and > share the output? > > Michal > This is output of gdb 't a a bt' ~5 seconds after that error message appeared in log with

Hi,I am having an issue on several KVM hosts which run CentOs7 and libvirt-daemon-1.2.17-13.el7_2.3.x86_64 .About once a week the libvirtd hangs forever and becomes unresponsive, the only help is to restart it. I attached gdb to it and the output of it can be seen at the end of the mail. Laine from the irc channel suggests it has to do with dbus/policykit. If anybody got an idea what it could be

В письме от Вторник, 25-июн-2013 11:47:10 пользователь Michal Privoznik написал: > On 24.06.2013 11:36, Александр wrote: > > libvirtd will lock if for example kill programm which established > > connection,> > > only sigkill + restart helps., to reproduce: > > virConnectPtr libvirt_connection = virConnectOpen("qemu:///system"); > >

Some corrections about the previous mails. Problem does not happen when no volumes created. Problem happens volumes created but in stopped state. Problem also happens when volumes started state. Below is the 5 stack traces taken by 10 min intervals and volumes stopped state. --1-- Thread 8 (Thread 0x7f413f3a7700 (LWP 104249)): #0 0x0000003d99c0f00d in nanosleep () from /lib64/libpthread.so.0 #1

On Tue, Sep 5, 2017 at 6:13 PM, Serkan ?oban <cobanserkan at gmail.com> wrote: > Some corrections about the previous mails. Problem does not happen > when no volumes created. > Problem happens volumes created but in stopped state. Problem also > happens when volumes started state. > Below is the 5 stack traces taken by 10 min intervals and volumes stopped > state. > As

On Mon, 4 Sep 2017 at 20:04, Serkan ?oban <cobanserkan at gmail.com> wrote: > I have been using a 60 server 1560 brick 3.7.11 cluster without > problems for 1 years. I did not see this problem with it. > Note that this problem does not happen when I install packages & start > glusterd & peer probe and create the volumes. But after glusterd > restart. > > Also

On 20.06.2013 12:56, Alexandr wrote: > On 20.06.2013 10:44, Michal Privoznik wrote: >> On 20.06.2013 09:40, Александр wrote: >>> В письме от Четверг, 20-июн-2013 09:15:14 Вы написали: >>>> On 19.06.2013 21:24, Александр wrote: >>>>> В письме от Среда, 19-июн-2013 09:35:27 пользователь Michal Privoznik >>> написал: >>>>>> On

This is the core trace (gdb) bt #0 0xb7e5a231 in strcasecmp () from /lib/libc.so.6 #1 0xb7ce0a3f in local_ast_moh_start (chan=0x82496a8, mclass=0xb720f828 "default", interpclass=0x0) at res_musiconhold.c:646 #2 0x08083695 in ast_moh_start (chan=0x64, mclass=0x64 <Address 0x64 out of bounds>, interpclass=0x88 <Address 0x88 out of bounds>) at channel.c:4614 #3

В письме от Воскресенье, 30-июн-2013 03:41:37 пользователь Александр написал: > В письме от Вторник, 25-июн-2013 11:47:10 пользователь Michal Privoznik > > написал: > > On 24.06.2013 11:36, Александр wrote: > > > libvirtd will lock if for example kill programm which established > > > connection,> > > > > > > only sigkill + restart helps., to

This project provides a a pkg-config [.pc] file, pthread-stubs.pc, which provides the necessary flags for the given platform to link with the most lightweight implementation of the POSIX threads functions for that platform which is known to work with the XCB family of libraries. This release mainly affects the build & distribution process - the primary change to the installed contents is the

libvirtd will lock if for example kill programm which established connection, only sigkill + restart helps., to reproduce: virConnectPtr libvirt_connection = virConnectOpen("qemu:///system"); if(libvirt_connection == NULL) { std::cout<<"failed to connect to qemu:///system\n"; exit(-1); } exit(0);

I'm trying the following command on the source machine: virsh migrate --live --copy-storage-all --verbose TEST qemu+ssh:// 10.30.76.66/system If I ssh into the destination machine when this command is running, I can see NBD copying data as expected, and if I wait long enough it completes and succeeds. However if I ctrl+c this command above before it completes, it causes virsh commands

https://bugs.freedesktop.org/show_bug.cgi?id=98763 Bug ID: 98763 Summary: Lots of crashes of kontact /kmail5 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau Assignee: nouveau at

Hi, On 64 bit centos 5.6 I have virtualbox 4 and 64 bit elastix latest. Since yesterday cpu utilization has been constantly peaking 65-75%. Hardly 1-2 concurrent calls. No other activity on server. Top shows asterisk on top. Its quad xeon server with 4 gb ram. Any suggestion where should I start and how should I go about with my investigation. Thank you and have a great weekend. Sans

On 20.06.2013 10:44, Michal Privoznik wrote: > On 20.06.2013 09:40, Александр wrote: >> В письме от Четверг, 20-июн-2013 09:15:14 Вы написали: >>> On 19.06.2013 21:24, Александр wrote: >>>> В письме от Среда, 19-июн-2013 09:35:27 пользователь Michal Privoznik >> написал: >>>>> On 18.06.2013 22:21, Александр wrote: >>>>>> В письме

Hi Nick, On 9/20/2013 5:59 PM, Nick Kledzik wrote: > On Sep 20, 2013, at 3:42 PM, Shankar Easwaran > <shankare at codeaurora.org> wrote: >> nextFile could pass the current resolver state at the time when its called, the linkingcontext can return the next file to be processed as below :- >> >> nextFile(currentResolverState) :- >> >> a) Returns the next

i did the debugging as you said. Kindly refer the following logs: (gdb) c Continuing. thread apply all bt [New Thread 0x7fc337c6b700 (LWP 29520)] Program received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) thread apply all bt Thread 12 (Thread 0x7fc337c6b700 (LWP 29520)): #0 0x00007fc33509f18d in read () from /lib/x86_64-linux-gnu/libpthread.so.0 #1

Hello libvirt-users list, We're catching the same bug since 3.4.0 version (3.3.0 works OK). So, we have process that is permanently connected to libvirtd via socket and it is collecting stats, listening to events and control the VPSes. When we try to 'shutdown' a number of VPSes we often catch the bug. One of VPSes sticks in 'in shutdown' state, no related 'qemu'

В письме от Среда, 19-июн-2013 09:35:27 пользователь Michal Privoznik написал: > On 18.06.2013 22:21, Александр wrote: > > В письме от Вторник, 18-июн-2013 12:10:41 пользователь Michal Privoznik > > > > написал: > >> On 18.06.2013 07:14, Александр wrote: > >>> good day, i am trying to create domain via virDomainDefineXML. and my > >>> program

В письме от Четверг, 20-июн-2013 13:25:06 пользователь Michal Privoznik написал: > On 20.06.2013 12:56, Alexandr wrote: > > On 20.06.2013 10:44, Michal Privoznik wrote: > >> On 20.06.2013 09:40, Александр wrote: > >>> В письме от Четверг, 20-июн-2013 09:15:14 Вы написали: > >>>> On 19.06.2013 21:24, Александр wrote: > >>>>> В письме