search

RocketChat / Rocket.Chat.RaspberryPi

Run a private social network on your Pi for iPhone and Android devices !
MIT License
337 stars 59 forks source link

Snap daemon won't start #36

Closed bleucitron closed 4 years ago

bleucitron commented 5 years ago

Hello there !

After following the install instructions, with the latest version (November 2018) of Raspbian Stretch Lite on Raspberry Pi B+, i get stuck at sudo snap install rocketchat-server. The problem seems to be related to snapd that always fails to start, even after reboot.

pi@raspberrypi:/lib/systemd/system $ sudo systemctl status snapd
● snapd.service - Snappy daemon
   Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Thu 2018-12-27 16:02:28 CET; 7s ago
  Process: 2212 ExecStart=/usr/lib/snapd/snapd (code=killed, signal=SEGV)
 Main PID: 2212 (code=killed, signal=SEGV)

déc. 27 16:02:28 raspberrypi systemd[1]: snapd.service: Failed with result 'signal'.
déc. 27 16:02:28 raspberrypi systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
déc. 27 16:02:28 raspberrypi systemd[1]: Stopped Snappy daemon.
déc. 27 16:02:28 raspberrypi systemd[1]: snapd.service: Start request repeated too quickly.
déc. 27 16:02:28 raspberrypi systemd[1]: Failed to start Snappy daemon.
déc. 27 16:02:28 raspberrypi systemd[1]: snapd.service: Unit entered failed state.
déc. 27 16:02:28 raspberrypi systemd[1]: snapd.service: Failed with result 'signal'.

WIth a little investigation, it seems that at the end of snapd installation, something went wrong:

Job for snapd.autoimport.service failed because a fatal signal was delivered to the control process.
See "systemctl status snapd.autoimport.service" and "journalctl -xe" for details.
snapd.autoimport.service couldn't start.

systemctl status snapd.autoimport.service gives me:

pi@raspberrypi:~ $ systemctl status snapd.autoimport.service
● snapd.autoimport.service - Auto import assertions from block devices
   Loaded: loaded (/lib/systemd/system/snapd.autoimport.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Thu 2018-12-27 17:15:20 CET; 23s ago
  Process: 1389 ExecStart=/usr/bin/snap auto-import (code=killed, signal=ILL)
 Main PID: 1389 (code=killed, signal=ILL)

déc. 27 17:15:20 raspberrypi systemd[1]: Starting Auto import assertions from block devices...
déc. 27 17:15:20 raspberrypi /usr/bin/snap[1389]: cmd.go:105: DEBUG: restarting into "/snap/core/current/usr/bin/snap"
déc. 27 17:15:20 raspberrypi systemd[1]: snapd.autoimport.service: Main process exited, code=killed, status=4/ILL
déc. 27 17:15:20 raspberrypi systemd[1]: Failed to start Auto import assertions from block devices.
déc. 27 17:15:20 raspberrypi systemd[1]: snapd.autoimport.service: Unit entered failed state.
déc. 27 17:15:20 raspberrypi systemd[1]: snapd.autoimport.service: Failed with result 'signal'.

journalctl -xe gives me:

déc. 27 17:15:21 raspberrypi /usr/lib/snapd/snapd[1410]: cmd.go:105: DEBUG: restarting into "/snap/core/current/usr/li
déc. 27 17:15:21 raspberrypi systemd[1]: snapd.service: Main process exited, code=killed, status=11/SEGV
déc. 27 17:15:21 raspberrypi systemd[1]: snapd.service: Unit entered failed state.
déc. 27 17:15:21 raspberrypi systemd[1]: snapd.service: Failed with result 'signal'.
déc. 27 17:15:21 raspberrypi systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
déc. 27 17:15:21 raspberrypi systemd[1]: Stopped Snappy daemon.

Does anyone have an idea on how to solve this ?

Sing-Li commented 4 years ago

Early Raspbian did not always play nice with snapd.

Support for snapd on the current Raspbian Buster Lite (July 2019) is solid. Please re-image your SD and try Raspbian Buster Lite with snap install for the 1.0.x official release of Rocket.Chat for the smootest experience (2 GB Raspberry Pi 4 or larger recommended).