PMS 1.16.3.1433 on Ubuntu 32 bit

I can’t get 1.16.1433 to start on Ubuntu 18.04 32bit. 1.14 worked. I’m really getting irritated about it. I’ve seen many, many posts about the problem and NO posts on how to fix it. Rather, the pattern is the same, post logs, post systemctl status, etc.

NO ANSWERS.

There is something wrong with the Ubuntu server and it needs to be addressed.

I’ve now rolled back many times. I’ve re-booted. I’ve reinstalled (including purge). Nothing is working.

Someone, PLEASE, give us easy to find direction on how to fix this problem. I swear, my lifetime membership is starting to feel like a waste.

@themadskeptic

I have broken you out of that other thread so you have a dedicated one.

Please tell me the following:

  1. CPU
  2. Memory
  3. Can you manually grab the log files and attach them?
sudo sh
tar cfz /tmp/Plexlogs.tar.gz "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs"
  1. CPU is an old Pentium 4
  2. MemTotal: 1021228 kB
  3. Files are attached.Plexlogs.tar.gz (12.1 MB)

Thanks for the logs.

Guess what? It’s still there and running.
I can see you tried to access from FireFox

I an also see this is the first time this machine has been run since 0.9.15.6 (PMS.2.log)

Apr 01, 2016 02:10:16 [0xb23feb40] INFO - Plex Media Server v0.9.15.6.1714-7be11e1 - ubuntu PC i686 - build: linux-ubuntu-i686 ubuntu
Apr 01, 2016 02:10:16 [0xb23feb40] INFO - Linux version: 3.13.0-79-generic (#123-Ubuntu SMP Fri Feb 19 14:28:32 UTC 2016)
Apr 01, 2016 02:10:16 [0xb23feb40] INFO - Processor               Intel(R) Pentium(R) 4 CPU 2.00GHz

I see you ran for about 7 hours on 1.14.1.5488 at which time it did nothing (PMS.1.log).

Aug 01, 2019 13:30:32.103 [0xb31feb40] INFO - Plex Media Server v1.14.1.5488-cc260c476 - ubuntu PC i686 - build: linux-ubuntu-i686 ubuntu - GMT -04:00
Aug 01, 2019 13:30:32.306 [0xb31feb40] INFO - Linux version: 4.15.0-54-generic (#58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019), language: en-US
Aug 01, 2019 13:30:32.306 [0xb31feb40] INFO - Processor               Intel(R) Pentium(R) 4 CPU 2.00GHz

ending with

Aug 01, 2019 20:46:34.392 [0xb45fe280] DEBUG - Captured session 16.
Aug 01, 2019 20:46:34.393 [0xb45fe280] DEBUG - Captured session 17.
Aug 01, 2019 20:46:34.393 [0xb45fe280] DEBUG - Captured session 18.
Aug 01, 2019 20:46:34.393 [0xb45fe280] DEBUG - Captured session 19.
Aug 01, 2019 20:46:36.021 [0xb45fe280] DEBUG - Database: Shutting down.
Aug 01, 2019 20:46:36.021 [0xb45fe280] DEBUG - Captured session 0.
Aug 01, 2019 20:46:36.022 [0xb45fe280] DEBUG - Captured session 1.

I am going to suggest you wipe this clean and start the database over.
I think you’ll be a lot happier if you do. I can’t tell which is which here 0.9.15.6 or 1.14.1.5488

How would you like to proceed?

Your description of my logs isn’t accurate. I’ve been running 1.14.1.3.5488 for months (January? February?). While I may not stream something every day, the server is active 24/7.

I think I’ll have to wipe and completely reinstall because this is unacceptable. I sudo apt remove --purge’d the 1.14 version the other day and tried sudo dpkg -i’ing the 1.16 and I got the same symptoms I’ve gotten before - which is immediately observable by not being able to access the server via the browser.

I just dpkg -r the existing plexmediaserver and rm -r the /var/lib/plexmediaserver/Library/Application Support/Plex Media Server.

I am unable to connect via Firefox.

systemctl status plexmediaserver returns:

sudo systemctl status plexmediaserver
● plexmediaserver.service - Plex Media Server
   Loaded: loaded (/lib/systemd/system/plexmediaserver.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Fri 2019-08-02 07:00:52 EDT; 4s ago
  Process: 18951 ExecStart=/bin/sh -c  PLEX_MEDIA_SERVER_INFO_VENDOR="$(grep ^NAME= /etc/os-release | awk -F= "{print \$2}" | tr -d \" )"  PLEX_MEDIA
  Process: 18949 ExecStartPre=/bin/sh -c /usr/bin/test -d "${PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR}" || /bin/mkdir -p "${PLEX_MEDIA_SERVER_APPLIC
 Main PID: 18951 (code=exited, status=132)

Aug 02 07:00:52 camarasaurus systemd[1]: plexmediaserver.service: Main process exited, code=exited, status=132/n/a
Aug 02 07:00:52 camarasaurus systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
Aug 02 07:00:57 camarasaurus systemd[1]: plexmediaserver.service: Service hold-off time over, scheduling restart.
Aug 02 07:00:57 camarasaurus systemd[1]: plexmediaserver.service: Scheduled restart job, restart counter is at 3.
Aug 02 07:00:57 camarasaurus systemd[1]: Stopped Plex Media Server.
Aug 02 07:00:57 camarasaurus systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Aug 02 07:00:57 camarasaurus systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
Aug 02 07:00:57 camarasaurus systemd[1]: Failed to start Plex Media Server.

This is the same behavior I’ve been getting for the last many, many months.

I took the log ZIP you gave me. Those are the 3 versions I pulled from it. I showed the file names they came from as well.

I concur nothing makes sense but that is what your log files tell me and why I ask.
Are you redirecting log output to somewhere else like SYSLOG ?

I have not explanation about the logs. I’m not redirecting them elsewhere. Perhaps something was deleted accidentally while I’ve been trying to fix this problem.

Still, the systemctl I posted above is from a new install of 1.16. It isn’t starting.

sudo journalctl -xe | grep -i plex

Now, look through the output slowly.
You will you see where it will call out the specific reason it’s not starting.
It will be something obvious like “Permission Denied” or similar.

Was the metadata library copied from elsewhere?
If so, the UID/GID of the Library will be different. Some of this is auto-detected at installation time but it can happen that not all is.

I don’t see anything obvious like you suggested. Also, I haven’t copied any metadata from anywhere.

Here’s the output:

sudo journalctl -xe | grep -i plex
Aug 02 19:48:28 camarasaurus sudo[18915]:    myron : TTY=pts/0 ; PWD=/home/myron ; USER=root ; COMMAND=/bin/systemctl start plexmediaserver
Aug 02 19:48:28 camarasaurus systemd[1]: Starting Plex Media Server...
-- Subject: Unit plexmediaserver.service has begun start-up
-- Unit plexmediaserver.service has begun starting up.
Aug 02 19:48:28 camarasaurus systemd[1]: Started Plex Media Server.
-- Subject: Unit plexmediaserver.service has finished start-up
-- Unit plexmediaserver.service has finished starting up.
Aug 02 19:48:29 camarasaurus kernel: traps: Plex Media Serv[18930] trap invalid opcode ip:b7206995 sp:bfd55bc0 error:0 in libopencv_imgproc.so.3.1[b70d9000+289000]
Aug 02 19:48:30 camarasaurus systemd[1]: plexmediaserver.service: Main process exited, code=exited, status=132/n/a
Aug 02 19:48:30 camarasaurus systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
Aug 02 19:48:33 camarasaurus sudo[18934]:    myron : TTY=pts/0 ; PWD=/home/myron ; USER=root ; COMMAND=/bin/systemctl status plexmediaserver
Aug 02 19:48:35 camarasaurus systemd[1]: plexmediaserver.service: Service hold-off time over, scheduling restart.
Aug 02 19:48:35 camarasaurus systemd[1]: plexmediaserver.service: Scheduled restart job, restart counter is at 1.
-- Automatic restarting of the unit plexmediaserver.service has been scheduled, as the result for
Aug 02 19:48:35 camarasaurus systemd[1]: Stopped Plex Media Server.
-- Subject: Unit plexmediaserver.service has finished shutting down
-- Unit plexmediaserver.service has finished shutting down.
Aug 02 19:48:35 camarasaurus systemd[1]: Starting Plex Media Server...
-- Subject: Unit plexmediaserver.service has begun start-up
-- Unit plexmediaserver.service has begun starting up.
Aug 02 19:48:35 camarasaurus systemd[1]: Started Plex Media Server.
-- Subject: Unit plexmediaserver.service has finished start-up
-- Unit plexmediaserver.service has finished starting up.
Aug 02 19:48:35 camarasaurus kernel: traps: Plex Media Serv[18949] trap invalid opcode ip:b7137995 sp:bfdbb250 error:0 in libopencv_imgproc.so.3.1[b700a000+289000]
Aug 02 19:48:36 camarasaurus systemd[1]: plexmediaserver.service: Main process exited, code=exited, status=132/n/a
Aug 02 19:48:36 camarasaurus systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
Aug 02 19:48:41 camarasaurus systemd[1]: plexmediaserver.service: Service hold-off time over, scheduling restart.
Aug 02 19:48:41 camarasaurus systemd[1]: plexmediaserver.service: Scheduled restart job, restart counter is at 2.
-- Automatic restarting of the unit plexmediaserver.service has been scheduled, as the result for
Aug 02 19:48:41 camarasaurus systemd[1]: Stopped Plex Media Server.
-- Subject: Unit plexmediaserver.service has finished shutting down
-- Unit plexmediaserver.service has finished shutting down.
Aug 02 19:48:41 camarasaurus systemd[1]: Starting Plex Media Server...
-- Subject: Unit plexmediaserver.service has begun start-up
-- Unit plexmediaserver.service has begun starting up.
Aug 02 19:48:41 camarasaurus systemd[1]: Started Plex Media Server.
-- Subject: Unit plexmediaserver.service has finished start-up
-- Unit plexmediaserver.service has finished starting up.
Aug 02 19:48:41 camarasaurus kernel: traps: Plex Media Serv[18965] trap invalid opcode ip:b7190995 sp:bfcd1390 error:0 in libopencv_imgproc.so.3.1[b7063000+289000]
Aug 02 19:48:42 camarasaurus systemd[1]: plexmediaserver.service: Main process exited, code=exited, status=132/n/a
Aug 02 19:48:42 camarasaurus systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
Aug 02 19:48:47 camarasaurus systemd[1]: plexmediaserver.service: Service hold-off time over, scheduling restart.
Aug 02 19:48:47 camarasaurus systemd[1]: plexmediaserver.service: Scheduled restart job, restart counter is at 3.
-- Automatic restarting of the unit plexmediaserver.service has been scheduled, as the result for
Aug 02 19:48:47 camarasaurus systemd[1]: Stopped Plex Media Server.
-- Subject: Unit plexmediaserver.service has finished shutting down
-- Unit plexmediaserver.service has finished shutting down.
Aug 02 19:48:47 camarasaurus systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Aug 02 19:48:47 camarasaurus systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
Aug 02 19:48:47 camarasaurus systemd[1]: Failed to start Plex Media Server.
-- Subject: Unit plexmediaserver.service has failed
-- Unit plexmediaserver.service has failed.

Thank you for the logs. Now I see what’s happening:

Aug 02 19:48:35 camarasaurus kernel: traps: Plex Media Serv[18949] trap invalid opcode ip:b7137995 sp:bfdbb250 error:0 in libopencv_imgproc.so.3.1[b700a000+289000]
Aug 02 19:48:36 camarasaurus systemd[1]: plexmediaserver.service: Main process exited, code=exited, status=132/n/a
Aug 02 19:48:36 camarasaurus systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.

The invalid instruction trap will occur in 32 bit systems if you don’t have a high enough SSE instruction set. PMS is compiled to require 4.2 (which has been around some 10+ years)

Ref: https://en.wikipedia.org/wiki/SSE4

The new compilers, as of PMS 1.15.0, take have added this optimization.
Therefore, regrettably, the best you can run is PMS 1.14.1.5488

Can this be promenently posted somewhere? I’ve wasted a lot of time and have become really frustrated trying to get something that’s supposed to work with my OS to work when, in fact, it doesn’t work with my hardware. Some of us have been running Plex for many years on old hardware and I think some sort of warning would be beneficial

Now, I have the OLD server running again but, now I am getting a “Secure Connection Failed” page on Firefox when I try to go in and reconfigure everything. This experience has been pretty frustrating.

Screenshot_2019-08-03_07-17-35|690x387

Edit: all fixed. I forgot I needed to access the server locally first and had forgotten I had disabled AllowTcpForwarding in sshd_config. 1.14 is now re-indexing my files.

When 1.15.0 was in Forum Preview testing, all of this was disclosed.
I don’t know how much more prominently it can be displayed unless you mean to have minimum hardware requirements listed in the support documents?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.