Search found 3 matches
- July 29th, 2017, 4:45 pm
- Forum: Debian/Ubuntu Package
- Topic: Unable to start as a service suddenly [Raspi]
- Replies: 4
- Views: 3733
Re: Unable to start as a service suddenly [Raspi]
Thanks but I don't think it's an upgrade of SABnzbd plus that has caused it, more likely I think the OSMC auto updated has updated a library that sab uses which is where the segmentation fault would be occurring. I can't see any likely candidates though! Might be time for a full reinstall.
- July 29th, 2017, 12:04 am
- Forum: Debian/Ubuntu Package
- Topic: Unable to start as a service suddenly [Raspi]
- Replies: 4
- Views: 3733
Re: Unable to start as a service suddenly [Raspi]
It's OSMC which is Debian Jessie with a skinned version of kodi on top: osmc@osmclounge:~$ lsb_release -da No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.9 (jessie) Release: 8.9 Codename: jessie Installation was through the ppa nobetas repo using apt-get (I had ...
- July 27th, 2017, 8:38 pm
- Forum: Debian/Ubuntu Package
- Topic: Unable to start as a service suddenly [Raspi]
- Replies: 4
- Views: 3733
Unable to start as a service suddenly [Raspi]
Had sab installed on osmc on a Rasp Pi for ages... Suddenly failing to start as a service. journalctl tells me it's a segmentation fault: -- Unit sabnzbdplus.service has begun starting up. Jul 28 13:29:49 osmclounge sabnzbdplus[28783]: Segmentation fault Jul 28 13:29:49 osmclounge systemd[1]: sabnzb...