Project

General

Profile

Bug #1569

Plex Media Server Stopped, won't start

Added by jaredmalik almost 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Apps
Target version:
-
Start date:
11/01/2014
Due date:
% Done:

0%


Description

I had the plex amahi app running great for about a month. Last night 10/31 I went to the web gui and it didn't load, looking at the settings/server page shows all servers up except for plex. When I start plex from there it immediately stops. I included the output from rpm -ql amahi-plex command in a text file.

I also updated my config file to no longer update plex today, let me know if I need to turn that back on for troubleshooting. Thanks!

[root@localhost ~]# systemctl start amahi-plex
[root@localhost ~]# systemctl status amahi-plex
amahi-plex.service - Plex Media Server for Amahi
Loaded: loaded (/usr/lib/systemd/system/amahi-plex.service; enabled)
Active: failed (Result: exit-code) since Sat 2014-11-01 10:54:38 MDT; 11s ago
Process: 3393 ExecStopPost=/bin/rm -f /run/amahi-plex.pid (code=exited, status=0/SUCCESS)
Process: 3391 ExecStop=/usr/bin/kill $MAINPID (code=exited, status=1/FAILURE)
Process: 3387 ExecStart=/usr/bin/amahi-plex (code=exited, status=0/SUCCESS)
Main PID: 3389 (code=exited, status=132)
CGroup: name=systemd:/system/amahi-plex.service

Nov 01 10:54:38 localhost.localdomain systemd[1]: Starting Plex Media Server for Amahi...
Nov 01 10:54:38 localhost.localdomain systemd[1]: Started Plex Media Server for Amahi.
Nov 01 10:54:38 localhost.localdomain runuser[3389]: pam_unix(runuser:session): session opened for user apache by (uid=0)
Nov 01 10:54:38 localhost.localdomain systemd[1]: amahi-plex.service: main process exited, code=exited, status=132/n/a
Nov 01 10:54:38 localhost.localdomain systemd[1]: amahi-plex.service: control process exited, code=exited status=1
Nov 01 10:54:38 localhost.localdomain systemd[1]: Unit amahi-plex.service entered failed state.
[root@localhost ~]#

History

#1 Updated by cpg almost 7 years ago

  • File deleted (Plex.txt)

#2 Updated by cpg almost 7 years ago

  • Description updated (diff)

please share the output of: rpm -q amahi-plex

and after that, possibly (as root): systemctl restart amahi-plex

there was an automatic update of the plex server the day before yesterday. however, we did test this scenario of updating a running system before release and it worked, so we're curious why this stopped working!

#3 Updated by jaredmalik almost 7 years ago

Here is the output from rpm -q amahi-plex

amahi-plex-0.4-1.x86_64

I did the other command, plex server still won't stay up. Thanks for the reply!

#4 Updated by cpg almost 7 years ago

ok, you are updated at the latest plex.
however, a status error of 132 does not say much.

can you look for log files in plex, like in

 /var/log/*plex*

or similar?

we need to find the reason why it has an error starting.

#5 Updated by jaredmalik almost 7 years ago

Ok found one:

[root@localhost logs]# more error_log
[Sat Nov 01 10:26:12.336710 2014] [proxy:error] [pid 1506] (111)Connection refused: AH00957: HTTP: attempt to conn
ect to 127.0.0.1:32400 (localhost) failed
[Sat Nov 01 10:26:12.336842 2014] [proxy:error] [pid 1506] AH00959: ap_proxy_connect_backend disabling worker for
(localhost) for 60s
[Sat Nov 01 10:26:12.336865 2014] [proxy_http:error] [pid 1506] [client 192.168.0.101:53678] AH01114: HTTP: failed
 to make connection to backend: localhost, referer: http://hda/tab/apps
[Sat Nov 01 10:26:12.416439 2014] [proxy:error] [pid 1507] (111)Connection refused: AH00957: HTTP: attempt to conn
ect to 127.0.0.1:32400 (localhost) failed
[Sat Nov 01 10:26:12.416540 2014] [proxy:error] [pid 1507] AH00959: ap_proxy_connect_backend disabling worker for
(localhost) for 60s
[Sat Nov 01 10:26:12.416560 2014] [proxy_http:error] [pid 1507] [client 192.168.0.101:53679] AH01114: HTTP: failed
 to make connection to backend: localhost
[Sat Nov 01 10:27:45.751264 2014] [proxy:error] [pid 1507] (111)Connection refused: AH00957: HTTP: attempt to conn
ect to 127.0.0.1:32400 (localhost) failed
[Sat Nov 01 10:27:45.751396 2014] [proxy:error] [pid 1507] AH00959: ap_proxy_connect_backend disabling worker for
(localhost) for 60s
[Sat Nov 01 10:27:45.751413 2014] [proxy_http:error] [pid 1507] [client 192.168.0.101:53708] AH01114: HTTP: failed
 to make connection to backend: localhost, referer: http://hda/tab/apps
[Sat Nov 01 10:27:45.814752 2014] [proxy:error] [pid 1508] (111)Connection refused: AH00957: HTTP: attempt to conn
ect to 127.0.0.1:32400 (localhost) failed
[Sat Nov 01 10:27:45.814846 2014] [proxy:error] [pid 1508] AH00959: ap_proxy_connect_backend disabling worker for
(localhost) for 60s
[Sat Nov 01 10:27:45.814866 2014] [proxy_http:error] [pid 1508] [client 192.168.0.101:53709] AH01114: HTTP: failed
 to make connection to backend: localhost

#6 Updated by cpg almost 7 years ago

this is the web front end not being able the connect to the plex server.

we knew the plex server was not running, hence this is not a surprise.

what we do not know is why it does not seem to get started.

#7 Updated by jaredmalik almost 7 years ago

Any ideas to find another log? I looks in the var/hda/app folder nothing in there.

#8 Updated by jaredmalik almost 7 years ago

Nothing related seems to be in /var/log.

#9 Updated by cpg almost 7 years ago

hi, i sent email about solving his via remote access and irc, however, i am not sure you saw it.

in any case, the log files may be in this location:

/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs/

(i cannot check locally at the moment and i found the details in this page)

#10 Updated by cpg almost 7 years ago

the user has a system where this happens:

[root@localhost system]# /usr/bin/amahi-plex
Illegal instruction (core dumped)

with some research, the user is running an AMD Athlon(tm) 64 Processor 3200+ processor. This is a bit old and perhaps Plex are compiling with Intel optimization flags, which they should not be doing. they acknowledge they at some point used intel-specific compiler flags

#11 Updated by cpg almost 7 years ago

  • Status changed from New to Closed
  • Assignee changed from jaredmalik to cpg

as a work-around, i downgraded amahi-plex for this user and disabled the automatic updates permanently.

sad that this happens, but we cannot do much about this. intel fights to ensure bad experiences happen in non-intel chips.

Also available in: Atom