Jump to content

sqlite package error before update. CentOS


altramarine
 Share

Go to solution Solved by xenu,

Recommended Posts

altramarine

Good day,

 

CentOS7.2.1511

Emby Server: 3.0.8500.0

 

I ran a yum update today and was greeted by the following error (bottom portion):


Resolving Dependencies
--> Running transaction check
---> Package embymagick.x86_64 0:6.9.5-9.1 will be updated
---> Package embymagick.x86_64 0:6.9.6+6-1.1 will be an update
--> Processing Dependency: libgs.so.9()(64bit) for package: embymagick-6.9.6+6-1.1.x86_64
---> Package embysqlite.x86_64 0:3.15.0-1.1 will be obsoleted
--> Processing Dependency: embysqlite for package: emby-server-3.0.8500-89.1.x86_64
---> Package libembysqlite3-0.x86_64 0:3.15.0+1-6.1 will be obsoleting
--> Running transaction check
---> Package embysqlite.x86_64 0:3.15.0-1.1 will be obsoleted
--> Processing Dependency: embysqlite for package: emby-server-3.0.8500-89.1.x86_64
---> Package ghostscript.x86_64 0:9.07-18.el7 will be installed
--> Processing Dependency: urw-fonts >= 1.1 for package: ghostscript-9.07-18.el7.x86_64
--> Processing Dependency: poppler-data for package: ghostscript-9.07-18.el7.x86_64
--> Processing Dependency: ghostscript-fonts for package: ghostscript-9.07-18.el7.x86_64
--> Processing Dependency: libXt.so.6()(64bit) for package: ghostscript-9.07-18.el7.x86_64
--> Running transaction check
---> Package embysqlite.x86_64 0:3.15.0-1.1 will be obsoleted
--> Processing Dependency: embysqlite for package: emby-server-3.0.8500-89.1.x86_64
---> Package ghostscript-fonts.noarch 0:5.50-32.el7 will be installed
--> Processing Dependency: xorg-x11-font-utils for package: ghostscript-fonts-5.50-32.el7.noarch
---> Package libXt.x86_64 0:1.1.4-6.1.el7 will be installed
---> Package poppler-data.noarch 0:0.4.6-3.el7 will be installed
---> Package urw-fonts.noarch 0:2.4-16.el7 will be installed
--> Running transaction check
---> Package embysqlite.x86_64 0:3.15.0-1.1 will be obsoleted
--> Processing Dependency: embysqlite for package: emby-server-3.0.8500-89.1.x86_64
---> Package xorg-x11-font-utils.x86_64 1:7.5-20.el7 will be installed
--> Processing Dependency: libfontenc.so.1()(64bit) for package: 1:xorg-x11-font-utils-7.5-20.el7.x86_64
--> Processing Dependency: libXfont.so.1()(64bit) for package: 1:xorg-x11-font-utils-7.5-20.el7.x86_64
--> Running transaction check
---> Package embysqlite.x86_64 0:3.15.0-1.1 will be obsoleted
--> Processing Dependency: embysqlite for package: emby-server-3.0.8500-89.1.x86_64
---> Package libXfont.x86_64 0:1.5.1-2.el7 will be installed
---> Package libfontenc.x86_64 0:1.1.2-3.el7 will be installed
--> Finished Dependency Resolution
Error: Package: emby-server-3.0.8500-89.1.x86_64 (@home_emby)
           Requires: embysqlite
           Removing: embysqlite-3.15.0-1.1.x86_64 (@home_emby)
               embysqlite = 3.15.0-1.1
           Obsoleted By: libembysqlite3-0-3.15.0+1-6.1.x86_64 (home_emby)
               Not found
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

I understand there were some changes recently revolving around sqlite.

How do I go around this correctly?

 

Thank you!

Edited by altramarine
Link to comment
Share on other sites

altramarine

 

You need to refresh your yum cache.

yum clean all
yum makecache

 

Thanks.

I tried that. Unfortunately, the same error comes up.

Link to comment
Share on other sites

hurricanehrndz

Interesting. I ran a test earlier on centos and I didn't encounter this issue. I will run another test.

 

Sent from my ONEPLUS A3000 using Tapatalk

Link to comment
Share on other sites

Just tried it again as a double, triple check, no go:(

 

Please try to provide useful information. Thanks !

Link to comment
Share on other sites

Not sure if my problem is still related to this but I get exit code status 126 now.

 

What exactly gives a 126 exit code status? Thanks !

Link to comment
Share on other sites

What exactly gives a 126 exit code status? Thanks !

Whenever I try to start it.

 

$ sudo systemctl status emby-server.service  emby-server.service - Emby Media Server   Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: disabled)   Active: failed (Result: exit-code) since Wed 2016-11-30 21:51:26 CST; 11s ago  Process: 25336 ExecStopPost=/usr/lib/emby-server/emby-server.sh clear (code=exited, status=0/SUCCESS)  Process: 25319 ExecStart=/usr/lib/emby-server/emby-server.sh start (code=exited, status=126) Main PID: 25319 (code=exited, status=126)Nov 30 21:51:22 server systemd[1]: Started Emby Media Server.Nov 30 21:51:22 server systemd[1]: Starting Emby Media Server...Nov 30 21:51:24 server su[25319]: (to emby) root on noneNov 30 21:51:24 server systemd[1]: emby-server.service: main process ex...aNov 30 21:51:26 server systemd[1]: Unit emby-server.service entered fai....Nov 30 21:51:26 server systemd[1]: emby-server.service failed.Hint: Some lines were ellipsized, use -l to show in full.
Edited by cones
Link to comment
Share on other sites

hurricanehrndz

Whenever I try to start it.

 

$ sudo systemctl status emby-server.service  emby-server.service - Emby Media Server   Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: disabled)   Active: failed (Result: exit-code) since Wed 2016-11-30 21:51:26 CST; 11s ago  Process: 25336 ExecStopPost=/usr/lib/emby-server/emby-server.sh clear (code=exited, status=0/SUCCESS)  Process: 25319 ExecStart=/usr/lib/emby-server/emby-server.sh start (code=exited, status=126) Main PID: 25319 (code=exited, status=126)Nov 30 21:51:22 server systemd[1]: Started Emby Media Server.Nov 30 21:51:22 server systemd[1]: Starting Emby Media Server...Nov 30 21:51:24 server su[25319]: (to emby) root on noneNov 30 21:51:24 server systemd[1]: emby-server.service: main process ex...aNov 30 21:51:26 server systemd[1]: Unit emby-server.service entered fai....Nov 30 21:51:26 server systemd[1]: emby-server.service failed.Hint: Some lines were ellipsized, use -l to show in full.

I'm not sure why you are reporting another error. I think the issue we should focus on is getting libembysqlite3-0 installed on your system or have you been able to achieve this?

 

I have just double checked again on a CentOS machine and the packages and the repos are working correctly.

 

Can you please try downloading the rpm and installing it manually and report back your results.

yumdownloader libembysqlite3-0
rpm --install --force --verbose libembysqlite3-0-3.15.0+1-6.1.x86_64.rpm 
Edited by hurricanehrndz
Link to comment
Share on other sites

I'm not sure why you are reporting another error. I think the issue we should focus on is getting libembysqlite3-0 installed on your system or have you been able to achieve this?

 

I have just double checked again on a CentOS machine and the packages and the repos are working correctly.

 

Can you please try downloading the rpm and installing it manually and report back your results.

 

yumdownloader libembysqlite3-0
rpm --install --force --verbose libembysqlite3-0-3.15.0+1-6.1.x86_64.rpm 

Weird it was already installed but I ran that anyways and now it's working. I reset it though so have to go through that again. Random question I thought ffmpeg was installed with it?

Link to comment
Share on other sites

I had the same dependency resolution error as the OP as of 10 minutes ago even after cleaning yum cache when doing a "yum update".

What worked was doing a "yum -y remove emby-server && yum -y install emby-server"

  • Like 1
Link to comment
Share on other sites

hurricanehrndz

@@xenu well there seems to be an issue with how yum handels obsolescence of packages during upgrades.

 

Thanks for reporting your resolution.

 

Sent from my ONEPLUS A3000 using Tapatalk

Edited by hurricanehrndz
Link to comment
Share on other sites

altramarine

Please try to provide useful information. Thanks !

 

Sorry, I should have been more specific.

I tried below commands several times:

yum clean all
yum makecache

However, yum update gave me the same error as reported in post #1.

Error: Package: emby-server-3.0.8500-89.1.x86_64 (@home_emby)
           Requires: embysqlite
           Removing: embysqlite-3.15.0-1.1.x86_64 (@home_emby)
               embysqlite = 3.15.0-1.1
           Obsoleted By: libembysqlite3-0-3.15.0+1-6.1.x86_64 (home_emby)
               Not found
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

As per @@hurricanehrndz, I downloaded libembysqlite3 manually and tried to install. Here are the results:

[user@host ~]$ rpm --install --force --verbose libembysqlite3-0-3.15.0+1-6.1.x86_64.rpm
error: Failed dependencies:
    embysqlite conflicts with libembysqlite3-0-3.15.0+1-6.1.x86_64
    embysqlite is obsoleted by libembysqlite3-0-3.15.0+1-6.1.x86_64
Edited by altramarine
Link to comment
Share on other sites

altramarine

I did yum update and it gave me the same message:

Error: Package: emby-server-3.0.8500-89.1.x86_64 (@home_emby)
           Requires: embysqlite
           Removing: embysqlite-3.15.0-1.1.x86_64 (@home_emby)
               embysqlite = 3.15.0-1.1
           Obsoleted By: libembysqlite3-0-3.15.0+1-6.1.x86_64 (home_emby)
               Not found
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

I will reinstall emby-server like @@xenu did as it may be related to my install. This way I won't waste more of your precious time.

Edited by altramarine
Link to comment
Share on other sites

altramarine

Darn, sorry guys, I ran into more trouble.

I removed emby-server package, then ran yum update.

That updated mono from emby repo.

Then installed emby-server and restarted.

Here is what i have installed emby related:

[root@host]# yum list installed | grep emby
emby-server.x86_64                    3.0.8500-6.1                   @home_emby
embymagick.x86_64                     6.9.6+6-3.1                    @home_emby
libembysqlite3-0.x86_64               3.15.0+1-6.1                   @home_emby
mono-core.x86_64                      4.6.2.7-1.1                    @home_emby
mono-data.x86_64                      4.6.2.7-1.1                    @home_emby
mono-data-sqlite.x86_64               4.6.2.7-1.1                    @home_emby
mono-extras.x86_64                    4.6.2.7-1.1                    @home_emby
mono-mvc.x86_64                       4.6.2.7-1.1                    @home_emby
mono-wcf.x86_64                       4.6.2.7-1.1                    @home_emby
mono-web.x86_64                       4.6.2.7-1.1                    @home_emby
mono-winforms.x86_64                  4.6.2.7-1.1                    @home_emby
mono-winfxcore.x86_64                 4.6.2.7-1.1                    @home_emby
sqlite.x86_64                         3.8.2-10.1                     @home_emby

systemctl start emby-server failed with:

[root@host lib]# journalctl -xe
Dec 01 23:34:15 host polkitd[862]: Registered Authentication Agent for unix-process:4871:1373362 (system bus name :1.102 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, loca
Dec 01 23:34:15 host systemd[1]: Started Emby Media Server.
-- Subject: Unit emby-server.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit emby-server.service has finished starting up.
--
-- The start-up result is done.
Dec 01 23:34:15 host systemd[1]: Starting Emby Media Server...
-- Subject: Unit emby-server.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit emby-server.service has begun starting up.
Dec 01 23:34:15 host su[4876]: (to emby) root on none
Dec 01 23:34:15 host kernel: SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
Dec 01 23:34:15 host polkitd[862]: Unregistered Authentication Agent for unix-process:4871:1373362 (system bus name :1.102, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Dec 01 23:34:15 host systemd[1]: Created slice user-995.slice.
-- Subject: Unit user-995.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-995.slice has finished starting up.
--
-- The start-up result is done.
Dec 01 23:34:15 host systemd[1]: Starting user-995.slice.
-- Subject: Unit user-995.slice has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-995.slice has begun starting up.
Dec 01 23:34:15 host systemd[1]: Started Session c6 of user emby.
-- Subject: Unit session-c6.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-c6.scope has finished starting up.
--
-- The start-up result is done.
Dec 01 23:34:15 host su[4876]: pam_unix(su:session): session opened for user emby by (uid=0)
Dec 01 23:34:15 host systemd[1]: Starting Session c6 of user emby.
-- Subject: Unit session-c6.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-c6.scope has begun starting up.
Dec 01 23:34:15 host emby-server.sh[4876]: env: /usr/lib/emby-server/lib64/ImageMagick-6.9.5/modules-Q8/filters: Permission denied
Dec 01 23:34:15 host su[4876]: pam_unix(su:session): session closed for user emby
Dec 01 23:34:15 host systemd[1]: emby-server.service: main process exited, code=exited, status=126/n/a
Dec 01 23:34:15 host systemd[1]: Removed slice user-995.slice.
-- Subject: Unit user-995.slice has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-995.slice has finished shutting down.
Dec 01 23:34:15 host systemd[1]: Stopping user-995.slice.
-- Subject: Unit user-995.slice has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-995.slice has begun shutting down.
Dec 01 23:34:15 host systemd[1]: Unit emby-server.service entered failed state.
Dec 01 23:34:15 host systemd[1]: emby-server.service failed.

The filters directory is empty, should it be?

 

I checked the /var/log/emby-server.log but that file hasn't been updated in around 20 minutes so I am not sure this is relevant:

[root@host log]# tail emby-server.log
      NUMBER_OF_BYTES : 52285
      NUMBER_OF_BYTES-eng: 52285
      _STATISTICS_WRITING_APP: mkvmerge v9.5.0 ('Quiet Fire') 64bit
      _STATISTICS_WRITING_APP-eng: mkvmerge v9.5.0 ('Quiet Fire') 64bit
      _STATISTICS_WRITING_DATE_UTC: 2016-12-02 00:13:29
      _STATISTICS_WRITING_DATE_UTC-eng: 2016-12-02 00:13:29
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Edited by altramarine
Link to comment
Share on other sites

> The filters directory is empty, should it be?

Mine isn't empty:

$ sudo ls -lah /usr/lib/emby-server/lib64/ImageMagick-6.9.5/modules-Q8/filters/
total 40K
drwxr-xr-x. 2 root root   40 Oct 13 00:32 .
drwxr-xr-x. 4 root root   33 Oct 13 00:32 ..
-rwxr-xr-x. 1 root root 1.1K Aug 23 19:39 analyze.la
-rwxr-xr-x. 1 root root  34K Aug 23 19:39 analyze.so
edit:

I noticed I had some older packages installed:

$ sudo yum list installed | grep emby
emby-server.x86_64                    3.0.8500-6.1                    @home_emby
embymagick.x86_64                     6.9.5-9.1                       @home_emby
libembysqlite3-0.x86_64               3.15.0+1-6.1                    @home_emby
mono-core.x86_64                      4.6.1.5-1.1                     @home_emby
mono-data.x86_64                      4.6.1.5-1.1                     @home_emby
mono-data-sqlite.x86_64               4.6.1.5-1.1                     @home_emby
mono-extras.x86_64                    4.6.1.5-1.1                     @home_emby
mono-mvc.x86_64                       4.6.1.5-1.1                     @home_emby
mono-wcf.x86_64                       4.6.1.5-1.1                     @home_emby
mono-web.x86_64                       4.6.1.5-1.1                     @home_emby
mono-winforms.x86_64                  4.6.1.5-1.1                     @home_emby
mono-winfxcore.x86_64                 4.6.1.5-1.1                     @home_emby
After updating to the version as you have installed, I get the same errror when starting emby-server service & empty filters folder. Edited by xenu
Link to comment
Share on other sites

hurricanehrndz

The version of embymagick is wrong. The folder should be called embymagick not imagmagick. Can you remove all packages and delete /usr/lib/emby-server also check journalctl for the most recent logs instead or /var/lib/emby-server

 

Sent from my ONEPLUS A3000 using Tapatalk

Link to comment
Share on other sites

hurricanehrndz

Guys,

 

I also wanted to add my appreciation for you contributions to the project. I personally very thankful and grateful that both of you are giving your time and effort. I'm really sorry you have encountered these issues. If we can get them resolved, hopefully less users will experience similar issues. Emby wouldn't be as good of project if it wasn't for users like yourselves.

  • Like 1
Link to comment
Share on other sites

  • Solution

Glad to help.

 

I think I found the issue:

 

When I updated from "embymagick-6.9.5-9.1.x86_64" to "embymagick-6.9.6+6-3.1.x86_64" the old folder at "/usr/lib/emby-server/lib64/ImageMagick-6.9.5" didn't get deleted.

Now the emby startup script at "/usr/lib/emby-server/emby-server.sh" searches for the filter path here:

EMBY_LIBRARY_PATH=$(find /usr/lib/emby-server/ -maxdepth 1 -mindepth 1 -type d| grep -v bin | grep -v etc | grep -v -e "/\.")
MAGICK_CODER_FILTER_PATH_ENV="MAGICK_CODER_FILTER_PATH=$(find ${EMBY_LIBRARY_PATH} -type d -name "filters")"
Since the old folder is still present this results in:

/usr/lib/emby-server/lib64/ImageMagick-6.9.5/modules-Q8/filters
/usr/lib/emby-server/lib64/EmbyMagick-6.9.6/modules-Q8/filters
and picks the "wrong" folder.

 

Manually removing the old folder ("sudo rm -r /usr/lib/emby-server/lib64/ImageMagick-6.9.5/") and restarting emby-server solved the issue.

 

Edit: And thanks for all your work on emby :)

Edited by xenu
  • Like 1
Link to comment
Share on other sites

hurricanehrndz

Glad to help.

 

I think I found the issue:

 

When I updated from "embymagick-6.9.5-9.1.x86_64" to "embymagick-6.9.6+6-3.1.x86_64" the old folder at "/usr/lib/emby-server/lib64/ImageMagick-6.9.5" didn't get deleted.

Now the emby startup script at "/usr/lib/emby-server/emby-server.sh" searches for the filter path here:

EMBY_LIBRARY_PATH=$(find /usr/lib/emby-server/ -maxdepth 1 -mindepth 1 -type d| grep -v bin | grep -v etc | grep -v -e "/\.")
MAGICK_CODER_FILTER_PATH_ENV="MAGICK_CODER_FILTER_PATH=$(find ${EMBY_LIBRARY_PATH} -type d -name "filters")"
Since the old folder is still present this results in:

/usr/lib/emby-server/lib64/ImageMagick-6.9.5/modules-Q8/filters
/usr/lib/emby-server/lib64/EmbyMagick-6.9.6/modules-Q8/filters
and picks the "wrong" folder.

 

Manually removing the old folder ("sudo rm -r /usr/lib/emby-server/lib64/ImageMagick-6.9.5/") and restarting emby-server solved the issue.

 

Edit: And thanks for all your work on emby :)

 

Yup I suspected as much. I have made some small minor changes to the packages for any user experiencing issues. If we can get this tested and worked out I will commit the changes to the main repo:

The repo with the fixes can be found on here:

https://software.opensuse.org/download.html?project=home%3Ahurricanehernandez%3Aemby-server&package=emby-server

 

Please temporarily disable the emby main repo.

 

Currently the fixes are building. Thank you again. Please report back with the results. This should also fix the need to having to uninstall emby before being able to upgrade.

Edited by hurricanehrndz
  • Like 1
Link to comment
Share on other sites

altramarine

Man, i feel like this isn't my couple of days. I should have read @@xeno's last reply.

I went ahead and deleted emby-server related packages and the /usr/lib/emby-server directory.

I then reinstalled emby-server from repo and now /usr/lib/emby-server  is empty.

How badly did I butcher it?

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
 Share

×
×
  • Create New...