I've found a possible workaround, when running landscape-config fails, which should at least provide more insight into what is failing, if there are no logs.
Starting in a state where there are no landscape-client processes running, run the broker directly:
I've found a possible workaround, when running landscape-config fails, which should at least provide more insight into what is failing, if there are no logs.
Starting in a state where there are no landscape-client processes running, run the broker directly:
sudo -u landscape /usr/bin/python3 /usr/bin/ landscape- broker
If that fails, run the main landscape-client process (as root):
sudo /usr/bin/python3 /usr/bin/ landscape- client
If things seem to go okay, you can retry running landscape-config.
Unfortunately I've as of yet been unable to reproduce this one.