[ovirt-devel] supervdsm defunct bug?

[Dan Kenigsberg]

On Fri, May 09, 2014 at 02:39:29PM +0000, Sven Kieske wrote:
> I don't see anything in supervdsm.log

Still, I believe that the bug is worth reopening - it's a process leak,
and it should be avoided. I believe that it can be easily solved by
adding zombiereaper to supervdsm.

> 
> just one error at all related to a vm network.
> 
> in vdsm log I got these timeouts repeatedly:
> 
> Thread-25::DEBUG::2014-05-02
> 09:02:43,652::fileSD::222::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
> iflag=direct
> if=/rhev/data-center/mnt/_home_DATA/9dc0fcb5-b0b0-47dd-b41f-d8709fd8cab2/dom_md/metadata
> bs=4096
> count=1' (cwd None)
> Thread-25::DEBUG::2014-05-02
> 09:02:43,667::fileSD::222::Storage.Misc.excCmd::(getReadDelay) SUCCESS:
> <err> = '0+1 records in\n0+1 records out\n495 bytes (495 B) copied,
> 0.000160501 s, 3.1 MB/s\n'; <rc> = 0
> VM Channels Listener::DEBUG::2014-05-02
> 09:02:43,940::vmChannels::91::vds::(_handle_timeouts) Timeout on fileno 65.
> VM Channels Listener::DEBUG::2014-05-02
> 09:02:45,384::vmChannels::91::vds::(_handle_timeouts) Timeout on fileno 106.

This is unrelated - that's Vdsm complaining about guest agents not
heart-beating. It's log noise that has very small value (particularly if
you never run guest agents). It should not appear repeatedly more than
once per guest.

Solving this isn't hard, but would never get priority without an
acclaimed user's BZ (hint hint).

Dan.