razzfazz 11 Posted January 20, 2018 Share Posted January 20, 2018 (edited) Hi all, The FreeBSD port for Emby recently got updated to version 3.2.70, and ever since it seems to crash immediately whenever I try to connect to it via http or https, leaving an "unhandled_[...].txt" file in the logs directory with the following contents: System.Net.Sockets.SocketException (0x80004005): Address already in use at System.Net.Sockets.Socket.Bind (System.Net.EndPoint localEP) [0x0004c] in <65d66c5eaa6a48038257422d3c294dab>:0 at Emby.Server.Implementations.Net.UdpSocket..ctor (System.Net.Sockets.Socket socket, System.Int32 localPort, System.Net.IPAddress ip) [0x0006b] in <730a104ef6c8470ebc4f70071ce76249>:0 at Emby.Server.Implementations.Net.SocketFactory.CreateUdpMulticastSocket (System.String ipAddress, System.Int32 multicastTimeToLive, System.Int32 localPort) [0x000ba] in <730a104ef6c8470ebc4f70071ce76249>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>m__1 (System.Object state) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context (System.Object state) [0x0000e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x0002a] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 System.Net.Sockets.SocketException at System.Net.Sockets.Socket.Bind (System.Net.EndPoint localEP) [0x0004c] in <65d66c5eaa6a48038257422d3c294dab>:0 at Emby.Server.Implementations.Net.UdpSocket..ctor (System.Net.Sockets.Socket socket, System.Int32 localPort, System.Net.IPAddress ip) [0x0006b] in <730a104ef6c8470ebc4f70071ce76249>:0 at Emby.Server.Implementations.Net.SocketFactory.CreateUdpMulticastSocket (System.String ipAddress, System.Int32 multicastTimeToLive, System.Int32 localPort) [0x000ba] in <730a104ef6c8470ebc4f70071ce76249>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>m__1 (System.Object state) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context (System.Object state) [0x0000e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x0002a] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 Anyone else seeing this? Edited January 20, 2018 by razzfazz Link to comment Share on other sites More sharing options...
Luke 37113 Posted January 20, 2018 Share Posted January 20, 2018 can you please attach the complete log file? thanks. Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 20, 2018 Author Share Posted January 20, 2018 That was the entire contents of the "unhandled_[...].txt" file; do you mean the regular log file? Link to comment Share on other sites More sharing options...
Luke 37113 Posted January 20, 2018 Share Posted January 20, 2018 the regular log file would be good, thanks. Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 20, 2018 Author Share Posted January 20, 2018 Looks like it's basically the same thing: 2018-01-19 23:03:59.978 Info Main: Emby Command line: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -os freebsd -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server Operating system: Unix 11.1.4.0 64-Bit OS: True 64-Bit Process: True User Interactive: False Mono: 4.8.1 (4.8.1.0 Wed Sep 20 01:18:30 UTC 2017) Processor count: 4 Program data path: /var/db/emby-server Application directory: /usr/local/lib/emby-server 2018-01-19 23:04:00.343 Info App: Application version: 3.2.70.0 2018-01-19 23:04:00.344 Info App: Loading assemblies 2018-01-19 23:04:00.353 Info App: Loading Emby.Kodi.SyncQueue, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading statistics, Version=2.0.2.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading Trakt, Version=3.1.4.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading MediaBrowser.Api, Version=3.2.70.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading MediaBrowser.WebDashboard, Version=3.2.70.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading MediaBrowser.Model, Version=3.2.70.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading MediaBrowser.Common, Version=3.2.70.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading MediaBrowser.Controller, Version=3.2.70.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading MediaBrowser.Providers, Version=3.2.70.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading Emby.Photos, Version=3.2.70.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading Emby.Server.Implementations, Version=3.2.70.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading Emby.Server.MediaEncoding, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading Emby.Dlna, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading MediaBrowser.LocalMetadata, Version=3.2.70.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading MediaBrowser.XbmcMetadata, Version=3.2.70.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading MediaBrowser.Server.Mono, Version=3.2.70.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading Emby.Server.CinemaMode, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading Emby.Server.Connect, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.353 Info App: Loading Emby.Server.Sync, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null 2018-01-19 23:04:00.404 Info SqliteUserRepository: Sqlite version: 3.21.0 2018-01-19 23:04:00.405 Info SqliteUserRepository: Sqlite compiler options: COMPILER=clang-4.0.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS4,ENABLE_RTREE,ENABLE_UNLOCK_NOTIFY,HAVE_ISNAN,SECURE_DELETE,TEMP_STORE=1,THREADSAFE=1,USE_URI 2018-01-19 23:04:00.421 Info SqliteUserRepository: Default journal_mode for /var/db/emby-server/data/users.db is wal 2018-01-19 23:04:00.422 Info SqliteUserRepository: PRAGMA synchronous=1 2018-01-19 23:04:00.428 Info AuthenticationRepository: Default journal_mode for /var/db/emby-server/data/authentication.db is wal 2018-01-19 23:04:00.428 Info AuthenticationRepository: PRAGMA synchronous=1 2018-01-19 23:04:00.488 Info DeviceManager: Default journal_mode for /var/db/emby-server/data/devices.db is wal 2018-01-19 23:04:00.488 Info DeviceManager: PRAGMA synchronous=1 2018-01-19 23:04:00.508 Info ActivityRepository: Default journal_mode for /var/db/emby-server/data/activitylog.db is wal 2018-01-19 23:04:00.508 Info ActivityRepository: PRAGMA synchronous=1 2018-01-19 23:04:00.510 Info SqliteDisplayPreferencesRepository: Default journal_mode for /var/db/emby-server/data/displaypreferences.db is wal 2018-01-19 23:04:00.510 Info SqliteDisplayPreferencesRepository: PRAGMA synchronous=1 2018-01-19 23:04:00.512 Info SqliteItemRepository: Default journal_mode for /var/db/emby-server/data/library.db is wal 2018-01-19 23:04:00.512 Info SqliteItemRepository: PRAGMA synchronous=1 2018-01-19 23:04:00.521 Info SqliteNotificationsRepository: Default journal_mode for /var/db/emby-server/data/notifications.db is wal 2018-01-19 23:04:00.521 Info SqliteNotificationsRepository: PRAGMA synchronous=1 2018-01-19 23:04:00.646 Info App: Emby.Kodi.SyncQueue IS NOW STARTING!!! 2018-01-19 23:04:00.647 Info App: Emby.Kodi.SyncQueue: Creating DB Repository... 2018-01-19 23:04:00.677 Info App: Emby.Kodi.SyncQueue: SyncAPI Created and Listening at "/Emby.Kodi.SyncQueue/{UserID}/{LastUpdateDT}/GetItems?format=json" - {LastUpdateDT} must be a UTC DateTime formatted as yyyy-MM-ddTHH:mm:ssZ 2018-01-19 23:04:00.677 Info App: Emby.Kodi.SyncQueue: SyncAPI Created and Listening at "/Emby.Kodi.SyncQueue/{UserID}/GetItems?LastUpdateDT={LastUpdateDT}&format=json" - {LastUpdateDT} must be a UTC DateTime formatted as yyyy-MM-ddTHH:mm:ssZ 2018-01-19 23:04:00.677 Info App: Emby.Kodi.SyncQueue: The following parameters also exist to filter the results: 2018-01-19 23:04:00.677 Info App: Emby.Kodi.SyncQueue: filter=movies,tvshows,music,musicvideos,boxsets 2018-01-19 23:04:00.677 Info App: Emby.Kodi.SyncQueue: Results will be included by default and only filtered if added to the filter query... 2018-01-19 23:04:00.677 Info App: Emby.Kodi.SyncQueue: the filter query must be lowercase in both the name and the items... 2018-01-19 23:04:00.706 Info HttpServer: Calling ServiceStack AppHost.Init 2018-01-19 23:04:01.017 Info ServerManager: Loading Http Server 2018-01-19 23:04:01.020 Info HttpServer: Adding HttpListener prefix http://+:8096/ 2018-01-19 23:04:01.020 Info HttpServer: Adding HttpListener prefix https://+:8920/ 2018-01-19 23:04:01.124 Info Main: Skia not available. Will try next image processor. libSkiaSharp.so 2018-01-19 23:04:01.127 Info ImageMagick: ImageMagick version: ImageMagick 6.9.9-28 Q8 amd64 2017-12-26 http://www.imagemagick.org 2018-01-19 23:04:01.133 Info App: Emby.Kodi.SyncQueue.Task: Retention Task Scheduled! 2018-01-19 23:04:01.153 Info TaskManager: Daily trigger for Remove Old Sync Data set to fire at 01/20/2018 00:01:00, which is 56.98078835 minutes from now. 2018-01-19 23:04:01.154 Info TaskManager: Daily trigger for Calculate statistics for all users set to fire at 01/20/2018 00:00:00, which is 55.9807601833333 minutes from now. 2018-01-19 23:04:01.158 Info TaskManager: Daily trigger for Chapter image extraction set to fire at 01/20/2018 02:00:00, which is 175.980692566667 minutes from now. 2018-01-19 23:04:01.163 Info TaskManager: Daily trigger for Start new log file set to fire at 01/20/2018 00:00:00, which is 55.9806149666667 minutes from now. 2018-01-19 23:04:01.165 Info MediaEncoder: FFMpeg: /usr/local/bin/ffmpeg 2018-01-19 23:04:01.165 Info MediaEncoder: FFProbe: /usr/local/bin/ffprobe 2018-01-19 23:04:01.166 Info MediaEncoder: Validating media encoder at /usr/local/bin/ffmpeg 2018-01-19 23:04:01.167 Info MediaEncoder: Running /usr/local/bin/ffmpeg -decoders 2018-01-19 23:04:01.244 Info MediaEncoder: Decoder available: mpeg2video 2018-01-19 23:04:01.315 Info MediaEncoder: Decoder available: ac3 2018-01-19 23:04:01.319 Info MediaEncoder: Decoder available: aac 2018-01-19 23:04:01.324 Info MediaEncoder: Decoder available: mp3 2018-01-19 23:04:01.325 Info MediaEncoder: Decoder available: h264 2018-01-19 23:04:01.326 Info MediaEncoder: Decoder available: hevc 2018-01-19 23:04:01.338 Info MediaEncoder: Running /usr/local/bin/ffmpeg -encoders 2018-01-19 23:04:01.406 Info MediaEncoder: Encoder available: libx264 2018-01-19 23:04:01.406 Info MediaEncoder: Encoder available: libx265 2018-01-19 23:04:01.407 Info MediaEncoder: Encoder available: mpeg4 2018-01-19 23:04:01.408 Info MediaEncoder: Encoder available: msmpeg4 2018-01-19 23:04:01.409 Info MediaEncoder: Encoder available: libvpx 2018-01-19 23:04:01.410 Info MediaEncoder: Encoder available: libvpx-vp9 2018-01-19 23:04:01.411 Info MediaEncoder: Encoder available: aac 2018-01-19 23:04:01.413 Info MediaEncoder: Encoder available: libmp3lame 2018-01-19 23:04:01.415 Info MediaEncoder: Encoder available: libopus 2018-01-19 23:04:01.417 Info MediaEncoder: Encoder available: libvorbis 2018-01-19 23:04:01.419 Info MediaEncoder: Encoder available: srt 2018-01-19 23:04:01.442 Info MediaEncoder: Encoder available: ac3 2018-01-19 23:04:01.442 Info MediaEncoder: Encoder validation complete 2018-01-19 23:04:01.443 Info App: ServerId: 81abcaa877f94aad964e93d7bc7e64f6 2018-01-19 23:04:01.443 Info App: Core startup complete 2018-01-19 23:04:01.443 Info App: Post-init migrations complete 2018-01-19 23:04:01.462 Info App: Starting entry point Emby.Kodi.SyncQueue.EntryPoints.LibrarySyncNotification 2018-01-19 23:04:01.462 Info App: Emby.Kodi.SyncQueue: LibrarySyncNotification Startup... 2018-01-19 23:04:01.462 Info App: Entry point completed: Emby.Kodi.SyncQueue.EntryPoints.LibrarySyncNotification. Duration: 0.000751 seconds 2018-01-19 23:04:01.462 Info App: Starting entry point Emby.Kodi.SyncQueue.EntryPoints.UserSyncNotification 2018-01-19 23:04:01.463 Info App: Emby.Kodi.SyncQueue: UserSyncNotification Startup... 2018-01-19 23:04:01.463 Info App: Entry point completed: Emby.Kodi.SyncQueue.EntryPoints.UserSyncNotification. Duration: 0.000278 seconds 2018-01-19 23:04:01.463 Info App: Starting entry point Trakt.ServerMediator 2018-01-19 23:04:01.463 Info App: Entry point completed: Trakt.ServerMediator. Duration: 0.000178 seconds 2018-01-19 23:04:01.463 Info App: Starting entry point MediaBrowser.Api.ApiEntryPoint 2018-01-19 23:04:01.463 Info App: Entry point completed: MediaBrowser.Api.ApiEntryPoint. Duration: 3.2E-05 seconds 2018-01-19 23:04:01.463 Info App: Starting entry point MediaBrowser.WebDashboard.ServerEntryPoint 2018-01-19 23:04:01.464 Info App: Entry point completed: MediaBrowser.WebDashboard.ServerEntryPoint. Duration: 0.000677 seconds 2018-01-19 23:04:01.464 Info App: Starting entry point Emby.Server.Implementations.Activity.ActivityLogEntryPoint 2018-01-19 23:04:01.465 Info App: Entry point completed: Emby.Server.Implementations.Activity.ActivityLogEntryPoint. Duration: 0.001265 seconds 2018-01-19 23:04:01.465 Info App: Starting entry point Emby.Server.Implementations.Channels.ChannelsEntryPoint 2018-01-19 23:04:01.466 Info App: Entry point completed: Emby.Server.Implementations.Channels.ChannelsEntryPoint. Duration: 0.000616 seconds 2018-01-19 23:04:01.466 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint 2018-01-19 23:04:01.466 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint. Duration: 0.000158 seconds 2018-01-19 23:04:01.466 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ExternalPortForwarding 2018-01-19 23:04:01.467 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ExternalPortForwarding. Duration: 0.000203 seconds 2018-01-19 23:04:01.467 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.KeepServerAwake 2018-01-19 23:04:01.467 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.KeepServerAwake. Duration: 0.0001 seconds 2018-01-19 23:04:01.467 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier 2018-01-19 23:04:01.467 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier. Duration: 0.000538 seconds 2018-01-19 23:04:01.467 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LoadRegistrations 2018-01-19 23:04:01.467 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LoadRegistrations. Duration: 0.000116 seconds 2018-01-19 23:04:01.467 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.RecordingNotifier 2018-01-19 23:04:01.468 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.RecordingNotifier. Duration: 0.000516 seconds 2018-01-19 23:04:01.468 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier 2018-01-19 23:04:01.469 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.00101 seconds 2018-01-19 23:04:01.469 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard 2018-01-19 23:04:01.469 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 0.000208 seconds 2018-01-19 23:04:01.469 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents 2018-01-19 23:04:01.469 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 0.000125 seconds 2018-01-19 23:04:01.469 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UdpServerEntryPoint 2018-01-19 23:04:01.473 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UdpServerEntryPoint. Duration: 0.003508 seconds 2018-01-19 23:04:01.473 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UsageEntryPoint 2018-01-19 23:04:01.474 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UsageEntryPoint. Duration: 0.000683 seconds 2018-01-19 23:04:01.474 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier 2018-01-19 23:04:01.474 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 7.5E-05 seconds 2018-01-19 23:04:01.474 Info App: Starting entry point Emby.Server.Implementations.IO.LibraryMonitorStartup 2018-01-19 23:04:01.544 Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.070484 seconds 2018-01-19 23:04:01.544 Info App: Starting entry point Emby.Server.Implementations.LiveTv.EmbyTV.EntryPoint 2018-01-19 23:04:01.547 Info App: Loading live tv data from /var/db/emby-server/data/livetv/timers 2018-01-19 23:04:01.557 Info LibraryMonitor: Watching directory /zdata/media/livetv/emby 2018-01-19 23:04:01.573 Info App: Entry point completed: Emby.Server.Implementations.LiveTv.EmbyTV.EntryPoint. Duration: 0.02873 seconds 2018-01-19 23:04:01.573 Info App: Starting entry point Emby.Server.Implementations.News.NewsEntryPoint 2018-01-19 23:04:01.574 Info App: Entry point completed: Emby.Server.Implementations.News.NewsEntryPoint. Duration: 0.000322 seconds 2018-01-19 23:04:01.574 Info App: Starting entry point Emby.Server.Implementations.Notifications.Notifications 2018-01-19 23:04:01.575 Info App: Entry point completed: Emby.Server.Implementations.Notifications.Notifications. Duration: 0.000829 seconds 2018-01-19 23:04:01.575 Info App: Starting entry point Emby.Server.Implementations.Notifications.WebSocketNotifier 2018-01-19 23:04:01.575 Info App: Entry point completed: Emby.Server.Implementations.Notifications.WebSocketNotifier. Duration: 0.000371 seconds 2018-01-19 23:04:01.575 Info App: Starting entry point Emby.Server.MediaEncoding.Api.ApiEntryPoint 2018-01-19 23:04:01.575 Info App: Entry point completed: Emby.Server.MediaEncoding.Api.ApiEntryPoint. Duration: 0.000423 seconds 2018-01-19 23:04:01.575 Info App: Starting entry point Emby.Dlna.DlnaProfileEntryPoint 2018-01-19 23:04:01.575 Info App: Entry point completed: Emby.Dlna.DlnaProfileEntryPoint. Duration: 2.6E-05 seconds 2018-01-19 23:04:01.575 Info App: Starting entry point Emby.Dlna.Main.DlnaEntryPoint 2018-01-19 23:04:01.630 Info App: Entry point completed: Emby.Dlna.Main.DlnaEntryPoint. Duration: 0.054479 seconds 2018-01-19 23:04:01.630 Info App: Starting entry point MediaBrowser.XbmcMetadata.EntryPoint 2018-01-19 23:04:01.630 Info App: Entry point completed: MediaBrowser.XbmcMetadata.EntryPoint. Duration: 7.4E-05 seconds 2018-01-19 23:04:01.630 Info App: Starting entry point Emby.Server.CinemaMode.IntrosEntryPoint 2018-01-19 23:04:01.630 Info App: Entry point completed: Emby.Server.CinemaMode.IntrosEntryPoint. Duration: 0.0001 seconds 2018-01-19 23:04:01.630 Info App: Starting entry point Emby.Security.PluginSecurityManager 2018-01-19 23:04:01.630 Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 2.5E-05 seconds 2018-01-19 23:04:01.630 Info App: Starting entry point Emby.Server.Connect.ConnectEntryPoint 2018-01-19 23:04:01.631 Info App: Loading data from /var/db/emby-server/data/connect.txt 2018-01-19 23:04:01.634 Info App: Loading data from /var/db/emby-server/data/wan.dat 2018-01-19 23:04:01.674 Info App: Entry point completed: Emby.Server.Connect.ConnectEntryPoint. Duration: 0.04342 seconds 2018-01-19 23:04:01.674 Info App: Starting entry point Emby.Server.Sync.SyncManagerEntryPoint 2018-01-19 23:04:01.676 Info App: Sqlite version: 3.21.0 2018-01-19 23:04:01.676 Info App: Sqlite compiler options: COMPILER=clang-4.0.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS4,ENABLE_RTREE,ENABLE_UNLOCK_NOTIFY,HAVE_ISNAN,SECURE_DELETE,TEMP_STORE=1,THREADSAFE=1,USE_URI 2018-01-19 23:04:01.676 Info App: Default journal_mode for /var/db/emby-server/data/sync14.db is wal 2018-01-19 23:04:01.677 Info App: PRAGMA synchronous=1 2018-01-19 23:04:01.681 Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.007429 seconds 2018-01-19 23:04:01.682 Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint 2018-01-19 23:04:01.682 Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.000424 seconds 2018-01-19 23:04:01.682 Info App: Starting entry point Emby.Security.PluginSecurityManager 2018-01-19 23:04:01.682 Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 7.9E-05 seconds 2018-01-19 23:04:01.682 Info App: All entry points have started 2018-01-19 23:04:01.783 Info LibraryMonitor: Watching directory /zdata/media/tv 2018-01-19 23:04:01.832 Error LibraryMonitor: Error in Directory watcher for: /zdata/media/livetv/emby *** Error Report *** Version: 3.2.70.0 Command line: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -os freebsd -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server Operating system: Unix 11.1.4.0 64-Bit OS: True 64-Bit Process: True User Interactive: False Mono: 4.8.1 (4.8.1.0 Wed Sep 20 01:18:30 UTC 2017) Processor count: 4 Program data path: /var/db/emby-server Application directory: /usr/local/lib/emby-server System.IO.IOException: persistent kevent() error, error code = '0' at System.IO.KqueueMonitor.Monitor () [0x0013f] in <65d66c5eaa6a48038257422d3c294dab>:0 at System.IO.KqueueMonitor.DoMonitor () [0x00047] in <65d66c5eaa6a48038257422d3c294dab>:0 System.IO.IOException at System.IO.KqueueMonitor.Monitor () [0x0013f] in <65d66c5eaa6a48038257422d3c294dab>:0 at System.IO.KqueueMonitor.DoMonitor () [0x00047] in <65d66c5eaa6a48038257422d3c294dab>:0 2018-01-19 23:04:01.832 Info LibraryMonitor: Stopping directory watching for path /zdata/media/livetv/emby 2018-01-19 23:04:01.833 Info LibraryMonitor: Watching directory /zdata/media/movies 2018-01-19 23:04:02.091 Info HttpClient: HttpClientManager GET: http://emby.media/community/index.php?/blog/rss/1-media-browser-developers-blog 2018-01-19 23:04:04.183 Info TaskManager: StartupTrigger fired for task: Check for application updates 2018-01-19 23:04:04.183 Info TaskManager: StartupTrigger fired for task: Check for plugin updates 2018-01-19 23:04:04.183 Info TaskManager: Queueing task SystemUpdateTask 2018-01-19 23:04:04.183 Info TaskManager: Queueing task PluginUpdateTask 2018-01-19 23:04:04.186 Info TaskManager: Executing Check for plugin updates 2018-01-19 23:04:04.186 Info TaskManager: Executing Check for application updates 2018-01-19 23:04:04.190 Info InstallationManager: Opening /var/db/emby-server/cache/serverpackages.json 2018-01-19 23:04:04.232 Error LibraryMonitor: Error in Directory watcher for: /zdata/media/tv *** Error Report *** Version: 3.2.70.0 Command line: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -os freebsd -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server Operating system: Unix 11.1.4.0 64-Bit OS: True 64-Bit Process: True User Interactive: False Mono: 4.8.1 (4.8.1.0 Wed Sep 20 01:18:30 UTC 2017) Processor count: 4 Program data path: /var/db/emby-server Application directory: /usr/local/lib/emby-server System.IO.IOException: persistent kevent() error, error code = '13' at System.IO.KqueueMonitor.Monitor () [0x0013f] in <65d66c5eaa6a48038257422d3c294dab>:0 at System.IO.KqueueMonitor.DoMonitor () [0x00047] in <65d66c5eaa6a48038257422d3c294dab>:0 System.IO.IOException at System.IO.KqueueMonitor.Monitor () [0x0013f] in <65d66c5eaa6a48038257422d3c294dab>:0 at System.IO.KqueueMonitor.DoMonitor () [0x00047] in <65d66c5eaa6a48038257422d3c294dab>:0 2018-01-19 23:04:04.232 Info LibraryMonitor: Stopping directory watching for path /zdata/media/tv 2018-01-19 23:04:04.236 Info TaskManager: Check for application updates Completed after 0 minute(s) and 0 seconds 2018-01-19 23:04:04.243 Info HttpClient: HttpClientManager.GetTempFileResponse url: https://www.mb3admin.com/admin/service/EmbyPackages.json 2018-01-19 23:04:04.246 Info TaskManager: ExecuteQueuedTasks 2018-01-19 23:04:04.264 Info TaskManager: Check for plugin updates Completed after 0 minute(s) and 0 seconds 2018-01-19 23:04:04.264 Info TaskManager: ExecuteQueuedTasks 2018-01-19 23:04:04.277 Error LibraryMonitor: Error in Directory watcher for: /zdata/media/movies *** Error Report *** Version: 3.2.70.0 Command line: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -os freebsd -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server Operating system: Unix 11.1.4.0 64-Bit OS: True 64-Bit Process: True User Interactive: False Mono: 4.8.1 (4.8.1.0 Wed Sep 20 01:18:30 UTC 2017) Processor count: 4 Program data path: /var/db/emby-server Application directory: /usr/local/lib/emby-server System.IO.IOException: persistent kevent() error, error code = '0' at System.IO.KqueueMonitor.Monitor () [0x0013f] in <65d66c5eaa6a48038257422d3c294dab>:0 at System.IO.KqueueMonitor.DoMonitor () [0x00047] in <65d66c5eaa6a48038257422d3c294dab>:0 System.IO.IOException at System.IO.KqueueMonitor.Monitor () [0x0013f] in <65d66c5eaa6a48038257422d3c294dab>:0 at System.IO.KqueueMonitor.DoMonitor () [0x00047] in <65d66c5eaa6a48038257422d3c294dab>:0 2018-01-19 23:04:04.277 Info LibraryMonitor: Stopping directory watching for path /zdata/media/movies 2018-01-19 23:04:06.642 Error Main: UnhandledException *** Error Report *** Version: 3.2.70.0 Command line: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -os freebsd -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server Operating system: Unix 11.1.4.0 64-Bit OS: True 64-Bit Process: True User Interactive: False Mono: 4.8.1 (4.8.1.0 Wed Sep 20 01:18:30 UTC 2017) Processor count: 4 Program data path: /var/db/emby-server Application directory: /usr/local/lib/emby-server System.Net.Sockets.SocketException (0x80004005): Address already in use at System.Net.Sockets.Socket.Bind (System.Net.EndPoint localEP) [0x0004c] in <65d66c5eaa6a48038257422d3c294dab>:0 at Emby.Server.Implementations.Net.UdpSocket..ctor (System.Net.Sockets.Socket socket, System.Int32 localPort, System.Net.IPAddress ip) [0x0006b] in <730a104ef6c8470ebc4f70071ce76249>:0 at Emby.Server.Implementations.Net.SocketFactory.CreateUdpMulticastSocket (System.String ipAddress, System.Int32 multicastTimeToLive, System.Int32 localPort) [0x000ba] in <730a104ef6c8470ebc4f70071ce76249>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>m__1 (System.Object state) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context (System.Object state) [0x0000e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x0002a] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 System.Net.Sockets.SocketException at System.Net.Sockets.Socket.Bind (System.Net.EndPoint localEP) [0x0004c] in <65d66c5eaa6a48038257422d3c294dab>:0 at Emby.Server.Implementations.Net.UdpSocket..ctor (System.Net.Sockets.Socket socket, System.Int32 localPort, System.Net.IPAddress ip) [0x0006b] in <730a104ef6c8470ebc4f70071ce76249>:0 at Emby.Server.Implementations.Net.SocketFactory.CreateUdpMulticastSocket (System.String ipAddress, System.Int32 multicastTimeToLive, System.Int32 localPort) [0x000ba] in <730a104ef6c8470ebc4f70071ce76249>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>m__1 (System.Object state) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context (System.Object state) [0x0000e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x0002a] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 Link to comment Share on other sites More sharing options...
Luke 37113 Posted January 20, 2018 Share Posted January 20, 2018 Ok, a windows user reported this. It's already patched in the beta if you want to grab the mono zip and unpack that over your installation: https://github.com/MediaBrowser/Emby/releases/download/3.2.70.2/Emby.Mono.zip Thanks. Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 20, 2018 Author Share Posted January 20, 2018 Already rolled back to 3.2.60 and no longer seeing this; I guess I'll just wait until the next port update. Link to comment Share on other sites More sharing options...
woodsb02 17 Posted January 20, 2018 Share Posted January 20, 2018 For the record, I am not seeing this behaviour on FreeBSD 12-CURRENT with emby-server 3.2.70.0. I do not use livetv, which is mentioned in this log file around the time of the error. Is it specific to livetv? Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 20, 2018 Author Share Posted January 20, 2018 (edited) I don't think it's (directly) related to Live TV; it looks like it dies trying to open a UDP multicast socket because someone else already has it opened, so probably only an issue if something else on your machine happens to be using that same port. Maybe mDNS- or SSDP-related? In any case, I actually see the same error in the log on 3.2.60, but apparently on that version the exception is getting caught (and the server keeps running), but on 3.2.70 it is not (and it exits because of unhandled exception). Edited January 20, 2018 by razzfazz Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 20, 2018 Author Share Posted January 20, 2018 Bingo -- error goes away when I stop tvheadend. Looks like they're both trying to open a UDP multicast socket for port 1900 (SSDP), and at least one of them is doing so without setting SO_REUSEPORT. Link to comment Share on other sites More sharing options...
Luke 37113 Posted January 20, 2018 Share Posted January 20, 2018 Interesting, thanks for the info. Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 20, 2018 Author Share Posted January 20, 2018 (edited) Looks like you're creating multicast sockets with SocketOptionName.ReuseAddress (the .NET equivalent of SO_REUSEADDR), where you'd really want the equivalent of SO_REUSEPORT (apparently in WinSock this is split in SO_REUSEUNICASTPORT and SO_REUSEMULTICASTPORT, so you'd want the latter). Also, is there a reason you're binding to IPADDR_ANY for SSDP? Seems like that should be 239.255.255.250... EDIT: Never mind, looks like Emby can also create a unicast socket for SSDP, and only uses IPADDR_ANY for that. Also, it would appear that for multicast sockets, SO_REUSEADDR is actually supposed to behave just like SO_REUSEPORT, so that doesn't seem to be the issue, either. Hmm... Edited January 20, 2018 by razzfazz 1 Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 21, 2018 Author Share Posted January 21, 2018 (edited) So I did some more digging, and it does look like Emby is at fault here: When I start miniupnpd and tvheadend (in either order), they both successfully bind to multicasts on port 1900. However, when I start Emby and miniupnpd in either order, whichever of the two is started second will fail to bind with "Address already in use". Edited January 21, 2018 by razzfazz Link to comment Share on other sites More sharing options...
Luke 37113 Posted January 21, 2018 Share Posted January 21, 2018 So I did some more digging, and it does look like Emby is at fault here: When I start miniupnpd and tvheadend (in either order), they both successfully bind to multicasts on port 1900. However, when I start Emby and miniupnpd in either order, the whichever is started second will fail to bind with "Address already in use". So it looks like SO_REUSEADDR somehow doesn't take effect on the socket that Emby creates for SSDP. Because on BSD the mono runtime throws a platform not supported error when using that option. 1 Link to comment Share on other sites More sharing options...
woodsb02 17 Posted January 21, 2018 Share Posted January 21, 2018 Hi Luke, can you point me to the relevant section in the mono code for this? Link to comment Share on other sites More sharing options...
Luke 37113 Posted January 21, 2018 Share Posted January 21, 2018 Well there's this: https://github.com/mono/mono/blob/master/mcs/class/System/System.Net.Sockets/Socket.cs#L2418 But I don't know if the bsd port has a customized socket implementation. Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 21, 2018 Author Share Posted January 21, 2018 Because on BSD the mono runtime throws a platform not supported error when using that option. That's not what I'm seeing; when I run truss on Emby, it shows that the setsockopt() syscalls all return zero, and when I add an error log in the relevant catch sections in the Emby code, that never seems to get called. 1 Link to comment Share on other sites More sharing options...
razzfazz 11 Posted January 21, 2018 Author Share Posted January 21, 2018 And in fact Mono on FreeBSD automatically sets SO_REUSEPORT whenever SO_REUSEADDR is set and the socket type is gram or stream; see mono bug 81891. 1 Link to comment Share on other sites More sharing options...
Luke 37113 Posted January 21, 2018 Share Posted January 21, 2018 I'm sure you're right. This is all coming from memory so things may have changed. 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