Jump to content

Debian


Luke

Recommended Posts

nicheplayer

Hmm, just leave them for now. I will run more test

 

OK. Thank you. I just ran:

 

sudo service emby-server start

 

and got:

emby-server: unrecognized service
Link to comment
Share on other sites

hurricanehrndz

Yeah okay, those are old and haven't been updated, so yes uninstall those packages. Then just do a sudo apt-get install emby-server libsqlite-dev and report back.  apt-get remove --purge. We did a major update this week. We are sort of in a testing phase and trying to see what is left to fix from all the changes.

Edited by hurricanehrndz
Link to comment
Share on other sites

nicheplayer

Yeah okay, those are old and haven't been updated, so yes uninstall those packages. Then just do a sudo apt-get install emby-server libsqlite-dev and report back.  apt-get remove --purge. We did a major update this week. We are sort of in a testing phase and trying to see what is left to fix from all the changes.

 

Well, I seemed to have successfully removed one of the pkgs, but trying to remove the "common" one got me:

dpkg -r imagemagick-common
dpkg: dependency problems prevent removal of imagemagick-common:
 libmagickcore-6.q8-2:amd64 depends on imagemagick-common (= 8:6.9.1-2).
 libmagickwand-6.q8-2:amd64 depends on imagemagick-common (= 8:6.9.1-2).

dpkg: error processing imagemagick-common (--remove):
 dependency problems - not removing
Errors were encountered while processing:
 imagemagick-common

So not sure what's going on there. Do I have to also get rid of these:

libmagic1:amd64    5.11-2+deb7u8  amd64 File type determination library using "magic" numbers
libmagickcore-6.q8-2:amd64   8:6.9.1-2  amd64 low-level image manipulation library -- quantum depth Q8
libmagickcore-6.q8-2-extra:amd64  8:6.9.1-2  amd64 low-level image manipulation library - extra codecs (Q8)
libmagickwand-6.q8-2:amd64  8:6.9.1-2 amd64 image manipulation library

And when you write:

 

 

 

Then just do a sudo apt-get install emby-server libsqlite-dev and report back.  apt-get remove --purge.

 

is there an order to those commands? Do

 

sudo apt-get install emby-server libsqlite-dev

 

first and then 

 

apt-get remove --purge

 

or vice versa? Really sorry to be such a PITA! Thanks very much for your patience.

Edited by nicheplayer
Link to comment
Share on other sites

hurricanehrndz

No worries. I'm happy to help.

 

I would run the following in the this order:

sudo apt-get remove --purge libmagickwand-6.q8-2 libmagickcore-6.q8-2 imagemagick-common emby-server

If that is successful 

sudo apt-get install emby-server
Link to comment
Share on other sites

nicheplayer

All right, ran the first line and got this:

sudo apt-get remove --purge libmagickwand-6.q8-2 libmagickcore-6.q8-2 imagemagick-common emby-server
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package 'emby-server' is not installed, so not removed
The following packages were automatically installed and are no longer required:
  libdjvulibre-text libdjvulibre21 libfftw3-3 libilmbase6 liblqr-1-0 libnetpbm10 libopenexr6 libwebp5 libwmf0.2-7 netpbm
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  imagemagick-common* libmagickcore-6.q8-2* libmagickcore-6.q8-2-extra* libmagickwand-6.q8-2*
0 upgraded, 0 newly installed, 4 to remove and 83 not upgraded.
70 not fully installed or removed.
After this operation, 8,609 kB disk space will be freed.
Do you want to continue [Y/n]? Y

Proceeded, got a bunch of output, and ended up at a prompt, but no error message there. So...try your second line of code now?

Link to comment
Share on other sites

nicheplayer

Actually, there was one error along the way:
 

adduser: Warning: The home directory `/var/lib/colord' does not belong to the user you are currently creating.
Link to comment
Share on other sites

nicheplayer

Yes, and do you mind waiting a couple of minutes. I got to push an update to fix some issues.

 

Of course. I'll wait as long as you like. Thanks again.

Link to comment
Share on other sites

nicheplayer

What command have you run by the way?

 

You mean what's the last one I ran? It was:

sudo apt-get remove --purge libmagickwand-6.q8-2 libmagickcore-6.q8-2 imagemagick-common emby-server
Link to comment
Share on other sites

hurricanehrndz

Okay awesome, for now since I see you have some issues with your packages run the following:

 

apt-get -f install

apt-get autoremove

apt-get clean

  • Like 1
Link to comment
Share on other sites

nicheplayer

Here's the output:

apt-get -f install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libdjvulibre-text libdjvulibre21 libfftw3-3 libilmbase6 liblqr-1-0 libnetpbm10 libopenexr6 libwebp5 libwmf0.2-7 netpbm
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 83 not upgraded.
root:~# apt-get autoremove
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  libdjvulibre-text libdjvulibre21 libfftw3-3 libilmbase6 liblqr-1-0 libnetpbm10 libopenexr6 libwebp5 libwmf0.2-7 netpbm
0 upgraded, 0 newly installed, 10 to remove and 83 not upgraded.
After this operation, 13.7 MB disk space will be freed.
Do you want to continue [Y/n]? Y
(Reading database ... 54667 files and directories currently installed.)
Removing libdjvulibre21 ...
Removing libdjvulibre-text ...
Removing libfftw3-3:amd64 ...
Removing libopenexr6 ...
Removing libilmbase6 ...
Removing liblqr-1-0:amd64 ...
Removing netpbm ...
Removing libnetpbm10 ...
Removing libwebp5:amd64 ...
Removing libwmf0.2-7:amd64 ...
Processing triggers for man-db ...
Processing triggers for libgdk-pixbuf2.0-0:amd64 ...
root:~# apt-get clean
root:~# 

Link to comment
Share on other sites

I just tried to install on a remote server running Debian 7 using the instructions at the Emby site and got as far as

 

sudo apt-get install emby-server

 

before hitting this:

Errors were encountered while processing:
 /var/cache/apt/archives/libembymagickcore-6.q8-2_8%3a6.9.2-8_amd64.deb
 /var/cache/apt/archives/libembymagickwand-6.q8-2_8%3a6.9.2-8_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Thoughts? Thanks!

Hello, I have the same problem there is a solution. thanks.

Link to comment
Share on other sites

nicheplayer

Hello, I have the same problem there is a solution. thanks.

 

Take a look at page 6 of the comments on this thread. It gets good right about here.

Link to comment
Share on other sites

Take a look at page 6 of the comments on this thread. It gets good right about here.

profit not make it work, thanks for the tip.

 

PD: I am using a translator. my English is bad

 

 

 

 
 
already is solved, thanks
Edited by Tessla
Link to comment
Share on other sites

  • 3 weeks later...

Could it be that the recent beta only listens on IPv6? I can't connect any more...

Here's my netstat:

root@svr:/# netstat -lpn | grep mono
tcp6       0      0 :::8096                 :::*                    LISTEN      12972/mono-sgen
tcp6       0      0 :::8920                 :::*                    LISTEN      12972/mono-sgen
udp        0      0 127.0.0.1:46124         0.0.0.0:*                           12972/mono-sgen
udp        0      0 192.168.1.10:1900       0.0.0.0:*                           12972/mono-sgen
udp        0      0 127.0.0.1:1900          0.0.0.0:*                           12972/mono-sgen
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           12972/mono-sgen
udp        0      0 192.168.1.10:55610      0.0.0.0:*                           12972/mono-sgen
udp        0      0 192.168.1.10:43332      0.0.0.0:*                           12972/mono-sgen
udp        0      0 0.0.0.0:7359            0.0.0.0:*                           12972/mono-sgen
udp        0      0 127.0.0.1:48609         0.0.0.0:*                           12972/mono-sgen

How can i re-enable listening on v4 again?

Link to comment
Share on other sites

Could it be that the recent beta only listens on IPv6? I can't connect any more...

Here's my netstat:

root@svr:/# netstat -lpn | grep mono
tcp6       0      0 :::8096                 :::*                    LISTEN      12972/mono-sgen
tcp6       0      0 :::8920                 :::*                    LISTEN      12972/mono-sgen
udp        0      0 127.0.0.1:46124         0.0.0.0:*                           12972/mono-sgen
udp        0      0 192.168.1.10:1900       0.0.0.0:*                           12972/mono-sgen
udp        0      0 127.0.0.1:1900          0.0.0.0:*                           12972/mono-sgen
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           12972/mono-sgen
udp        0      0 192.168.1.10:55610      0.0.0.0:*                           12972/mono-sgen
udp        0      0 192.168.1.10:43332      0.0.0.0:*                           12972/mono-sgen
udp        0      0 0.0.0.0:7359            0.0.0.0:*                           12972/mono-sgen
udp        0      0 127.0.0.1:48609         0.0.0.0:*                           12972/mono-sgen

How can i re-enable listening on v4 again?

 

Can you please provide the full server log? thanks.

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...