> -----Original Message-----> From:atomic-devel-boun...@projectatomic.io
[mailto:atomic-devel-> boun...@projectatomic.io]On Behalf Of Colin Walters>
Sent:Sunday, March 24, 2019 2:28 AM> To:atomic-devel@projectatomic.io>
Subject:Re: [atomic-devel] Rebase Fedora Atomic 27 > 29 fails to boot> > > > On
Wed, Mar20, 2019, at 11:41 AM, Doug Campbell wrote:> >Currently running Fedora
Atomic 27.153> >> >Following instructions at:> >
http://www.projectatomic.io/blog/2018/10/fedora-atomic-28-to-29-> upgrade/ to
upgrade to version 29.> >> > Uponreboot everything is fine until I see:> >> >
(1 of2) A start job is running for Network Manager (3min 6s / 1min 36s)>
>[timestmp] systemd-journal[990]: Failed to send WATCHDOG=1 notification>
>message: Connection refused> >[timestmp] systemd-journal[990]: Failed to send
WATCHDOG=1 notification> >message: Transport endpoint is not connected> >> >
Thelast line continues to repeat periodically for as long as I would wait.> >
Try sendingthe systemd journal to the console:>
https://freedesktop.org/wiki/Software/systemd/Debugging/> Specificallyyou want
to add to the kernel commandline:> >
systemd.journald.forward_to_console=1console=ttyS0,38400 console=tty1> > If
you'reusing the default GRUB setup just press `e` at the prompt.> > If this isa
physical box that's hard to change remotely, one thing I'd recommend> is to
trysetting up a similar system in a VM (using the same config management> etc.)
andsee if it reproduces there too. VMs area lot easier to debug. Thanks for
the suggestions. I unfortunately am dealing witha remote server and although I
tried I cannot seem to duplicate the issuelocally on a virtual machine. After
switching back to version27 I was able to look at the logs though and one thing
that appearedinteresting was the following lines: 23:11 <error>
[1553094660.3061] dispatcher:could not get dispatcher proxy! Error calling
StartServiceByName fororg.freedesktop.nm_dispatcher: Timeout wa...
NetworkManager23:04 Process 1237 (systemd) of user 0 dumped core.Stack trace
of thread 1237: #00x00007fc8537cd83b kill (libc.so.6) #1 0x00005575ce842eda
n/a (systemd)... systemd-coredump23:04 Freezing execution
systemd23:04 Caught <ABRT>, dumped core as pid 1237
systemd23:04 Assertion 'slot->n_ref > 0' failed
at../src/libsystemd/sd-bus/bus-slot.c:198, function
sd_bus_slot_unref().Aborting.
systemd23:04 Failed to get initial list of names:
Connection timed out
systemd23:02 Assertion
'slot->n_ref > 0' failed at../src/libsystemd/sd-bus/bus-slot.c:198, function
sd_bus_slot_unref().Aborting.
systemd-login Not sure what that meansexactly but I
suspect the problem may lie in there. Doug
