Quantcast
Channel: Squeezebox : Community : Forums - Logitech Media Server
Viewing all articles
Browse latest Browse all 5293

Multiple Processes and issues on Debian/Ubuntu

$
0
0
Hi

I have had major issues with LMS suddenly using 100% cpu (and beeing impossible to connect to) - using LMS 7.7.2 and 7.7.3.

I find it related to bad wifi-connection, as it happens very often when a player is "polling" the server due to loosing->regaining connection over and over again.

I have find the strange thing, that I have two processes running (I see this in Ubuntu, Debian and Raspbian (RaspberryPi) but not in CentoOS where I see only 1 process).

Code:

ps -aux |grep squeeze
gives me:

Code:

104      20455  0.0  0.1  5044  1416 ?        S    14:28  0:00 /bin/bash /usr/sbin/squeezeboxserver_safe /usr/sbin/squeezeboxserver --prefsdir /var/lib/squeezeb  oxserver/prefs --logdir /var/log/squeezeboxserver/ --cachedir /var/lib/squeezeboxserver/cache --charset=utf8
104      20467 22.4  6.0  76124 61928 ?        S    14:28  0:02 /usr/bin/perl /usr/sbin/squeezeboxserver --prefsdir /var/lib/squeezeboxserver/prefs --logdir /var  /log/squeezeboxserver/ --cachedir /var/lib/squeezeboxserver/cache --charset=utf8 --norestart

Thus indicating both PID 20455 and PID 20467.

One running squeezeboxserver_safe and the other squeezeboxserver with no _safe suffix.

Looking in /var/run/logitechmediaserver.pid gives me the 20455 PID.

Looking at 'top' - revealing that it is the 20467 process that is attributing to the actual CPU load - the 20455 process is never reaching the top list of CPU using processes.

If I stop, and restart the process I see this:
Code:

root@MediaServer ~# service logitechmediaserver stop
Stopping Logitech Media Server.
root@MediaServer ~# service logitechmediaserver start
Making sure that Logitech Media Server is not running first: start-stop-daemon: warning: failed to kill 20455: No such process
No process in pidfile '/var/run/logitechmediaserver.pid' found running; none killed.
Starting Logitech Media Server.

Indicating that there is something fishy with the way the startup script works.

I am seeing this deadlock with 100% quite often. Sometimes every day, sometimes it can be a week or so inbetween.
It does not matter if I am playing media - of or if all connecting players are just on standby.

In /var/log/squeezeboxserver/server.log I see something like this when it is in deadlock:

Code:

[13-11-28 09:07:00.4225] Slim::Networking::IO::Select::__ANON__ (147) Error: Select task failed calling Slim::Player::Source::__ANON__: illegal file descriptor or filehandle (either no attached file descriptor or illegal value):  at /usr/share/perl5/Slim/Networking/IO/Select.pm line 150.
; fh=Slim::Player::Protocols::HTTP=GLOB(0xeb0ef90)
[13-11-29 06:50:58.4085] Slim::Networking::IO::Select::__ANON__ (147) Error: Select task failed calling Slim::Player::Source::__ANON__: illegal file descriptor or filehandle (either no attached file descriptor or illegal value):  at /usr/share/perl5/Slim/Networking/IO/Select.pm line 150.
; fh=Slim::Player::Protocols::HTTP=GLOB(0xeef8a48)
[13-11-29 06:51:33.6482] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Web::Cometd::sendResponse failed: illegal file descriptor or filehandle (either no attached file descriptor or illegal value):  at /usr/share/perl5/Slim/Networking/IO/Select.pm line 150.
[13-11-29 06:52:28.4450] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Web::Cometd::sendResponse failed: illegal file descriptor or filehandle (either no attached file descriptor or illegal value):  at /usr/share/perl5/Slim/Networking/IO/Select.pm line 150.
[13-11-29 06:52:52.4317] Slim::Networking::IO::Select::__ANON__ (147) Error: Select task failed calling Slim::Web::HTTP::sendStreamingResponse: illegal file descriptor or filehandle (either no attached file descriptor or illegal value):  at /usr/share/perl5/Slim/Networking/IO/Select.pm line 150.
; fh=Slim::Web::HTTP::ClientConn=GLOB(0xf1f896c)
[13-11-29 06:53:06.9320] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Web::Cometd::sendResponse failed: illegal file descriptor or filehandle (either no attached file descriptor or illegal value):  at /usr/share/perl5/Slim/Networking/IO/Select.pm line 150.
[13-11-29 06:53:37.9926] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Web::Cometd::sendResponse failed: illegal file descriptor or filehandle (either no attached file descriptor or illegal value):  at /usr/share/perl5/Slim/Networking/IO/Select.pm line 150.
[13-11-29 06:54:22.5039] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Web::Cometd::sendResponse failed: illegal file descriptor or filehandle (either no attached file descriptor or illegal value):  at /usr/share/perl5/Slim/Networking/IO/Select.pm line 150.
[13-11-29 06:54:56.0245] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Web::Cometd::sendResponse failed: illegal file descriptor or filehandle (either no attached file descriptor or illegal value):  at /usr/share/perl5/Slim/Networking/IO/Select.pm line 150.
[13-11-29 06:55:19.3061] Slim::Networking::IO::Select::__ANON__ (147) Error: Select task failed calling Slim::Player::Source::__ANON__: illegal file descriptor or filehandle (either no attached file descriptor or illegal value):  at /usr/share/perl5/Slim/Networking/IO/Select.pm line 150.
; fh=Slim::Player::Protocols::HTTP=GLOB(0xdc513dc)

Have anyone seen something simular?

We are having so many issues with this, that the wife could and up demanding a switch (downgrade IMO) to Sonos instead.

BR
macsat

Viewing all articles
Browse latest Browse all 5293

Trending Articles