Jump to content

Ubuntu


Luke

Recommended Posts

hurricanehrndz

I'm not sure what this will do to your system, I have not tested it thoroughly. 

 

Replace /etc/sudoers.d/emby with https://raw.githubusercontent.com/hurricanehrndz/Emby.Build/ft_docker/builders/emby-server/debfiles/emby

 

Replace /usr/bin/emby-server with https://raw.githubusercontent.com/hurricanehrndz/Emby.Build/ft_docker/builders/emby-server/debfiles/bin/emby-server

Link to comment
Share on other sites

nicheplayer

Okay, I will write some new files for you soon. 

 

Thank you. I really appreciate your help. I'm not sure why the admins at my VPS are running Debian 7, but, then, I don't have any control over it.

 

I'm not sure what this will do to your system, I have not tested it thoroughly. 

 

Replace /etc/sudoers.d/emby with https://raw.githubusercontent.com/hurricanehrndz/Emby.Build/ft_docker/builders/emby-server/debfiles/emby

 

Replace /usr/bin/emby-server with https://raw.githubusercontent.com/hurricanehrndz/Emby.Build/ft_docker/builders/emby-server/debfiles/bin/emby-server

 

What's the best way to do that? Just scp them into their respective directories to overwrite?

Link to comment
Share on other sites

hurricanehrndz

Yeah, make sure they are both executable or wget them from the server itself.

 

Stop emby-server, before overwriting the existing files. Start emby-server. And then try the restart.sh script.

Edited by hurricanehrndz
Link to comment
Share on other sites

nicheplayer

Yeah, make sure they are both executable or wget them from the server itself.

 

What should I run for wget, and do I have to do it from the destination directory (i.e., /etc/sudoers.d/ and /usr/bin/emby-server, respectively)?

Link to comment
Share on other sites

hurricanehrndz

As root run the following

rm /etc/sudoers.d/emby
wget https://raw.githubusercontent.com/hurricanehrndz/Emby.Build/ft_docker/builders/emby-server/debfiles/emby > /etc/sudoers.d/emby
chmod +x /etc/sudoers.d/emby
rm /usr/bin/emby-server
wget https://raw.githubusercontent.com/hurricanehrndz/Emby.Build/ft_docker/builders/emby-server/debfiles/bin/emby-server > /usr/bin/emby-server
chmod +x /usr/bin/emby-server


su nicheplayer007
sudo /etc/init.d/emby-server start 

You shouldn't be prompted for a password

  • Like 1
Link to comment
Share on other sites

nicheplayer

Got all the way to 

 

 

su nicheplayer007

 

and got this after running 

sudo /etc/init.d/emby-server start
[sudo] password for nicheplayer007: 
nicheplayer007 is not in the sudoers file.  This incident will be reported.
Link to comment
Share on other sites

hurricanehrndz

 

Got all the way to 

 

and got this after running 

sudo /etc/init.d/emby-server start
[sudo] password for nicheplayer007: 
nicheplayer007 is not in the sudoers file.  This incident will be reported.

 

cat /etc/group | grep emby check if nicheplayer is in group emby.

Link to comment
Share on other sites

nicheplayer

lol, This is the funniest thing I have ever seen in my life.

 

I hear ya. It's not like I have a huge install here, so I'm totally good with wiping everything and starting from scratch. But in any case, running

 

 

cat /etc/group | grep emby

gets me

root@darktruth:~# cat /etc/group | grep emby
emby:x:117:
root@darktruth:~# 
Link to comment
Share on other sites

hurricanehrndz

weird..,

 

okay do the following, start as root

usermod -G emby nicheplayer007

cat /etc/group | emby <--- ensure nicheplayer007 shows up

 

su nicheplayer007

sudo /etc/init.d/emby-server start <--- should not ask for a password. 

Link to comment
Share on other sites

nicheplayer

First command ran without comment. Then I ran

cat /etc/group | emby

and got

root@machine:/etc# cat /etc/group | emby
-bash: emby: command not found

so then I nanoed into /etc/group and found nicheplayer007 in the following places:

nicheplayer007:x:1000:
openvpn:x:1001:
openvpn_as:x:1002:
plex:x:113:
messagebus:x:114:
colord:x:115:
fuse:x:116:
emby:x:117:nicheplayer007
Link to comment
Share on other sites

nicheplayer

I proceeded with your directions anyway, for the hell of it, and got

root@machine:/etc# su nicheplayer007
$ sudo /etc/init.d/emby-server start
[sudo] password for nicheplayer007: 
nicheplayer007 is not in the sudoers file.  This incident will be reported.
Link to comment
Share on other sites

hurricanehrndz

Well I'm beat for today. I heading to bed, I will see if I can try and track it down. It makes no sense to me. The group emby is in the sudoers and I made you part of that group.

  • Like 1
Link to comment
Share on other sites

nicheplayer

Well I'm beat for today. I heading to bed, I will see if I can try and track it down. It makes no sense to me. The group emby is in the sudoers and I made you part of that group.

I hear ya! Thanks a lot for your help!! I'll get it nailed down eventually!

Link to comment
Share on other sites

nicheplayer

What's the permission of the emby file in sudoers.d folder

:/etc/sudoers.d# ls -la
total 12
drwxr-xr-x   2 root root 4096 Dec 12 02:11 .
drwxr-xr-x 105 root root 4096 Dec 12 02:26 ..
-rwxr-xr-x   1 root root    0 Dec 12 02:11 emby
-r--r-----   1 root root  958 Mar  1  2013 README
Link to comment
Share on other sites

nicheplayer

FWIW, as soon as I do the 

su nicheplayer007

line my command prompt turns into a $. When I run 

sudo /etc/init.d/emby-server start

from that $ prompt, I get

[sudo] password for nicheplayer007: 
nicheplayer007 is not in the sudoers file.  This incident will be reported.

Oh well. A job for another day!

Link to comment
Share on other sites

nicheplayer
cat /etc/sudoers.d/emby

Just returned me to the system prompt. Then:

root@machine:/# ls -lah /etc/sudoers.d/
total 12K
drwxr-xr-x   2 root root 4.0K Dec 12 02:11 .
drwxr-xr-x 105 root root 4.0K Dec 12 02:26 ..
-r--r-----   1 root root    0 Dec 12 02:11 emby
-r--r-----   1 root root  958 Mar  1  2013 README
Link to comment
Share on other sites

hurricanehrndz

Well there is nothing in the file... of course it's not going to work.

 

Try and edit the file and just copy and paste the lines. 

 

Or download it to your home directory and then move them where there suppose to go.

Edited by hurricanehrndz
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...