* Carlos E. R. <robin.listas@telefonica.net> [01-02-23 15:58]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday, 2023-01-02 at 15:43 -0500, Patrick Shanahan wrote:
* Carlos E. R. <> [01-02-23 15:06]:
On 2023-01-02 20:09, Patrick Shanahan wrote:
* Simon Becherer <> [01-02-23 13:39]:
Hi andrei,
thanks for answering:
Am 01.01.23 um 09:47 schrieb Andrei Borzenkov:
I cannot reproduce it on VM with wicked. You may want to enable debug output to see what's going on.
could you please provide the comandline to get debug output i sould use?
thanks,
wicked --help
And where exactly is that wicked call produced, so that he can write whatever option is needed? Saying to read the help doesn't help.
it is that difficult to execute the command and look for a debug instance?
Yes, it is, because it runs automatically "somewhere" during boot. You have to explain how to modify the boot process so to insert that debugging option(s).
- -- Cheers, Carlos E. R. (from openSUSE 15.4 x86_64 at Telcontar)
-----BEGIN PGP SIGNATURE-----
iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCY7NFGhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVlMMAniq23lfgUHBbUrS21uiD e8SeR/9eAJ99MNv73CR74qAoxlKoSy+4gUk4bQ== =el0r -----END PGP SIGNATURE-----
ok, halt the current instance and restart with wicked --debug all not knowing where the particular problem is, "--debug all" rather than the more narrow options. if the problem is on boot, disable wicked, reboot, then start wicked as above. it's not really rocket science, more like basic plumbing. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc