5/16/2023 0 Comments Emby server betaInfo App: SyncRepository Initialize taking write lock Info App: Entry point completed: .EncodingManagerEntryPoint. Info App: Starting entry point .EncodingManagerEntryPoint Info LiveTV: Creating recording timer for a323845af0562ce48d86e5ae2772d36f, It's Sew Easy. Info LiveTV: Creating recording timer for 5ff8de3d633dc9f1ae3ae9a445c0e6f5, Best of Sewing With Nancy. Info LibraryMonitor: Watching directory /config/data/livetv/recordings Info LiveTV: Loading live tv data from /config/data/livetv/timers Info App: Entry point completed: .ChannelsEntryPoint. Info App: Starting entry point .ChannelsEntryPoint Info App: Entry point completed: .UserDataChangeNotifier. Info App: Starting entry point .UserDataChangeNotifier Info App: Entry point completed: .SystemEvents. Info App: Starting entry point .SystemEvents Info App: Entry point completed: .StartupWizard. Info App: Starting entry point .StartupWizard Info App: Entry point completed: .ServerEventNotifier. Info LibraryMonitor: Watching directory /mnt/Music Info App: Starting entry point .ServerEventNotifier Info App: Entry point completed: .Librar圜hangedNotifier. Info App: Starting entry point .Librar圜hangedNotifier Info App: Entry point completed: .KeepServerAwake. Info App: Starting entry point .KeepServerAwake Info App: Entry point completed: .AutomaticRestartEntryPoint. Info App: Starting entry point .AutomaticRestartEntryPoint Info App: Entry point completed: .LibraryMonitorStartup. TargetSite: Void UpdateStatusAfterSocketErrorAndThrowException(, System.String) : (0xFFFDFFFE): Unknown socket errorĪt .UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)Īt .SetMulticastOption(SocketOptionName optionName, MulticastOption MR)Īt .SetSocketOption(SocketOptionLevel optionLevel, SocketOptionName optionName, Object optionValue)Īt (IPAddress localIpAddress, Int32 localPort, List`1 localAddresses)Īt (CancellationToken cancellationToken) IPAddress: 10.0.0.33Ĭommand line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Warn App: SetSocketOption 'MulticastLocalAdminAddress' failed for IP address '10.0.0.33': Unknown socket errorĮrror App: Error in CreateSsdpUdpSocket. Info App: Starting entry point .LibraryMonitorStartup Info App: Entry point completed: .DeviceAccessEntryPoint. Info App: Starting entry point .DeviceAccessEntryPoint Info App: Entry point completed: .UdpServerEntryPoint. Info App: Starting entry point .UdpServerEntryPoint Info App: Entry point completed: Tvdb.EntryPoint. Info App: Starting entry point Tvdb.EntryPoint Info App: Entry point completed: NfoMetadata.EntryPoint. Info App: Starting entry point NfoMetadata.EntryPoint Info App: Loading data from /config/data/connect.txt And yes in futher i will use a native unraid system where the data drives will also connected to unraid and not to a vm. I hope you guys can help me to solve my problem. Everything together has read and write permissions according to the dialog. I created the whole "mnt" folder for all internal host hard disks from the UNraid host itself and from the SMB shares instead of just the SMB share. When I look at the path in the emby container for the media library everything is set correctly there. On the Emby Dashboard page, contrary to the above settings, the paths for the meta data are not traced back to the media directories, but are located in the config folder of the emby Docker container. I have made the appropriate settings in the libraries, see screens: This SMB share is mounted via Unassigned Device Plugin and here I also looked if there are any READ WRITE permissions, but found nothing. Here also runs a virtual machine with Xpenology (Synologys DSM) which shares a SMB share with Unraid and provides emby. I suspect a permissions problem but can't solve it myself.Įmby is running as a Docker container on a Unraid host system. If I add the data manually to the folders emby loads them without problems. Emby does not store the meta data and images in the media folders.
0 Comments
Leave a Reply. |