You are not logged in.

#1 2015-10-23 15:38:19

delta575
Member
Registered: 2015-10-23
Posts: 5

Daemons failing after pacman -Syu

Hi

I've been using arch as a media server for a while, (kodi, emby, sonarr, couchpotato, etc.)
I don't know much about linux but I've managed some basics
Recently this year I've been having this issue... sometimes when I upgrade packages (pacman -Syu or yaourt -Syu) some of these daemons fails to start and I cant get them right... I end up reinstalling the whole OS instead

I became bored of doing that so I'm asking for your help, just let me know what you need to help me.

I've tried reinstalling disabling reenabling.. deleting all files related, etc.

Thanks in advance and sorry for my bad english.

Offline

#2 2015-10-23 16:44:32

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,604

Re: Daemons failing after pacman -Syu

Need logs

Offline

#3 2015-10-23 23:47:02

delta575
Member
Registered: 2015-10-23
Posts: 5

Re: Daemons failing after pacman -Syu

 systemctl --failed
  UNIT                LOAD   ACTIVE SUB    DESCRIPTION
● couchpotato.service loaded failed failed An automatic NZB and torrent movie downloader
● emby-server.service loaded failed failed Emby brings together your videos, music, photos, and live television.
● sonarr.service      loaded failed failed Sonarr Service 

(also kodi-standalone-service is installed and enabled.. it isn't listed here but it doesn't start... and sabnzbd seems to have issues)

systemctl status couchpotato
● couchpotato.service - An automatic NZB and torrent movie downloader
   Loaded: loaded (/usr/lib/systemd/system/couchpotato.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2015-10-23 20:39:44 CLT; 4min 47s ago
  Process: 464 ExecStart=/usr/bin/couchpotato --config_file $CP_CONF --data_dir $CP_DATA --pid_file=/run/couchpotato/couchpotato.pid --console_log (code=exited, status=1/FAILURE)
 Main PID: 464 (code=exited, status=1/FAILURE)

Oct 23 20:39:44 DeltaServer couchpotato[464]: File "/usr/lib/python2.7/tarfile.py", line 2045, in addfile
Oct 23 20:39:44 DeltaServer couchpotato[464]: copyfileobj(fileobj, self.fileobj, tarinfo.size)
Oct 23 20:39:44 DeltaServer couchpotato[464]: File "/usr/lib/python2.7/tarfile.py", line 275, in copyfileobj
Oct 23 20:39:44 DeltaServer couchpotato[464]: dst.write(buf)
Oct 23 20:39:44 DeltaServer couchpotato[464]: File "/usr/lib/python2.7/gzip.py", line 241, in write
Oct 23 20:39:44 DeltaServer couchpotato[464]: self.fileobj.write(self.compress.compress(data))
Oct 23 20:39:44 DeltaServer couchpotato[464]: IOError: [Errno 28] No space left on device
Oct 23 20:39:44 DeltaServer systemd[1]: couchpotato.service: Main process exited, code=exited, status=1/FAILURE
Oct 23 20:39:44 DeltaServer systemd[1]: couchpotato.service: Unit entered failed state.
Oct 23 20:39:44 DeltaServer systemd[1]: couchpotato.service: Failed with result 'exit-code'. 
systemctl status kodi
● kodi.service - Starts instance of Kodi using xinit
   Loaded: loaded (/usr/lib/systemd/system/kodi.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Fri 2015-10-23 20:39:46 CLT; 5min ago
  Process: 456 ExecStart=/usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7 (code=exited, status=0/SUCCESS)
 Main PID: 456 (code=exited, status=0/SUCCESS)

Oct 23 20:39:43 DeltaServer systemd[1]: Started Starts instance of Kodi using xinit.
Oct 23 20:39:43 DeltaServer systemd[456]: pam_unix(login:session): session opened for user kodi by (uid=0) 
systemctl status emby-server
● emby-server.service - Emby brings together your videos, music, photos, and live television.
   Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Fri 2015-10-23 20:39:49 CLT; 5min ago
  Process: 617 ExecStart=/usr/bin/emby-server (code=exited, status=0/SUCCESS)
 Main PID: 617 (code=exited, status=0/SUCCESS)

Oct 23 20:39:49 DeltaServer systemd[1]: emby-server.service: Service hold-off time over, scheduling restart.
Oct 23 20:39:49 DeltaServer systemd[1]: Stopped Emby brings together your videos, music, photos, and live television..
Oct 23 20:39:49 DeltaServer systemd[1]: emby-server.service: Start request repeated too quickly.
Oct 23 20:39:49 DeltaServer systemd[1]: Failed to start Emby brings together your videos, music, photos, and live television..
Oct 23 20:39:49 DeltaServer systemd[1]: emby-server.service: Unit entered failed state.
Oct 23 20:39:49 DeltaServer systemd[1]: emby-server.service: Failed with result 'start-limit'. 
 sonarr.service - Sonarr Service
   Loaded: loaded (/usr/lib/systemd/system/sonarr.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2015-10-23 20:39:44 CLT; 6min ago
  Process: 460 ExecStart=/usr/bin/sonarr -nobrowser -data=/var/lib/sonarr (code=exited, status=1/FAILURE)
 Main PID: 460 (code=exited, status=1/FAILURE)

Oct 23 20:39:44 DeltaServer sonarr[460]: [Info] AppFolderInfo: Data directory is being overridden to [/var/lib/sonarr]
Oct 23 20:39:44 DeltaServer sonarr[460]: [Error] PidFileProvider: Unable to write PID file: /var/lib/sonarr/nzbdrone.pid
Oct 23 20:39:44 DeltaServer sonarr[460]: [Fatal] ConsoleApp: EPIC FAIL!
Oct 23 20:39:44 DeltaServer sonarr[460]: System.IO.IOException: Disk full. Path /var/lib/sonarr/nzbdrone.pid
Oct 23 20:39:44 DeltaServer sonarr[460]: at System.IO.FileStream.FlushBuffer () [0x00000] in <filename unknown>:0
Oct 23 20:39:44 DeltaServer sonarr[460]: at System.IO.FileStream.Dispose (Boolean disposing) [0x00000] in <filename unknown>:0
Oct 23 20:39:44 DeltaServer sonarr[460]: Press any key to exit...
Oct 23 20:39:44 DeltaServer systemd[1]: sonarr.service: Main process exited, code=exited, status=1/FAILURE
Oct 23 20:39:44 DeltaServer systemd[1]: sonarr.service: Unit entered failed state.
Oct 23 20:39:44 DeltaServer systemd[1]: sonarr.service: Failed with result 'exit-code'. 
sabnzbd.service - SABnzbd binary newsreader
   Loaded: loaded (/usr/lib/systemd/system/sabnzbd.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2015-10-23 20:39:43 CLT; 6min ago
 Main PID: 463 (SABnzbd.py)
   CGroup: /system.slice/sabnzbd.service
           └─463 /usr/bin/python2 -OO /opt/sabnzbd/SABnzbd.py -l0

Oct 23 20:40:50 DeltaServer SABnzbd.py[463]: 2015-10-23 20:40:50,854::ERROR::[config:791] Cannot write to INI file /opt/sabnzbd/sabnzbd.ini
Oct 23 20:41:23 DeltaServer SABnzbd.py[463]: 2015-10-23 20:41:23,878::ERROR::[config:791] Cannot write to INI file /opt/sabnzbd/sabnzbd.ini
Oct 23 20:41:56 DeltaServer SABnzbd.py[463]: 2015-10-23 20:41:56,907::ERROR::[config:791] Cannot write to INI file /opt/sabnzbd/sabnzbd.ini
Oct 23 20:42:29 DeltaServer SABnzbd.py[463]: 2015-10-23 20:42:29,944::ERROR::[config:791] Cannot write to INI file /opt/sabnzbd/sabnzbd.ini
Oct 23 20:43:02 DeltaServer SABnzbd.py[463]: 2015-10-23 20:43:02,968::ERROR::[config:791] Cannot write to INI file /opt/sabnzbd/sabnzbd.ini
Oct 23 20:43:36 DeltaServer SABnzbd.py[463]: 2015-10-23 20:43:36,007::ERROR::[config:791] Cannot write to INI file /opt/sabnzbd/sabnzbd.ini
Oct 23 20:44:09 DeltaServer SABnzbd.py[463]: 2015-10-23 20:44:09,043::ERROR::[config:791] Cannot write to INI file /opt/sabnzbd/sabnzbd.ini
Oct 23 20:44:42 DeltaServer SABnzbd.py[463]: 2015-10-23 20:44:42,074::ERROR::[config:791] Cannot write to INI file /opt/sabnzbd/sabnzbd.ini
Oct 23 20:45:15 DeltaServer SABnzbd.py[463]: 2015-10-23 20:45:15,099::ERROR::[config:791] Cannot write to INI file /opt/sabnzbd/sabnzbd.ini
Oct 23 20:45:48 DeltaServer SABnzbd.py[463]: 2015-10-23 20:45:48,125::ERROR::[config:791] Cannot write to INI file /opt/sabnzbd/sabnzbd.ini 

Last edited by delta575 (2015-10-24 00:36:37)

Offline

#4 2015-10-23 23:48:40

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: Daemons failing after pacman -Syu

Please use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Fo … s_and_code

logs wrote:
Oct 23 20:39:44 DeltaServer sonarr[460]: [Fatal] ConsoleApp: EPIC FAIL!
Oct 23 20:39:44 DeltaServer sonarr[460]: System.IO.IOException: Disk full. Path /var/lib/sonarr/nzbdrone.pid

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#5 2015-10-23 23:48:59

Banton
Member
Registered: 2010-05-28
Posts: 67

Re: Daemons failing after pacman -Syu

looks like your disk is full

Offline

#6 2015-10-24 00:38:35

delta575
Member
Registered: 2015-10-23
Posts: 5

Re: Daemons failing after pacman -Syu

Banton wrote:

looks like your disk is full

that seemed to do the trick! Thanks!

pacman -Sc released some space but I'll have to work it some more


I'm using a small 60gb SSD for arch... the partition that's full is 7.1gb (sda4 created automatically during install)... is there a way I could expand it?

[delta@DeltaServer ~]$ sudo df -h
Filesystem         Size  Used Avail Use% Mounted on
dev                3.4G     0  3.4G   0% /dev
run                3.4G  648K  3.4G   1% /run
/dev/sda4          7.1G  6.3G  443M  94% /
tmpfs              3.4G   16K  3.4G   1% /dev/shm
tmpfs              3.4G     0  3.4G   0% /sys/fs/cgroup
tmpfs              4.0G  4.0K  4.0G   1% /tmp
/mnt/5Tb;/mnt/4Tb  8.2T  5.0T  3.3T  60% /mnt/storage
/dev/sda5           51G   53M   48G   1% /home
/dev/sdc1          4.6T  2.2T  2.4T  49% /mnt/5Tb
/dev/sdb1          3.7T  2.8T  952G  75% /mnt/4Tb
tmpfs              692M     0  692M   0% /run/user/420
tmpfs              692M     0  692M   0% /run/user/1000

Last edited by delta575 (2015-10-24 00:44:06)

Offline

#7 2015-10-24 05:00:52

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: Daemons failing after pacman -Syu

I see that sda5 which is mounted on /home is almost empty. You can probably move home's data somewhere else. Delete that partition and expand your root. Gparted should do the job. But be sure to backup everything, just in case.

Offline

#8 2015-10-24 15:34:10

delta575
Member
Registered: 2015-10-23
Posts: 5

Re: Daemons failing after pacman -Syu

x33a wrote:

I see that sda5 which is mounted on /home is almost empty. You can probably move home's data somewhere else. Delete that partition and expand your root. Gparted should do the job. But be sure to backup everything, just in case.

Done!, was really easy, thanks guys!

Offline

#9 2015-10-24 16:15:37

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,902
Website

Re: Daemons failing after pacman -Syu

delta575 wrote:

the partition that's full is 7.1gb (sda4 created automatically during install)...

How did you install? There is no automatic partition creation during a proper Arch Linux install..


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#10 2015-10-25 15:52:16

delta575
Member
Registered: 2015-10-23
Posts: 5

Re: Daemons failing after pacman -Syu

WorMzy wrote:
delta575 wrote:

the partition that's full is 7.1gb (sda4 created automatically during install)...

How did you install? There is no automatic partition creation during a proper Arch Linux install..


Archboot-network ISO does

Offline

Board footer

Powered by FluxBB