Thanks Juston. I assume serviio shuts down cleanly while the network is still up?
It does seem to hang when it's already down, at shutdown. The order of events apparently is Jun 04 17:34:02 m51ac-x systemd[1]: Received SIGCHLD from PID 1918 (java). Jun 04 17:34:02 m51ac-x systemd[1]: Child 1918 (java) died (code=exited, status=1/FAILURE) Jun 04 17:34:02 m51ac-x systemd[1]: Child 1918 belongs to session-c1.scope Jun 04 17:34:02 m51ac-x systemd[1]: Stopping Network. Jun 04 17:34:02 m51ac-x NetworkManager[721]: <info> (eth0): link disconnected Jun 04 17:34:02 m51ac-x systemd[1]: Stopped Network Manager. Jun 04 17:35:32 m51ac-x systemd[1]: Received SIGCHLD from PID 1848 (java). Jun 04 17:35:32 m51ac-x systemd[1]: Child 1848 (java) died (code=killed, status=9/KILL) Jun 04 17:35:32 m51ac-x systemd[1]: Child 1848 belongs to session-c1.scope Jun 04 17:35:32 m51ac-x systemd[1]: session-c1.scope: cgroup is empty Jun 04 17:35:32 m51ac-x systemd[1]: session-c1.scope changed stop-sigkill -> failed i. e first the session gets terminated, NetworkManager stops (and with it the network), and eventually the hanging pid 1848 child gets killed as it doesn't terminate properly. I don't have an off-hand idea how to fix that (serviio shouldn't hang forever, but we don't have control about that). ** Changed in: systemd (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1456730 Title: Hangs on shutdown after installing and running serviio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
