Explain please? If there is anything which might need work, it’s init.
I had to recreate everything from scratch.
init-based systems are everywhere and used countless diferrent ways.
Help me understand what isn’t there and I’ll get it back.
My Ubuntu 16.04 box is not in the best shape and I don’t use it for very much anymore.
However I seem to be running a init/systemd hybrid which is not allowing me to install the new deb package.
Is there an easy fix to this or would I be better off finally upgrading.
what does cat /proc/1/comm return at the command line?
Stating it’s a hybrid means?
After attempting to install, /tmp/plexinstaller.log exists. may I see it?
Hey - updated to the new official version … go thru’ install successfully but it’s removing the plexmediaserver service. Reverting to plexmediaserver_1.18.4.2164-2aa83397b-sysvinit_amd64.deb sorts it out. I know that’s not enough info. let me know what you need me to provide to help.
Thanks.
Please help me understand what’s missing.
- You assert someone else’s sysv-init packaging works.
- You’re telling me I remove a ‘service’ file? Service files are indicative of systemd.
Please provide
- Details about what is being removed (pathnames)
- The contents of
/tmp/plexinstaller.log - If a container environment
- Details of any hand customizations.
Look in /etc/init.d/ for plexmediaserver files. Use the one that comes in the official Plex deb and not the one in the deprecated sysvinit_amd64 deb. It should have a newer date. We worked very closely with Chuck to bring back sysvinit support and as such, the sysvinit_amd64.deb packages should no longer be used.
I’m on wheezy so i was waiting for this release cos’ of sysvinit support.
The package I mentioned above I believe was the last one provided by Ryushin (thanks) on the now closed “New Linux installer - Forum preview & beta testing” thread.
Yesterday I reinstated my apt sources to include “deb https://downloads.plex.tv/repo/deb public main” and updated to the latest plexmediaserver - on doing so i noticed pms was not running at the end of the installation and “service plexmediaserver start” well does nothing as there is no plexmediaserver service anymore.
What being removed is /etc/init.d/plexmediaserver
Also - post install there is no /tmp/plexinstaller.log (looked on whole drive!)
The SYSV support is PlexPass beta.
It isn’t in the public repository yet.
Download and install manually.
Running Plex as a native application on ubuntu
sudo dpkg -i plexmediaserver_1.18.5.2260-056ab4be9_amd64.deb
[sudo] password for mike:
(Reading database ... 165542 files and directories currently installed.)
Preparing to unpack plexmediaserver_1.18.5.2260-056ab4be9_amd64.deb ...
Removed /etc/systemd/system/multi-user.target.wants/plexmediaserver.service.
PlexMediaServer install: Pre-installation Validation.
PlexMediaServer install: Error: "/var/lib/plexmediaserver/Library/Application Support" is not owned by "plex", UID: 122. Found "root" UID: 0 . Please correct before continuing.
dpkg: error processing archive plexmediaserver_1.18.5.2260-056ab4be9_amd64.deb (--install):
new plexmediaserver package pre-installation script subprocess returned error exit status 1
Created symlink /etc/systemd/system/multi-user.target.wants/plexmediaserver.service → /lib/systemd/system/plexmediaserver.service.
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Errors were encountered while processing:
plexmediaserver_1.18.5.2260-056ab4be9_amd64.deb
mike@mike-B450-AORUS-M:/tmp/mozilla_mike0$ getent passwd plex
plex:x:122:127::/var/lib/plexmediaserver:/bin/bash
Let me know what else I can get you
EDIT
just to add to this, this is the same method i used to install the base version on this system, and have upgraded the same way each time. if i did a chown -R on this directory and set it to plex, would that resolve this problem?
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3089 plex 20 0 3100828 128712 35808 S 0.4 1.6 0:13.19 Plex Media Serv
3139 plex 35 15 1876172 52824 10404 S 0.2 0.6 0:04.64 Plex Script Hos
3078 plex 20 0 4624 888 844 S 0.0 0.0 0:00.00 sh
3207 plex 20 0 521936 13908 12340 S 0.0 0.2 0:00.29 Plex Tuner Serv
3246 plex 20 0 966484 45772 10144 S 0.0 0.6 0:01.84 Plex Script Hos
21892 plex 20 0 8344 0 0 S 0.0 0.0 0:00.00 nginx
21893 plex 20 0 8344 0 0 S 0.0 0.0 0:00.00 nginx
it looks like the process is running as plex
I’m having the same issue as @amnacog, but I’m just using a very old, hand rolled Dockerfile. I’ve reverted for the time being, but it seems like there needs to be a way to avoid that check beyond you trying to add lots of possible values to check for. Can there be an environment variable or something we can just set to say “Look, we know you want init or systemd, but it’s cool?”
If you scroll back, you’ll see that was raised above.
The gaping oversight on my part (and everyone else who looked at it, including the community members who helped test), passwd uses grep, video uses getent as it should.
I corrected it within a few hours of it being discovered.
I’m currently waiting for the Engineering/QA turnaround to verify the changes did come through correctly.
We’ve discussed just that case. Where I am leaning, if the logic holds:
- If
init,systemd,linuxserver.io, orbinhexthen treat as according to standard PMS installation rules for those environments. - Anything else defaults to
Process Control: Customand I let go of all start/stop activities. - The unknown is what does the installation script do if ‘Custom’ upon completion of installation? Does it look for something to start? If so, what?
Does this make sense?
@ChuckPa also have the same issue as @amnacog with a custom Docker file.
But from what I’ve seen in this conversation you will solve the issue in the next release (with the sh in /proc/1/comm) correct ?
That’s correct. I’ve taken care of it || [ "$(cat /proc/1/comm)" = "sh" ]
Looking further down the road, the potential exists to have a litany of exceptions.
I’m working on a way now (possibly) have:
- SYSV
- Systemd
- Docker
- LXC
- Custom
Custom would capture everything else. I don’t now how viable that is or what impact it will have on the code itself but this is where I am looking.
That makes sense. Would it make sense to have Custom just do nothing and put up a big warning stating that the user is doing something unsupported and they’re on their own?
The || [ "$(cat /proc/1/comm)" = "sh" ] will take care of my situation, but it seems like explicitly disallowing installs with no way around is rough. Although, could you theoretically just do sh -c 'dpkg -i package.deb' after the latest change if you were falling all the way through to Custom? If that’s the case, maybe Custom just says that is an option, forcing the user to actually read the error message.
The whole purpose of the new packaging was to add intelligence and not let broken installations happen.
With all the former Windows users making their way to Linux, it’s important that we support them as they learn without Linux being “geek only”
Let me ask this way:
Does the installation script reporting its discovered configuration add value or is it just noise ?
@ChuckPa Thank you for your guidance sir 
- plexmediaserver_1.18.5.2260-056ab4be9_amd64.deb installed and working fine.
5 posts were split to a new topic: Correcting media using Whatever-Topic-Name-Isnt-TakenAlready
Im also getting the same error for the first time in history
best solution is to wait for the next plex pass build? Dont wanna mess up my setup
dpkg -i plexmediaserver_1.18.5.2260-056ab4be9_amd64.deb
(Reading database ... 129905 files and directories currently installed.)
Preparing to unpack plexmediaserver_1.18.5.2260-056ab4be9_amd64.deb ...
Removed symlink /etc/systemd/system/multi-user.target.wants/plexmediaserver.service.
PlexMediaServer install: Pre-installation Validation.
PlexMediaServer install: Error: "/var/lib/plexmediaserver/Library/Application Support" is not owned by "plex", UID: 0. Found "avahi" UID: 109 . Please correct before continuing.
dpkg: error processing archive plexmediaserver_1.18.5.2260-056ab4be9_amd64.deb (--install):
subprocess new pre-installation script returned error exit status 1
Created symlink from /etc/systemd/system/multi-user.target.wants/plexmediaserver.service to /lib/systemd/system/plexmediaserver.service.
Processing triggers for libc-bin (2.23-0ubuntu11) ...
Errors were encountered while processing:
plexmediaserver_1.18.5.2260-056ab4be9_amd64.deb
Please stay with the existing version of Plex until the next PlexPass update.
The change was made to relax that to a Warning.
I hope it will complete Engineering and QA review Monday but can’t control schedules.
1 Like
@ChuckPa I apologize for going off topic, but this seems as good a place to ask as anywhere else.
The same improvements you’ve made to the install process for Debian derivatives… any intention on doing the same for CentOS, etc? Just curious You’ve done great work either way. It seems like there are minor hiccups but it’s moving in the right direction.
