yoyo77yo 13 Posted September 22, 2020 Share Posted September 22, 2020 (edited) hello I can see that there is an update 4.5 on emby but on my synology there is no update of emby Edited September 22, 2020 by yoyo77yo Link to comment Share on other sites More sharing options...
Luke 37009 Posted September 22, 2020 Share Posted September 22, 2020 Hi, the announcement is coming in the morning, but going forward you need to install the update using the process on our download page: https://emby.media/download.html Link to comment Share on other sites More sharing options...
yoyo77yo 13 Posted September 22, 2020 Author Share Posted September 22, 2020 OK thanks but i have a synology DS916+ and i don't know what platform can i choose ? X64 / ARMV8 ? etc... Link to comment Share on other sites More sharing options...
Luke 37009 Posted September 22, 2020 Share Posted September 22, 2020 Try the x64. Link to comment Share on other sites More sharing options...
unisoft 272 Posted September 22, 2020 Share Posted September 22, 2020 (edited) 7 hours ago, Luke said: Try the x64. Did that. Says its installed. Rebooted. Emby won't run now. If I try and run it, it goes to Stopped after a few seconds. Logs say successful, its create a group called "Video" and changed the Emby full name to Emby User and embysvr to emby the path on Synology Emby app where I had put TV Recordings, Transcoding and metadata to reside (via Emby GUI) now has folders for: Fonts root plugins localization data config cache In last version, all the above folders were not in this location. Latest server log: 2020-09-22 15:38:02.001 Error HttpServer: Unable to start Kestrel. *** Error Report *** Version: 4.5.0.50 Command line: /volume1/@appstore/EmbyServer/system/EmbyServer.dll -programdata /volume1/Emby -ffdetect /var/packages/EmbyServer/target/bin/ffdetect -ffmpeg /var/packages/EmbyServer/target/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/bin/ffprobe -nolocalportconfig -updatepackage emby-server-synology_{version}_x86_64.spk Operating system: Linux version 3.10.105 (root@build3) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #25426 SMP Wed Jul 8 03:19:33 CST 2020 Framework: .NET Core 3.1.7 OS/Process: x64/x64 Runtime: volume1/@appstore/EmbyServer/system/System.Private.CoreLib.dll Processor count: 4 Data path: /volume1/Emby Application path: /volume1/@appstore/EmbyServer/system System.IO.IOException: System.IO.IOException: Failed to bind to address https://[::]:8925: address already in use. ---> Microsoft.AspNetCore.Connections.AddressInUseException: Address already in use ---> System.Net.Sockets.SocketException (98): Address already in use at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName) at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind() --- End of inner exception stack trace --- at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind() at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.<>c__DisplayClass21_0`1.<<StartAsync>g__OnBind|0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context) --- End of inner exception stack trace --- at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.BindAsync(AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.AnyIPListenOptions.BindAsync(AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.EndpointsStrategy.BindAsync(AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(IServerAddressesFeature addresses, KestrelServerOptions serverOptions, ILogger logger, Func`2 createBinding) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.StartAsync[TContext](IHttpApplication`1 application, CancellationToken cancellationToken) Source: Microsoft.AspNetCore.Server.Kestrel.Core TargetSite: Void MoveNext() InnerException: Microsoft.AspNetCore.Connections.AddressInUseException: Address already in use Source: Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets TargetSite: Void Bind() at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind() at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.<>c__DisplayClass21_0`1.<<StartAsync>g__OnBind|0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context) InnerException: System.Net.Sockets.SocketException: Address already in use Source: System.Net.Sockets TargetSite: Void UpdateStatusAfterSocketErrorAndThrowException(System.Net.Sockets.SocketError, System.String) at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName) at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind() 2020-09-22 15:38:02.031 Error Main: Error in appHost.Init *** Error Report *** Version: 4.5.0.50 Command line: /volume1/@appstore/EmbyServer/system/EmbyServer.dll -programdata /volume1/Emby -ffdetect /var/packages/EmbyServer/target/bin/ffdetect -ffmpeg /var/packages/EmbyServer/target/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/bin/ffprobe -nolocalportconfig -updatepackage emby-server-synology_{version}_x86_64.spk Operating system: Linux version 3.10.105 (root@build3) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #25426 SMP Wed Jul 8 03:19:33 CST 2020 Framework: .NET Core 3.1.7 OS/Process: x64/x64 Runtime: volume1/@appstore/EmbyServer/system/System.Private.CoreLib.dll Processor count: 4 Data path: /volume1/Emby Application path: /volume1/@appstore/EmbyServer/system System.IO.IOException: System.IO.IOException: Failed to bind to address https://[::]:8925: address already in use. ---> Microsoft.AspNetCore.Connections.AddressInUseException: Address already in use ---> System.Net.Sockets.SocketException (98): Address already in use at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName) at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind() --- End of inner exception stack trace --- at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind() at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.<>c__DisplayClass21_0`1.<<StartAsync>g__OnBind|0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context) --- End of inner exception stack trace --- at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.BindAsync(AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.AnyIPListenOptions.BindAsync(AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.EndpointsStrategy.BindAsync(AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(IServerAddressesFeature addresses, KestrelServerOptions serverOptions, ILogger logger, Func`2 createBinding) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.StartAsync[TContext](IHttpApplication`1 application, CancellationToken cancellationToken) at Microsoft.AspNetCore.Hosting.WebHost.StartAsync(CancellationToken cancellationToken) at Microsoft.AspNetCore.Hosting.WebHost.Start() at Emby.Server.Implementations.HttpServer.KestrelHost.KestrelListener.OnAddPrefixesComplete() at Emby.Server.Implementations.ApplicationHost.Init() at EmbyServer.HostedService.StartAsync(CancellationToken cancellationToken) Source: Microsoft.AspNetCore.Server.Kestrel.Core TargetSite: Void MoveNext() InnerException: Microsoft.AspNetCore.Connections.AddressInUseException: Address already in use Source: Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets TargetSite: Void Bind() at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind() at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.<>c__DisplayClass21_0`1.<<StartAsync>g__OnBind|0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context) InnerException: System.Net.Sockets.SocketException: Address already in use Source: System.Net.Sockets TargetSite: Void UpdateStatusAfterSocketErrorAndThrowException(System.Net.Sockets.SocketError, System.String) at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName) at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind() 2020-09-22 15:38:02.045 Info Main: Shutdown complete Start-stop-status log (fine before update as exit code [0] and running): | init,1 | └─sh,27303 -e /proc/self/fd/9 | └─synopkgctl,27305 stop EmbyServer | └─start-stop-stat,27307 /var/packages/EmbyServer/scripts/start-stop-status stop [2020-09-22 14:10:19 UTC] >> Process [14645] exists. [2020-09-22 14:10:19 UTC] >> Emby Server is running. [2020-09-22 14:10:19 UTC] >> Stopping Emby Server. [2020-09-22 14:10:19 UTC] >> Waiting for daemon status to become [3]. [2020-09-22 14:10:19 UTC] >> Checking status [1/20]. [2020-09-22 14:10:19 UTC] >> Process [14645] exists. [2020-09-22 14:10:19 UTC] >> Emby Server is running. [2020-09-22 14:10:20 UTC] >> Checking status [2/20]. [2020-09-22 14:10:20 UTC] >> Process [14645] does not exist. [2020-09-22 14:10:20 UTC] >> Removed PID file [/var/packages/EmbyServer/target/var/esdaemon.pid]. [2020-09-22 14:10:20 UTC] >> Emby Server is not running. [2020-09-22 14:10:21 UTC] >> Checking status [3/20]. [2020-09-22 14:10:21 UTC] >> PID file [/var/packages/EmbyServer/target/var/esdaemon.pid] does not exist. [2020-09-22 14:10:21 UTC] >> Emby Server is not running. [2020-09-22 14:10:21 UTC] >> Target status is now [3]. [2020-09-22 14:10:21 UTC] >> Emby Server shutdown successfully. [2020-09-22 14:10:21 UTC] >> Exit status is [0]. [2020-09-22 14:10:22 UTC] >> Called by [synoscgi_SYNO.Core.Package_2_list], with action [status]. | init,1 | └─SYNO.Core.Packa,27424 | └─start-stop-stat,27426 /var/packages/EmbyServer/scripts/start-stop-status status [2020-09-22 14:10:23 UTC] >> PID file [/var/packages/EmbyServer/target/var/esdaemon.pid] does not exist. [2020-09-22 14:10:23 UTC] >> Emby Server is not running. [2020-09-22 14:10:23 UTC] >> Exit status is [3]. [2020-09-22 14:10:25 UTC] >> Called by [synoscgi_SYNO.Core.Package_2_list], with action [status]. Edited September 22, 2020 by unisoft Link to comment Share on other sites More sharing options...
Luke 37009 Posted September 22, 2020 Share Posted September 22, 2020 Did you change the emby port numbers away from defaults? Link to comment Share on other sites More sharing options...
unisoft 272 Posted September 22, 2020 Share Posted September 22, 2020 (edited) 9 minutes ago, Luke said: Did you change the emby port numbers away from defaults? 8096 for HTTP NGINX Reverse Proxy for 8925 for HTTPS - Emby default may have been 8920? The cert field was configured for Emby though, but it has the "hnadled by reverse proxy" option set. All the (standard) plugins loaded fine according to the log. No errors in previous version logs. I Only use the NAS for Emby too - no other apps. Should it just crash if port can eb changed in the GUI? surely not? Edited September 22, 2020 by unisoft Link to comment Share on other sites More sharing options...
Luke 37009 Posted September 22, 2020 Share Posted September 22, 2020 Are you sure you didn't set port 8925 in emby as emby's local port? I think you did based on the error message. Looks like a conflict with nginx. The previous version may have just been a little more forgiving of that. Link to comment Share on other sites More sharing options...
unisoft 272 Posted September 22, 2020 Share Posted September 22, 2020 Just now, Luke said: Are you sure you didn't set port 8925 in emby as emby's local port? I think you did based on the error message. Looks like a conflict with nginx. The previous version may have just been a little more forgiving of that. Yes changed my text to reflect. I set 8925 in Emby's GUI. It shouldn't crash though? I have WinSCP setup - I'm not a linux expert (much better on Windows) but is there a file I can amend in Notepad and upload again to cure port issue? Link to comment Share on other sites More sharing options...
Luke 37009 Posted September 22, 2020 Share Posted September 22, 2020 Yes look for emby's system.xml config file and set it back to 8920. Link to comment Share on other sites More sharing options...
unisoft 272 Posted September 22, 2020 Share Posted September 22, 2020 (edited) 6 minutes ago, Luke said: Yes look for emby's system.xml config file and set it back to 8920. Thanks Luke, Working again - Emby now loaded after changing the port to 8920 in system.xml. I take it I can now change back to 8925 again and it would work? It was just during the upgrade it encountered an error and didn't know how to handle? My external stuff like phones etc are configured to use 8925 currently that's all. Most people change the default suggested ports especially for external HTTPS, and you could do this in the Emby app... EDIT: Actually if I use Reverse Proxy I can leave the Emby app settings at 8920 anyway as reverse proxy does it stuff anyway! Edited September 22, 2020 by unisoft Link to comment Share on other sites More sharing options...
Luke 37009 Posted September 22, 2020 Share Posted September 22, 2020 No I would leave it at 8920 since 8925 is your nginx port. To be honest, it's on my to do list to hide the option on Synology anyway, since the port has to be declared in the package manifest, it should be denied permission to any others Link to comment Share on other sites More sharing options...
Sab39 7 Posted September 22, 2020 Share Posted September 22, 2020 Got a problem this morning too... should I open a new thread or post it here... Emby isn't accessible after the update. Shuts itself down with the "kill signal" Link to comment Share on other sites More sharing options...
unisoft 272 Posted September 22, 2020 Share Posted September 22, 2020 2 minutes ago, Luke said: No I would leave it at 8920 since 8925 is your nginx port. To be honest, it's on my to do list to hide the option on Synology anyway, since the port has to be declared in the package manifest, it should be denied permission to any others Ok. Everything else seems to be OK, a little slow to begin with, but think that's the cache validating itself as its been moved. It seems fine after a few minutes of running. I take it that the path on Synology Emby app where I had put TV Recordings, Transcoding to reside (via Emby GUI) now has folders for: Fonts root plugins localization data config cache logs and is to be expected in this upgrade, The Folder was called "Emby" actually that these were moved into? Link to comment Share on other sites More sharing options...
Luke 37009 Posted September 22, 2020 Share Posted September 22, 2020 Some things moved, yes. It's a new install package, we wanted to bring it under the emby user as opposed to embysvr, to make it more consistent with other platforms and easier to troubleshoot. Link to comment Share on other sites More sharing options...
Tzutzu 4 Posted September 23, 2020 Share Posted September 23, 2020 On 22/09/2020 at 09:32, Luke said: Hi, the announcement is coming in the morning, but going forward you need to install the update using the process on our download page: https://emby.media/download.html Hi Luke. One question please! That'll be the standard update procedure for now on? i.e. download the new package and update manually? Or we can make it like until now: "... a new version is available..." in Synology Package Center? Cause until now I was peaceful as I always received an email regarding updating to new versions. Thank you. Link to comment Share on other sites More sharing options...
Luke 37009 Posted September 23, 2020 Share Posted September 23, 2020 Ultimately we are going to be in the official Synology package center, not our own separate one. We are actively working on that, and hopefully it will be there soon. Until that happens you'll have to sideload the install package. 1 Link to comment Share on other sites More sharing options...
Tzutzu 4 Posted September 23, 2020 Share Posted September 23, 2020 Ok, got it! Thank you! Link to comment Share on other sites More sharing options...
Luke 37009 Posted September 28, 2020 Share Posted September 28, 2020 Sorry, one more time. Can you please try downloading the spk from our website and trying to install again? https://emby.media/download Please let us know if this resolves the issue. Thanks ! Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now