You mean the docker repository like this?
plexinc/pms-docker:latest
I believe so… It’s best to look in the Docker forum. They have a lot of help & examples there for many platforms.
Is this the same issue on Netgear debian firmware? I can’t get Plex to update and now I can’t get it to start either. Gives me error during post-install script.
The PMS images on Docker Hub are 7 months old. When will they be updated to include udev?
@papertigers said:
@StSimm1 said:
Fixed in 1.7.5Still seeing the issue over here.
Same for me. I had originally posted in another thread:
https://forums.plex.tv/discussion/277595/1-7-4-dpkg-error-processing-package-plexmediaserver-configure
but will move my reporting here.
I’m running Plex in an Ubuntu 17.04 container, on Ubuntu 17.04 server. Never had a problem before now.
So far I tried an apt purge plexmediaserver and rm /lib/systemd/system/plexmediaserver.service* and rm /etc/systemd/system/plexmediaserver.service* and rm -rf /var/lib/plexmediaserver for good measure (all my data is backed up elsewhere so I’m not concerned with wiping things in the container for testing)
I’m still getting
root@plex:~# dpkg -i plexmediaserver_1.7.5.4035-313f93718_amd64.deb
Selecting previously unselected package plexmediaserver.
(Reading database ... 27935 files and directories currently installed.)
Preparing to unpack plexmediaserver_1.7.5.4035-313f93718_amd64.deb ...
Unpacking plexmediaserver (1.7.5.4035-313f93718) ...
Setting up plexmediaserver (1.7.5.4035-313f93718) ...
dpkg: error processing package plexmediaserver (--install):
subprocess installed post-installation script returned error exit status 2
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu17) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Errors were encountered while processing:
plexmediaserver
root@plex:~# dpkg --configure -D 777 plexmediaserver
D000001: ensure_diversions: new, (re)loading
D000001: process queue pkg plexmediaserver:amd64 queue.len 0 progress 1, try 1
D000040: checking dependencies of plexmediaserver:amd64 (- <none>)
D000040: ok 2 msgs >><<
D000040: checking Breaks
Setting up plexmediaserver (1.7.5.4035-313f93718) ...
D000002: fork/exec /var/lib/dpkg/info/plexmediaserver.postinst ( configure )
dpkg: error processing package plexmediaserver (--configure):
subprocess installed post-installation script returned error exit status 2
D000001: ensure_diversions: same, skipping
Errors were encountered while processing:
plexmediaserver
doing sh -x /var/lib/dpkg/info/plexmediaserver.postinst
still gets me:
...
+ [ 1 = 0 ]
+ [ -f /etc/systemd/system/plexmediaserver.service ]
+ [ -f /sbin/udevadm ]
+ udevadm control --reload-rules
@tcdiem is a little more skilled than me, but as he mentions running “in a container and udev isn’t running” – I’m also running in an lxd container, and udev isn’t running. I also get:
root@plex:~# udevadm control --reload-rules
root@plex:~# echo $?
2
For now I think I’ll try to get around it, but it still isn’t fixed in the 1.7.5 package.
@opentoe@gmail.com said:
I’m using unraid and have no clue on updating the PMS docker. Is there even a way to perform that? It should follow other docker rules on unraid, when there is an update it should indicate on the unraid portal page there is an update. Apparently PMS isn’t taking that route and going to make this a time consuming process for people that don’t use the command line a lot?
Try restarting the PMS docker. Depending on where you got it from, it should seek out the latest version while restarting.
Folks,
Updating information for you:
- Two devs and I resolved the issue yesterday afternoon (EDT timezone), almost 24 hours ago now
- We have made changes which don’t need
--reload-rulesbut still accomplish what PMS needs by solely using the triggers. This allows it to run in chroot environments (Docker & LXC) as well as elevated seteuid() (sudo)
The base docker image is being updated and in QA.
@StSimm1 said:
Fixed in 1.7.5
Hello StSimm1:
It is not fixed. As I’ve made several comments and screenshots and all info before, it still gives retcode =2 because udevd is not running. Not only because udevadm does not exists (which was on a thread linked here. Look at my screenshots above and you can confirm that udevadm control returns retcode=2 when it cannot contact the udevd.
AFAIK file not found is retcode == 1.
Please look at my comments also on how other packages (including udev itself) addresses the issue (by using ‘||true’).
@tcdiem said:
@StSimm1 said:
Fixed in 1.7.5Hello StSimm1:
It is not fixed. As I’ve made several comments and screenshots and all info before, it still gives retcode =2 because udevd is not running. Not only because udevadm does not exists (which was on a thread linked here. Look at my screenshots above and you can confirm that udevadm control returns retcode=2 when it cannot contact the udevd.AFAIK file not found is retcode == 1.
Please look at my comments also on how other packages (including udev itself) addresses the issue (by using ‘||true’).
ALL:
Kindly go check now.
New Docker base image is available.
Corrected version 1.7.5 is available. This is a rebuild, NOT a repackage.
It has the right version number inside of PMS so when a new release is out it will supersede it properly.
@ChuckPA said:
Kindly go check now.
New Docker base image is available.
Corrected version 1.7.5 is available. This is a rebuild, NOT a repackage.
It has the right version number inside of PMS so when a new release is out it will supersede it properly.
Where can I download the corrected version?
On the downloads page shows 1.7.5.4035-313f93718, SHA1 f43884732dfb1eda70329ee596666655e9c10217, which was the “not-fixed 1.7.5”.
1.7.5 still fails for me…
Running plex in an lxd container.
Unpacking plexmediaserver (1.7.5.4035-313f93718) over (1.7.3.3937-70f781325) …
Setting up plexmediaserver (1.7.5.4035-313f93718) …
dpkg: error processing package plexmediaserver (–install):
subprocess installed post-installation script returned error exit status 2
Processing triggers for ureadahead (0.100.0-19) …
Processing triggers for systemd (229-4ubuntu17) …
Processing triggers for mime-support (3.59ubuntu1) …
Errors were encountered while processing:
plexmediaserver
How can I fix this??
Folks:
It is the holiday weekend here. Here is the link I have for PMS 1.7.5.4036 (not 4035). I was out of sync with Engineering and apologize for it
Please try it as follows:
- remove the installed package
apt-get clean all- install this package
If you still have the issue, I need to know the following:
Is your Ubuntu distro a fresh install or an upgrade?
Do you have udev installed (apt list --installed | grep udev)
cat /proc/1/comm output
PMS_1.7.5.4036 https://drive.google.com/open?id=0B57qR6p2QjXpVWtZYjVUcVI1WjQ
@ChuckPA said:
Folks:It is the holiday weekend here. Here is the link I have for PMS 1.7.5.4036 (not 4035). I was out of sync with Engineering and apologize for it
Please try it as follows:
- remove the installed package
apt-get clean all- install this package
If you still have the issue, I need to know the following:
Is your Ubuntu distro a fresh install or an upgrade?
Do you have udev installed (apt list --installed | grep udev)
cat /proc/1/comm outputPMS_1.7.5.4036 https://drive.google.com/open?id=0B57qR6p2QjXpVWtZYjVUcVI1WjQ
Hi @ChuckPA,
The download that you provided installed without issues!
Thanks a alot!
FYI.
Ubuntu 16.04.02 LTS running in an Linux container in Proxmox. (Fresh install).
libudev1/xenial-updates,now 229-4ubuntu17 amd64 [installed]
udev/xenial-updates,now 229-4ubuntu17 amd64 [installed]
/Jo Christian
@ChuckPA said:
Folks:It is the holiday weekend here. Here is the link I have for PMS 1.7.5.4036 (not 4035). I was out of sync with Engineering and apologize for it
Please try it as follows:
- remove the installed package
apt-get clean all- install this package
PMS_1.7.5.4036 https://drive.google.com/open?id=0B57qR6p2QjXpVWtZYjVUcVI1WjQ
Hi @ChuckPA
Thank you for the fix. This release works for me without any issue.
I’m running Plex inside an LXC as well. Thank you for getting this working for us @ChuckPA.
Question though, why hasn’t the fixed 4036 version hit the official site yet?
No, it hasn’t. A lot of folks are on vacation and I don’t have authority to push that file else I would have.
FYI (as of this afternoon) 1.7.5.4035 is still in the repo. Manual pull/install of 1.7.5.4036 went flawlessly.
thanks!
I am experiencing this issue trying to install 1.7.6.4058.
I performed:
- apt remove plexmediaserver
- apt-get clean all
- dpkg -i plexmediaserver_1.7.6.4058-8fa494d15_amd64.deb
I get:
root@plex:/# dpkg -i plexmediaserver_1.7.6.4058-8fa494d15_amd64.deb
Selecting previously unselected package plexmediaserver.
(Reading database ... 27938 files and directories currently installed.)
Preparing to unpack plexmediaserver_1.7.6.4058-8fa494d15_amd64.deb ...
Unpacking plexmediaserver (1.7.6.4058-8fa494d15) ...
Setting up plexmediaserver (1.7.6.4058-8fa494d15) ...
dpkg: error processing package plexmediaserver (--install):
subprocess installed post-installation script returned error exit status 2
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu17) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Errors were encountered while processing:
plexmediaserver
and
root@plex:/# dpkg --configure -D 777 plexmediaserver
D000001: ensure_diversions: new, (re)loading
D000001: process queue pkg plexmediaserver:amd64 queue.len 0 progress 1, try 1
D000040: checking dependencies of plexmediaserver:amd64 (- <none>)
D000040: ok 2 msgs >><<
D000040: checking Breaks
Setting up plexmediaserver (1.7.6.4058-8fa494d15) ...
D000002: fork/exec /var/lib/dpkg/info/plexmediaserver.postinst ( configure 1.7.5.4035-313f93718 )
dpkg: error processing package plexmediaserver (--configure):
subprocess installed post-installation script returned error exit status 2
D000001: ensure_diversions: same, skipping
Errors were encountered while processing:
plexmediaserver
I never tried installing the rebuilt 1.7.5.4036 because I’d done the workaround for the error code in the postinst script for the pervious 1.7.5 build, so I can’t confirm whether that would have worked.
If you still have the issue, I need to know the following:
Is your Ubuntu distro a fresh install or an upgrade?
it was, long ago (over a year?) a fresh container of Ubuntu 16.04.2.
It is still Ubuntu 16.04.2 running inside lxd (lxc) on Ubuntu 17.04 (also was a fresh install)
Do you have udev installed (apt list --installed | grep udev)
libudev1/xenial-updates,now 229-4ubuntu17 amd64 [installed]
udev/xenial-updates,now 229-4ubuntu17 amd64 [installed]
cat /proc/1/comm output
systemd
Just updating to report: finally no error in 1.8.0.4109 when installing with dpkg.
