On Thu, 2017-01-26 at 16:51 +0000, Michael Vogt wrote: > Is this still a problem with the latest snapd? We use After=network- > online.target now which should ensure we do not run until we actually > have network. > > ** Changed in: snapd (Ubuntu) > Status: Confirmed => Incomplete > The last time I saw this was 10 Jan this year.
Jan 10 14:32:19 localhost systemd[1]: snapd.refresh.service: Main process exited, code=exited, status=1/FAILURE Jan 10 14:32:19 localhost systemd[1]: Failed to start Automatically refresh installed snaps. Jan 10 14:32:19 localhost systemd[1]: snapd.refresh.timer: Adding 28min 33.984038s random time. Jan 10 14:32:19 localhost systemd[1]: snapd.refresh.timer: Adding 5h 33min 46.386396s random time. Jan 10 14:32:19 localhost systemd[1]: snapd.refresh.service: Unit entered failed state. Jan 10 14:32:19 localhost systemd[1]: snapd.refresh.timer: Adding 1h 1min 47.737419s random time. Jan 10 14:32:19 localhost systemd[1]: snapd.refresh.timer: Adding 1h 27min 50.955932s random time. Jan 10 14:32:19 localhost systemd[1]: snapd.refresh.service: Failed with result 'exit-code'. -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 11:41:11 up 19:01, 1 user, load average: 0.66, 0.52, 0.36 Ubuntu 16.04.1 LTS, kernel 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592503 Title: "snapd.refresh.service" fails to start on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1592503/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
