Jump to content

Crash from Emby server on unraid


Recommended Posts

Posted

Emby have crash for no reason i have paste the log from unraid and include logs from emby. 

 

Info Server: http/1.0 GET http://proxy2.speedinfo.ca/emby/videos/374766/hls1/main/351.ts?DeviceId=F692747C-7F9B-46C7-B357-E49E6AEBEC4E&MediaSourceId=0fe3bcf1c8e636141e27738d2f3a1ac7&PlaySessionId=312c195134444edc8403d9ad49999816&VideoCodec=h264,hevc,mpeg2video&AudioCodec=ac3,mp3,aac&VideoBitrate=1116000&AudioBitrate=384000&AudioStreamIndex=2&TranscodingMaxAudioChannels=6&SegmentContainer=ts&SegmentLength=3&MinSegments=1&BreakOnNonKeyFrames=True&hevc-profile=Main,Main10&TranscodeReasons=ContainerBitrateExceedsLimit. Cache-Control=no-cache, Connection=close, Pragma=no-cache, Accept=*/*, Accept-Encoding=*/*, Host=proxy2.speedinfo.ca, User-Agent=libmpv, X-Real-IP=184.144.158.228, X-Forwarded-Proto=http, X-Forwarded-For=184.144.158.228, X-Forwarded-Host=184.144.158.228, Icy-MetaData=1
Info Server: http/1.0 Response 200 to 184.144.158.228. Time: 115ms. http://proxy2.speedinfo.ca/emby/videos/374766/hls1/main/351.ts?DeviceId=F692747C-7F9B-46C7-B357-E49E6AEBEC4E&MediaSourceId=0fe3bcf1c8e636141e27738d2f3a1ac7&PlaySessionId=312c195134444edc8403d9ad49999816&VideoCodec=h264,hevc,mpeg2video&AudioCodec=ac3,mp3,aac&VideoBitrate=1116000&AudioBitrate=384000&AudioStreamIndex=2&TranscodingMaxAudioChannels=6&SegmentContainer=ts&SegmentLength=3&MinSegments=1&BreakOnNonKeyFrames=True&hevc-profile=Main,Main10&TranscodeReasons=ContainerBitrateExceedsLimit
Info Server: http/1.0 GET http://proxy2.speedinfo.ca/emby/videos/374766/hls1/main/352.ts?DeviceId=F692747C-7F9B-46C7-B357-E49E6AEBEC4E&MediaSourceId=0fe3bcf1c8e636141e27738d2f3a1ac7&PlaySessionId=312c195134444edc8403d9ad49999816&VideoCodec=h264,hevc,mpeg2video&AudioCodec=ac3,mp3,aac&VideoBitrate=1116000&AudioBitrate=384000&AudioStreamIndex=2&TranscodingMaxAudioChannels=6&SegmentContainer=ts&SegmentLength=3&MinSegments=1&BreakOnNonKeyFrames=True&hevc-profile=Main,Main10&TranscodeReasons=ContainerBitrateExceedsLimit. Cache-Control=no-cache, Connection=close, Pragma=no-cache, Accept=*/*, Accept-Encoding=*/*, Host=proxy2.speedinfo.ca, User-Agent=libmpv, X-Real-IP=184.144.158.228, X-Forwarded-Proto=http, X-Forwarded-For=184.144.158.228, X-Forwarded-Host=184.144.158.228, Icy-MetaData=1
Info Server: http/1.0 Response 200 to 184.144.158.228. Time: 18ms. http://proxy2.speedinfo.ca/emby/videos/374766/hls1/main/352.ts?DeviceId=F692747C-7F9B-46C7-B357-E49E6AEBEC4E&MediaSourceId=0fe3bcf1c8e636141e27738d2f3a1ac7&PlaySessionId=312c195134444edc8403d9ad49999816&VideoCodec=h264,hevc,mpeg2video&AudioCodec=ac3,mp3,aac&VideoBitrate=1116000&AudioBitrate=384000&AudioStreamIndex=2&TranscodingMaxAudioChannels=6&SegmentContainer=ts&SegmentLength=3&MinSegments=1&BreakOnNonKeyFrames=True&hevc-profile=Main,Main10&TranscodeReasons=ContainerBitrateExceedsLimit
Info App: Entry point completed: Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint. Duration: 450.9447781 seconds
Info App: Starting entry point Emby.Notifications.Notifications
Info App: Entry point completed: Emby.Notifications.Notifications. Duration: 0.0002946 seconds
Info App: Starting entry point Emby.Server.Sync.SyncManagerEntryPoint
Info App: SyncRepository Initialize taking write lock
Info App: SyncRepository Initialize write lock taken
Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.0029669 seconds
Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0011261 seconds
Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint
Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 5.53E-05 seconds
Info App: All entry points have started
UnhandledException
System.InvalidOperationException: System.InvalidOperationException: Cannot process request because the process (338) has exited.
at System.Diagnostics.Process.ThrowIfExited(Boolean refresh)
at System.Diagnostics.Process.EnsureState(State state)
at System.Diagnostics.Process.GetStat()
at System.Diagnostics.Process.get_StartTimeCore()
at System.Diagnostics.Process.get_StartTime()
at Emby.ProcessRun.CoreProcess.CoreProcessLocal.get_StartTime()
at Emby.ProcessRun.Extensions.ProcessCpuMonitor.TimerCallback(Object state)
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
at System.Threading.TimerQueueTimer.CallCallback(Boolean isThreadPool)
at System.Threading.TimerQueueTimer.Fire(Boolean isThreadPool)
at System.Threading.ThreadPoolWorkQueue.Dispatch()
Source: System.Diagnostics.Process
TargetSite: Void ThrowIfExited(Boolean)


s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening
[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.
 

embyserver.txt hardware_detection-63778741426.txt

Posted

Hi, this is resolved for the next release. Thanks.

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