Jump to content

Permission denied.


DreadManX

Recommended Posts

DreadManX

Greetings,

 

I'm running Ubuntu 16.04.01 with the latest updates as of now.  Outside of normal system upgrades, I've not done anything that might cause this issue.   It was working fine yesterday, but not today after a reboot.  When I try to start Emby-server I'm getting the following:

:/usr/lib/emby-server# emby-server start
env: ‘/usr/lib/emby-server/x86_64-linux-gnu’: Permission denied

From /var/log/syslog

Apr  2 20:23:53 bigiron systemd[1]: Started Emby Media Server.
Apr  2 20:23:53 bigiron systemd[1]: Created slice User Slice of emby.
Apr  2 20:23:53 bigiron systemd[1]: Starting User Manager for UID 127...
Apr  2 20:23:53 bigiron systemd[1]: Started Session c8 of user emby.
Apr  2 20:23:53 bigiron systemd[21596]: Reached target Sockets.
Apr  2 20:23:53 bigiron systemd[21596]: Reached target Timers.
Apr  2 20:23:53 bigiron systemd[21596]: Reached target Paths.
Apr  2 20:23:53 bigiron systemd[21596]: Reached target Basic System.
Apr  2 20:23:53 bigiron systemd[21596]: Reached target Default.
Apr  2 20:23:53 bigiron systemd[21596]: Startup finished in 21ms.
Apr  2 20:23:53 bigiron systemd[1]: Started User Manager for UID 127.
Apr  2 20:23:53 bigiron emby-server[21579]: env: ‘/usr/lib/emby-server/x86_64-linux-gnu’: Permission denied
Apr  2 20:23:53 bigiron systemd[1]: emby-server.service: Main process exited, code=exited, status=126/n/a
Apr  2 20:23:53 bigiron console-kit-daemon[2541]: console-kit-daemon[2541]: GLib-CRITICAL: Source ID 284 was not found when attempting to remove it
Apr  2 20:23:53 bigiron console-kit-daemon[2541]: GLib-CRITICAL: Source ID 284 was not found when attempting to remove it
Apr  2 20:23:53 bigiron systemd[1]: Stopping User Manager for UID 127...
Apr  2 20:23:53 bigiron systemd[21596]: Reached target Shutdown.
Apr  2 20:23:53 bigiron systemd[21596]: Starting Exit the Session...
Apr  2 20:23:53 bigiron systemd[21596]: Stopped target Default.
Apr  2 20:23:53 bigiron systemd[21596]: Stopped target Basic System.
Apr  2 20:23:53 bigiron systemd[21596]: Stopped target Paths.
Apr  2 20:23:53 bigiron systemd[21596]: Stopped target Sockets.
Apr  2 20:23:53 bigiron systemd[21596]: Stopped target Timers.
Apr  2 20:23:53 bigiron systemd[21596]: Received SIGRTMIN+24 from PID 21636 (kill).
Apr  2 20:23:53 bigiron systemd[1]: emby-server.service: Unit entered failed state.
Apr  2 20:23:53 bigiron systemd[1]: emby-server.service: Failed with result 'exit-code'.
Apr  2 20:23:53 bigiron systemd[1]: Stopped User Manager for UID 127.
Apr  2 20:23:53 bigiron systemd[1]: Removed slice User Slice of emby.

Can someone please help?  Other than rebooting for a kernel upgrade and doing the normal apt update && apt upgrade, I've done nothing that I can think of to cause this.  On a whim I tried chown emby:emby /usr/lib/emby-server/x86_64-linux-gnu  but that didn't do.

Link to comment
Share on other sites

DreadManX

Unfortunately after several hours of troubleshooting, I ended up just apt --purge remove emby-server; rm -rf *emby* on the system, and reinstalling and it's magically working now :(

Link to comment
Share on other sites

Strange. I wonder if you could have just rebooted following that error, as if something was holding a lock on a required resource perhaps.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...