Yes, from my experiments, it gets stuck at some point where it has to start avahi. And it fails to start it because it is dependent on something that is not started yet (which is started when sssd is started). Googling for that error pointed took me to http://www.calculate-linux.org/boards/15/topics/26673, which seems to be somewhat related I think. I'll post the journal messages soon. Is there some sort of a systemd diff utility which can compare the start sequence of services from two different systems ? Since my replica is on 7.2, which afaik works fine, doing a diff between the two might highlight if something has changed in the start sequence.
On Thu, Nov 10, 2016 at 12:35 PM, Petr Vobornik <pvobo...@redhat.com> wrote: > On 11/09/2016 12:53 PM, Prasun Gera wrote: > > It looks like something is messed up in the systemd configuration after > 7.3. My > > system doesn't boot at all. The boot screen would display the message: > "Failed > > to register match for Disconnected message: Connection timed out". After > some > > trial and error, I've managed to boot it. Here's what works right now: > 1) Boot > > into system rescue target with debug shell 2) start sssd 3) isolate > graphical.target > > > > I have a replica which I haven't upgraded to 7.3 yet. So I can compare > the two > > systems to isolate the problem. > > > > I'm afraid that without more info(messages/journal) nobody will be able > to help. > > But based on the description it seems that it didn't even get to step > where IPA is started. > > -- > Petr Vobornik >
-- Manage your subscription for the Freeipa-users mailing list: https://www.redhat.com/mailman/listinfo/freeipa-users Go to http://freeipa.org for more info on the project