Displaying 6 results from an estimated 6 matches for "kharchenko".
2009 May 09
2
a general way to select a subset of matrix rows?
Dear fellow R users,
I can't figure out how to do a simple thing properly: apply an operation
to matrix columns on a selected subset of rows. Things go wrong when
only one row is being selected. I am sure there's a way to do this
properly.
Here's an example:
# define a 3-by-4 matrix x
> x <- matrix(runif(12),ncol=4)
> str(x)
num [1:3, 1:4] 0.568 0.217 0.309 0.859
2018 Jan 18
3
Re: Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
On 01/18/2018 08:25 AM, Ján Tomko wrote:
> On Wed, Jan 17, 2018 at 04:45:38PM +0200, Serhii Kharchenko wrote:
>> 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.
>>...
2018 Jan 17
4
Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
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'
2018 Jan 17
0
Re: Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
On 01/17/2018 03:45 PM, Serhii Kharchenko wrote:
> 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...
2018 Jan 18
0
Re: Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
On Wed, Jan 17, 2018 at 04:45:38PM +0200, Serhii Kharchenko wrote:
>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 'sh...
2018 Jan 17
1
Re: Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
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