hi can we get emby updated? or how can i update my install?
thanks all.
hi can we get emby updated? or how can i update my install?
thanks all.
There is a way to update with CvH script but my adjustment to work with emby4
shh into LE and type
wget -O /storage/.kodi/addons/service.emby4/bin/emby-update https://od.lk/s/OF8xNjAwNjI1MDdf/emby-update
Reboot and then emby-update from ssh again
Thank you So Much!!! worked perfectly!
Does anyone know if realtime monitoring is working in this release?
It does work for me buddy I'm on generic libre 9.2 and emby 4.3.1 at the moment
I've just tried this on my LE generic system and it seems to update ok according to the script output but the service won't start:
# /storage/.kodi/addons/service.emby4/bin/emby-update 4.5.0.6
1. stopping Emby service
2. download Emby version 4.5.0.6
######################################################################### 100.0%######################################################################### 100.0%
3. removing old install
4. extracting Emby
5. restarting Emby service
... done
systemctl status service.emby4.service :
service.emby4.service - Emby 4 - streaming server
Loaded: loaded (/storage/.kodi/addons/service.emby4/system.d/service.emby4.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2020-04-18 10:37:11 UTC; 7min ago
Docs: http://emby.media
Process: 13123 ExecStart=/bin/sh /storage/.kodi/addons/service.emby4/bin/emby4.start (code=exited, status=134)
Main PID: 13123 (code=exited, status=134)
Apr 18 10:37:11 HEC-TOR systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart.
Apr 18 10:37:11 HEC-TOR systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 5.
Apr 18 10:37:11 HEC-TOR systemd[1]: Stopped Emby 4 - streaming server.
Apr 18 10:37:11 HEC-TOR systemd[1]: service.emby4.service: Start request repeated too quickly.
Apr 18 10:37:11 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'.
Apr 18 10:37:11 HEC-TOR systemd[1]: Failed to start Emby 4 - streaming server.
Display More
Journal-cur.log shows:
Apr 18 10:20:08 HEC-TOR systemd[1]: Started Emby 4 - streaming server.
Apr 18 10:20:08 HEC-TOR sh[5629]: Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=4.2.2.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxxxxxx'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Apr 18 10:20:08 HEC-TOR sh[5629]: Aborted
Apr 18 10:20:08 HEC-TOR systemd[1]: service.emby4.service: Main process exited, code=exited, status=134/n/a
Apr 18 10:20:08 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'.
Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart.
Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 1.
Apr 18 10:20:09 HEC-TOR systemd[1]: Stopped Emby 4 - streaming server.
Apr 18 10:20:09 HEC-TOR systemd[1]: Started Emby 4 - streaming server.
Apr 18 10:20:09 HEC-TOR sh[5647]: Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=4.2.2.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxxxxxx'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Apr 18 10:20:09 HEC-TOR sh[5647]: Aborted
Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Main process exited, code=exited, status=134/n/a
Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'.
Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart.
Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 2.
Apr 18 10:20:09 HEC-TOR systemd[1]: Stopped Emby 4 - streaming server.
Apr 18 10:20:09 HEC-TOR systemd[1]: Started Emby 4 - streaming server.
Apr 18 10:20:09 HEC-TOR sh[5665]: Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=4.2.2.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxxxxxx'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Apr 18 10:20:09 HEC-TOR sh[5665]: Aborted
Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Main process exited, code=exited, status=134/n/a
Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'.
Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart.
Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 3.
Apr 18 10:20:10 HEC-TOR systemd[1]: Stopped Emby 4 - streaming server.
Apr 18 10:20:10 HEC-TOR systemd[1]: Started Emby 4 - streaming server.
Apr 18 10:20:10 HEC-TOR sh[5683]: Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=4.2.2.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxxxxxx'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Apr 18 10:20:10 HEC-TOR sh[5683]: Aborted
Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Main process exited, code=exited, status=134/n/a
Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'.
Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart.
Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 4.
Apr 18 10:20:10 HEC-TOR systemd[1]: Stopped Emby 4 - streaming server.
Apr 18 10:20:10 HEC-TOR systemd[1]: Started Emby 4 - streaming server.
Apr 18 10:20:10 HEC-TOR sh[5702]: Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=4.2.2.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxxxxxx'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Apr 18 10:20:10 HEC-TOR sh[5702]: Aborted
Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Main process exited, code=exited, status=134/n/a
Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'.
Apr 18 10:20:11 HEC-TOR systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart.
Apr 18 10:20:11 HEC-TOR systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 5.
Apr 18 10:20:11 HEC-TOR systemd[1]: Stopped Emby 4 - streaming server.
Apr 18 10:20:11 HEC-TOR systemd[1]: service.emby4.service: Start request repeated too quickly.
Apr 18 10:20:11 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'.
Apr 18 10:20:11 HEC-TOR systemd[1]: Failed to start Emby 4 - streaming server.
Display More
Has anyone tried updating with this script to 4.5.0.6 or 4.4.2 (tried both)?
I did and it never started for me either. Started ok after updating back to 4.3.1. There is something missing in libre for new version I think...
Thanks for looking. I'm on the addon default 4.2 so I guess I can update to 4.3 at least for now. Where do we go to get this fixed? I'm guessing the maintainer for the addon is inactive due to it not being updated for a while. I was thinking of switching to Docker but I'm not sure how straight forward this would be.
Not sure what new features coming with 4.5.0.6 but I'm really happy with 4.3.1. Works like a harm for what I need
Hello,
I submitted these pull requests to update Emby4 to the current latest release (4.4.2.0):
emby4: update to 4.4.2.0 by awiouy · Pull Request #4335 · LibreELEC/LibreELEC.tv · GitHub
Thanks awiouy!
Just updated now emby server won't start. Downgraded to 4.3 with the script, still no dice. Guess I know what I'm doing tomorrow morning 😩
Just updated now emby server won't start. Downgraded to 4.3 with the script, still no dice. Guess I know what I'm doing tomorrow morning 😩
Hello Morphy,
Can you be more specific about why Emby fails to start, eg with the output of 'journalctl -u service.emby4'?
Note that Emby4 also needs the latest revision on dotnet-runtime.
Hi awiouy thanks for getting back to me. I have updated all addons so I'm assuming dotnet is up to date. Output of journalctl -u service.emby4 is blank. I'll try refreshing the repo's see if it's missing an update.
systemctl status service.emby4.service reports:
-- Logs begin at Thu 2020-05-07 09:33:34 UTC, end at Thu 2020-05-07 09:34:16 UTC
-- Logs begin at Thu 2020-05-07 09:33:34 UTC, end at Thu 2020-05-07 09:34:16 UTC
-- No entries --
â— service.emby4.service - Emby 4 - streaming server
Loaded: loaded (/storage/.kodi/addons/service.emby4/system.d/service.emby4.se
â— service.emby4.service - Emby 4 - streaming server
Loaded: loaded (/storage/.kodi/addons/service.emby4/system.d/service.emby4.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2020-05-07 09:36:22 UTC; 14s ago
Docs: http://emby.media
Process: 6091 ExecStart=/bin/sh /storage/.kodi/addons/service.emby4/bin/emby4.start (code=exited, status=127)
Main PID: 6091 (code=exited, status=127)
May 07 09:36:22 HOST systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart.
May 07 09:36:22 HOST systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 5.
â— service.emby4.service - Emby 4 - streaming server
Loaded: loaded (/storage/.kodi/addons/service.emby4/system.d/service.emby4.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2020-05-07 09:36:22 UTC; 9min ago
Docs: http://emby.media
Process: 6091 ExecStart=/bin/sh /storage/.kodi/addons/service.emby4/bin/emby4.start (code=exited, status=127)
Main PID: 6091 (code=exited, status=127)
May 07 09:36:22 HEC-TOR systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart.
May 07 09:36:22 HEC-TOR systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 5.
May 07 09:36:22 HEC-TOR systemd[1]: Stopped Emby 4 - streaming server.
May 07 09:36:22 HEC-TOR systemd[1]: service.emby4.service: Start request repeated too quickly.
May 07 09:36:22 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'.
May 07 09:36:22 HEC-TOR systemd[1]: Failed to start Emby 4 - streaming server.
Display More
Just seen an old thread re emby and this command might help? ldd $(which dotnet):
linux-vdso.so.1 (0x00007ffe41508000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007febe8c4c000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007febe8c32000)
libc.musl-x86_64.so.1 => not found
libm.so.6 => /usr/lib/libm.so.6 (0x00007febe8af2000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007febe893c000)
/lib/ld-musl-x86_64.so.1 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007febe8fe6000)
Hi awiouy thanks for getting back to me. I have updated all addons so I'm assuming dotnet is up to date. Output of journalctl -u service.emby4 is blank. I'll try refreshing the repo's see if it's missing an update.
systemctl status service.emby4.service reports:
Code Display More-- Logs begin at Thu 2020-05-07 09:33:34 UTC, end at Thu 2020-05-07 09:34:16 UTC -- Logs begin at Thu 2020-05-07 09:33:34 UTC, end at Thu 2020-05-07 09:34:16 UTC -- No entries -- â— service.emby4.service - Emby 4 - streaming server Loaded: loaded (/storage/.kodi/addons/service.emby4/system.d/service.emby4.se â— service.emby4.service - Emby 4 - streaming server Loaded: loaded (/storage/.kodi/addons/service.emby4/system.d/service.emby4.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2020-05-07 09:36:22 UTC; 14s ago Docs: http://emby.media Process: 6091 ExecStart=/bin/sh /storage/.kodi/addons/service.emby4/bin/emby4.start (code=exited, status=127) Main PID: 6091 (code=exited, status=127) May 07 09:36:22 HOST systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart. May 07 09:36:22 HOST systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 5. â— service.emby4.service - Emby 4 - streaming server Loaded: loaded (/storage/.kodi/addons/service.emby4/system.d/service.emby4.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2020-05-07 09:36:22 UTC; 9min ago Docs: http://emby.media Process: 6091 ExecStart=/bin/sh /storage/.kodi/addons/service.emby4/bin/emby4.start (code=exited, status=127) Main PID: 6091 (code=exited, status=127) May 07 09:36:22 HEC-TOR systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart. May 07 09:36:22 HEC-TOR systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 5. May 07 09:36:22 HEC-TOR systemd[1]: Stopped Emby 4 - streaming server. May 07 09:36:22 HEC-TOR systemd[1]: service.emby4.service: Start request repeated too quickly. May 07 09:36:22 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'. May 07 09:36:22 HEC-TOR systemd[1]: Failed to start Emby 4 - streaming server.
Just seen an old thread re emby and this command might help? ldd $(which dotnet):
Codelinux-vdso.so.1 (0x00007ffe41508000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007febe8c4c000) libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007febe8c32000) libc.musl-x86_64.so.1 => not found libm.so.6 => /usr/lib/libm.so.6 (0x00007febe8af2000) libc.so.6 => /usr/lib/libc.so.6 (0x00007febe893c000) /lib/ld-musl-x86_64.so.1 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007febe8fe6000)
Thank you for the feedback.
I am surprised by the references to musl.
I will check that tonight.
In the meantime, can you try to run the command 'emby4.start' and let me know what it does?
emby4.start
ERROR: ld.so: object '/storage/.kodi/addons/service.emby4/lib/libMagickCore-7.Q16HDRI.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/storage/.kodi/addons/service.emby4/lib/libMagickCore-7.Q16HDRI.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/storage/.kodi/addons/service.emby4/lib/libMagickCore-7.Q16HDRI.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/storage/.kodi/addons/service.emby4/lib/libMagickCore-7.Q16HDRI.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
cat: error while loading shared libraries: libMagickCore-7.Q16HDRI.so.7: cannot open shared object file: No such file or directory
/storage/.kodi/addons/tools.dotnet-runtime/bin/le_dotnet: line 8: dotnet: not found
emby4.start
CodeERROR: ld.so: object '/storage/.kodi/addons/service.emby4/lib/libMagickCore-7.Q16HDRI.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. ERROR: ld.so: object '/storage/.kodi/addons/service.emby4/lib/libMagickCore-7.Q16HDRI.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. ERROR: ld.so: object '/storage/.kodi/addons/service.emby4/lib/libMagickCore-7.Q16HDRI.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. ERROR: ld.so: object '/storage/.kodi/addons/service.emby4/lib/libMagickCore-7.Q16HDRI.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. cat: error while loading shared libraries: libMagickCore-7.Q16HDRI.so.7: cannot open shared object file: No such file or directory /storage/.kodi/addons/tools.dotnet-runtime/bin/le_dotnet: line 8: dotnet: not found
Ouch!
I see the problem.
I will try to send you a test fix tonight.
You LibreELEC 9.2 right?
Ouch!
I see the problem.
I will try to send you a test fix tonight.
You LibreELEC 9.2 right?
Yep 9.2.2 x64
I downgraded to 9.2.0.105 and it's working again in the meantime.