[Bug 1632363] Re: snapd fail on boot
[Expired for snapd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: snapd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632363] Re: snapd fail on boot
** Changed in: snapd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632363] Re: snapd fail on boot
Here is the error: Oct 27 14:00:50 localhost.localdomain snapd[1855]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int It would be great if you could upload your /var/lib/snapd/state.json so that we can inspect it. If you do that and you have used "snap login" before, please make the bug private as the state.json file contains a "macaroon" security token. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632363] Re: snapd fail on boot
`journalctl -u snapd.service` -- Logs begin at Thu 2016-10-27 13:49:19 UTC, end at Thu 2016-10-27 14:00:54 UTC. -- Oct 27 14:00:45 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:47 localhost.localdomain snapd[1823]: error: internal error: could not unmarshal state entr Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, statu Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:48 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:48 localhost.localdomain snapd[1833]: error: internal error: could not unmarshal state entr Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, statu Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:48 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:48 localhost.localdomain snapd[1840]: error: internal error: could not unmarshal state entr Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, statu Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:49 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:49 localhost.localdomain snapd[1848]: error: internal error: could not unmarshal state entr Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, statu Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:49 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:50 localhost.localdomain snapd[1855]: error: internal error: could not unmarshal state entr Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, statu Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Start request repeated too quickly. Oct 27 14:00:50 localhost.localdomain systemd[1]: Failed to start Snappy daemon. `journalctl -u snapd.boot-ok.service` -- Logs begin at Thu 2016-10-27 13:49:19 UTC, end at Thu 2016-10-27 14:00:54 UTC. -- Oct 27 14:00:53 localhost.localdomain systemd[1]: Starting Notify bootloader that boot was successful... Oct 27 14:00:54 localhost.localdomain snap[1874]: error: can not SyncBoot, failed to make ubuntu-core active: snap not active Oct 27 14:00:54 localhost.localdomain systemd[1]: snapd.boot-ok.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:54 localhost.localdomain systemd[1]: Failed to start Notify bootloader that boot was successful. Oct 27 14:00:54 localhost.localdomain systemd[1]: snapd.boot-ok.service: Unit entered failed state. Oct 27 14:00:54 localhost.localdomain systemd[1]: snapd.boot-ok.service: Failed with result 'exit-code'. `journalctl -u snapd.socket` -- Logs begin at Thu 2016-10-27 13:49:19 UTC, end at Thu 2016-10-27 14:00:54 UTC. -- Oct 27 13:49:40 localhost.localdomain systemd[1]: Starting Socket activation for snappy daemon. Oct 27 13:49:40 localhost.localdomain systemd[1]: Listening on Socket activation for snappy daemon. Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.socket: Unit entered failed state. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632363] Re: snapd fail on boot
-- Logs begin at Thu 2016-10-27 13:49:19 UTC, end at Thu 2016-10-27 14:13:13 UTC. -- Oct 27 14:00:45 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:47 localhost.localdomain snapd[1823]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:48 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:48 localhost.localdomain snapd[1833]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:48 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:48 localhost.localdomain snapd[1840]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:49 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:49 localhost.localdomain snapd[1848]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:49 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:50 localhost.localdomain snapd[1855]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Start request repeated too quickly. Oct 27 14:00:50 localhost.localdomain systemd[1]: Failed to start Snappy daemon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632363] Re: snapd fail on boot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632363] Re: snapd fail on boot
The image was working fine, and although the sheer amount of experimentation and reinstalls makes my memory foggy, I do believe this particular install had gone through a ubuntu-core update without any issues. What caused the issue in the first place is a real networking issue. I had placed the install within a DMZ that was wrongly configured, so the clients of the subnet was unable to get a lease on an IP-address. It was left on this subnet for quite some time and over several boots. It now has internet access again, but the snap daemon fails continuously. For what reason I'm unsure. I've seen different reports of snap daemon failing because it starts before networking in the boot process, maybe I'm suffering the same problem. This bug then, would have surfaced due to a longer period of no network access for unknown reasons. @Michael I'm unfamiliar with journalctl and have yet to manage to get any form of relevant info from a query. Maybe you could help me with some suggestions as to what to search for in the journal? @Oliver The image is from https://people.canonical.com/~mvo/all-snaps/obsolete/, it was downloaded on the 19th of September. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632363] Re: snapd fail on boot
where exactly did you get this image from and when ? note that the bbb images are still rather experimental, there were issues in early ones where the clock was set wrong which causes snapd to be unhappy, but this was fixed in a later iteration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632363] Re: snapd fail on boot
Are there messages in the journal too? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
