[libvirt] debugging daemon-conf failure
Jim Meyering
jim at meyering.net
Fri Feb 26 18:44:29 UTC 2010
Eric Blake wrote:
> Ever since I first started playing with libvirt last month, 'make check'
> has been failing for me on the same test:
>
> $ VIR_TEST_DEBUG=2 make -C tests check TESTS=daemon-conf
> ...
> 1) corrupted config listen_tls ... OK
> 2) corrupted config listen_tcp ... OK
> 3) corrupted config tls_port ... OK
> 4) corrupted config tcp_port ... OK
> 5) corrupted config listen_addr ... OK
> 6) corrupted config mdns_adv ... FAILED
> 7) corrupted config mdns_name ... FAILED
> 8) corrupted config unix_sock_group ... FAILED
> 9) corrupted config unix_sock_ro_perms ... FAILED
> 10) corrupted config unix_sock_rw_perms ... FAILED
> 11) corrupted config unix_sock_dir ... FAILED
> 12) corrupted config auth_unix_ro ... OK
> 13) corrupted config auth_unix_rw ... OK
> 14) corrupted config auth_tcp ... OK
> 15) corrupted config auth_tls ... FAILED
> 16) corrupted config key_file ... FAILED
> 17) corrupted config cert_file ... FAILED
> 18) corrupted config ca_file ... FAILED
> 19) corrupted config crl_file ... FAILED
> 20) corrupted config tls_no_verify_certificate ... FAILED
> 21) corrupted config tls_allowed_dn_list ... FAILED
> 22) corrupted config sasl_allowed_username_list ... FAILED
> 23) corrupted config max_clients ... FAILED
> 24) corrupted config min_workers ... FAILED
> 25) corrupted config max_workers ... FAILED
> 26) corrupted config max_requests ... FAILED
> 27) corrupted config max_client_requests ... FAILED
> ./daemon-conf: line 81: kill: (3145) - No such process
> 28) valid config file (sleeping 2 seconds) ... FAILED
> FAIL: daemon-conf
> ==================
> 1 of 1 test failed
> ==================
>
> Any hints on what I should do to help find the root cause for the
> failure? Am I missing a package? Does the test need to be made
> more robust to skip if a prereq is missing?
What type of system are you using?
Parts of that test are a little obscure-looking (you can probably blame
me for that). It starts with the sample config file and iterates
through it corrupting one line at a time. If running libvirtd with
each resulting corrupted config file does not yield the expected result,
its a failure.
A good place to start would be to save one of the failing config
files and to invoke libvirtd manually to see exactly what it's
printing and thus get a hint as to why the expected diagnostic is missing.
More information about the libvir-list
mailing list