Failed to create CoreCLR, HRESULT: 0x80004005

[solidsnakex37 42]

A few weeks ago I installed 4.8 beta alongside my main 4.7 instance. 

Using Unraid 6.12.6
Docker - Official Emby Docker image

The beta image install, any time I restart it will often return these errors and I can't get it to start up. 

I delete the image, reinstall and it doesn't help. 

I will just try throughout the day to start the container and eventually, it works. 

There are no Emby logs being generated in appdata when this happens, the only logs I have are the below. 

The following logs are from the Docker container: 

 

s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Info App: Entry point completed: Emby.Server.Implementations.Udp.UdpServerEntryPoint. Duration: 0.0005473 seconds
Info App: Starting entry point Emby.Server.Implementations.Playlists.PlaylistUpgradeEntryPoint
Info ServerConfigurationManager: Saving system configuration
Info App: Entry point completed: Emby.Server.Implementations.Playlists.PlaylistUpgradeEntryPoint. Duration: 0.0015989 seconds
Info App: Setting default culture to en-US
Info App: Starting entry point Emby.Server.Implementations.Library.DeviceAccessEntryPoint
Info App: Entry point completed: Emby.Server.Implementations.Library.DeviceAccessEntryPoint. Duration: 0.0002085 seconds
Info App: Starting entry point Emby.Server.Implementations.IO.LibraryMonitorStartup
Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.0027433 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint. Duration: 0.0002714 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.KeepServerAwake
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.KeepServerAwake. Duration: 6.73E-05 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier. Duration: 0.0005629 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.0012568 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 0.000133 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 0.0001923 seconds
Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier
Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 4.76E-05 seconds
Info App: Starting entry point Emby.Server.Implementations.Channels.ChannelsEntryPoint
Info App: Entry point completed: Emby.Server.Implementations.Channels.ChannelsEntryPoint. Duration: 0.001686 seconds
Info App: Starting entry point Emby.LiveTV.EntryPoint
Info LiveTV: Loading live tv data from /config/data/livetv/timers
Info App: Entry point completed: Emby.LiveTV.EntryPoint. Duration: 0.0013308 seconds
Info App: Starting entry point Emby.LiveTV.RecordingNotifier
Info App: Entry point completed: Emby.LiveTV.RecordingNotifier. Duration: 0.0010672 seconds
Info App: Starting entry point Emby.ActivityLog.ActivityLogEntryPoint
Info App: Entry point completed: Emby.ActivityLog.ActivityLogEntryPoint. Duration: 0.0014785 seconds
Info App: Starting entry point Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint
Info App: Entry point completed: Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint. Duration: 0.0005445 seconds
Info App: Starting entry point Emby.Notifications.NotificationManagerEntryPoint
Info Notifications: Registering event nofitier Emby Server User Notifications
Info App: Entry point completed: Emby.Notifications.NotificationManagerEntryPoint. Duration: 0.0070618 seconds
Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0008387 seconds
Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint
Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 4.03E-05 seconds
Info App: All entry points have started
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

[jaycedk 398]

Did your set it up with sepret names, folders and port ?

[solidsnakex37 42]

Just now, jaycedk said:

Did your set it up with sepret names, folders and port ?

The containers are setup with different names, different app folder names etc, as well as ports. The Emby beta install will work, just won't start at certain times, not sure what is it. 

When you say folders, everything is different, but they both point to the same media folders. 

[Luke 37251]

Perhaps it's getting a kill signal coming from the outside? That could be stopping it from starting up.

[solidsnakex37 42]

Hmm, outside meaning? 

I can't figure this out, only thing I haven't tried is using LinuxServers image or something other than the emby official one. 
 

[Luke 37251]

Meaning something on the system could be sending the server a shutdown signal, which the server will respond to and shutdown.

[solidsnakex37 42]

The only thing I could find from a system log level is this, any time I try and start the container. 


Feb  6 14:22:36 FoxDie kernel: docker0: port 11(veth882f23d) entered blocking state
Feb  6 14:22:36 FoxDie kernel: docker0: port 11(veth882f23d) entered disabled state
Feb  6 14:22:36 FoxDie kernel: device veth882f23d entered promiscuous mode
Feb  6 14:22:36 FoxDie kernel: docker0: port 11(veth882f23d) entered blocking state
Feb  6 14:22:36 FoxDie kernel: docker0: port 11(veth882f23d) entered forwarding state
Feb  6 14:22:36 FoxDie kernel: docker0: port 11(veth882f23d) entered disabled state
Feb  6 14:22:37 FoxDie kernel: eth0: renamed from veth2d5dd8e
Feb  6 14:22:37 FoxDie kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth882f23d: link becomes ready
Feb  6 14:22:37 FoxDie kernel: docker0: port 11(veth882f23d) entered blocking state
Feb  6 14:22:37 FoxDie kernel: docker0: port 11(veth882f23d) entered forwarding state

I will keep toying around, would appreciate any suggestions in the meantime

[jaycedk 398]

are you using the same trancoding dir in both instances ?

[solidsnakex37 42]

1 hour ago, jaycedk said:

are you using the same trancoding dir in both instances ?

I am using the same root directory but different folders

[solidsnakex37 42]

11 hours ago, jaycedk said:

are you using the same trancoding dir in both instances ?

Weird...something with that directory Emby didn't like 

My transcode paths: 
/mnt/user/transcode - Main Emby Server

/mnt/user/transcode/embybeta - Beta Server 

That caused the beta not to start

Created a new share /mnt/user/embybetatmp for transcodes and this works now

[jaycedk 398]

12 hours ago, jaycedk said:

are you using the same trancoding dir in both instances ?

Like I asked about.

Good you got it running