Jump to content

emby 4.8.3.0 just halts w/o starting web UI

dance4ever

By dance4ever
in Linux

 Share
Go to solution Solved by dance4ever,

Recommended Posts

dance4ever

dance4ever 11

Posted
Posted (edited)

hi!   I have 4.8.3.0 installed using docker on Ubuntu Server 22.04.4 LTS.

How do I troubleshoot an install that was previously working and decided to stop working?  What I’ve confirmed is if I rename the root emby folder and force the server to recreate all its directories, the web interface comes up.   If I put the old emby root directory back in place, the web server never starts.  Here is the log file: 

2024-04-20 00:19:59.630 Info Main: Application path: /system/EmbyServer.dll
2024-04-20 00:20:00.009 Info App: Setting default culture to en-US
2024-04-20 00:20:00.014 Info Main: Emby
        Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3
        Operating system: Linux version 5.15.0-105-generic (buildd@lcy02-amd64-007) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #115-Ubun
        Framework: .NET 6.0.25
        OS/Process: x64/x64
        Runtime: system/System.Private.CoreLib.dll
        Processor count: 2
        Data path: /config
        Application path: /system
2024-04-20 00:20:00.014 Info Main: Logs path: /config/logs
2024-04-20 00:20:00.014 Info Main: Cache path: /config/cache
2024-04-20 00:20:00.014 Info Main: Internal metadata path: /config/metadata
2024-04-20 00:20:00.017 Info App: Emby Server Version: 4.8.3.0
2024-04-20 00:20:00.021 Info App: Loading assemblies
2024-04-20 00:20:00.072 Info App: File /config/plugins/Fanart.dll has version 1.0.16.0
2024-04-20 00:20:00.073 Info App: File /system/plugins/Fanart.dll has version 1.0.16.0
2024-04-20 00:20:00.073 Info App: File /config/plugins/MovieDb.dll has version 1.7.5.0
2024-04-20 00:20:00.073 Info App: File /system/plugins/MovieDb.dll has version 1.7.4.0
2024-04-20 00:20:00.074 Info App: File /config/plugins/OMDb.dll has version 1.0.21.0
2024-04-20 00:20:00.074 Info App: File /system/plugins/OMDb.dll has version 1.0.21.0
2024-04-20 00:20:00.074 Info App: File /config/plugins/Emby.PortMapper.dll has version 1.2.4.0
2024-04-20 00:20:00.074 Info App: File /system/plugins/Emby.PortMapper.dll has version 1.2.4.0
2024-04-20 00:20:00.074 Info App: File /config/plugins/EmbyGuideData.dll has version 1.0.13.0
2024-04-20 00:20:00.074 Info App: File /system/plugins/EmbyGuideData.dll has version 1.0.13.0
2024-04-20 00:20:00.075 Info App: File /config/plugins/StudioImages.dll has version 1.0.3.0
2024-04-20 00:20:00.075 Info App: File /system/plugins/StudioImages.dll has version 1.0.3.0
2024-04-20 00:20:00.075 Info App: File /config/plugins/MBBackup.dll has version 1.6.4.0
2024-04-20 00:20:00.075 Info App: File /system/plugins/MBBackup.dll has version 1.6.3.0
2024-04-20 00:20:00.076 Info App: File /config/plugins/OpenSubtitles.dll has version 1.0.54.0
2024-04-20 00:20:00.076 Info App: File /system/plugins/OpenSubtitles.dll has version 1.0.53.0
2024-04-20 00:20:00.076 Info App: File /config/plugins/NfoMetadata.dll has version 1.0.80.0
2024-04-20 00:20:00.076 Info App: File /system/plugins/NfoMetadata.dll has version 1.0.80.0
2024-04-20 00:20:00.076 Info App: File /config/plugins/Tvdb.dll has version 1.4.9.0
2024-04-20 00:20:00.076 Info App: File /system/plugins/Tvdb.dll has version 1.4.5.0
2024-04-20 00:20:00.077 Info App: File /config/plugins/Emby.Dlna.dll has version 1.3.8.0
2024-04-20 00:20:00.077 Info App: File /system/plugins/Emby.Dlna.dll has version 1.3.7.0
2024-04-20 00:20:00.077 Info App: File /config/plugins/Emby.Webhooks.dll has version 1.0.35.0
2024-04-20 00:20:00.077 Info App: File /system/plugins/Emby.Webhooks.dll has version 1.0.35.0
2024-04-20 00:20:00.091 Info App: Loading Fanart, Version=1.0.16.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Fanart.dll
2024-04-20 00:20:00.091 Info App: Loading MovieDb, Version=1.7.5.0, Culture=neutral, PublicKeyToken=null from /config/plugins/MovieDb.dll
2024-04-20 00:20:00.091 Info App: Loading OMDb, Version=1.0.21.0, Culture=neutral, PublicKeyToken=null from /config/plugins/OMDb.dll
2024-04-20 00:20:00.092 Info App: Loading Emby.PortMapper, Version=1.2.4.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Emby.PortMapper.dll
2024-04-20 00:20:00.092 Info App: Loading statistics, Version=3.2.0.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Statistics.dll
2024-04-20 00:20:00.092 Info App: Loading EmbyGuideData, Version=1.0.13.0, Culture=neutral, PublicKeyToken=null from /config/plugins/EmbyGuideData.dll
2024-04-20 00:20:00.092 Info App: Loading StudioImages, Version=1.0.3.0, Culture=neutral, PublicKeyToken=null from /config/plugins/StudioImages.dll
2024-04-20 00:20:00.092 Info App: Loading MBBackup, Version=1.6.4.0, Culture=neutral, PublicKeyToken=null from /config/plugins/MBBackup.dll
2024-04-20 00:20:00.092 Info App: Loading OpenSubtitles, Version=1.0.54.0, Culture=neutral, PublicKeyToken=null from /config/plugins/OpenSubtitles.dll
2024-04-20 00:20:00.092 Info App: Loading NfoMetadata, Version=1.0.80.0, Culture=neutral, PublicKeyToken=null from /config/plugins/NfoMetadata.dll
2024-04-20 00:20:00.092 Info App: Loading Tvdb, Version=1.4.9.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Tvdb.dll
2024-04-20 00:20:00.092 Info App: Loading Emby.Dlna, Version=1.3.8.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Emby.Dlna.dll
2024-04-20 00:20:00.092 Info App: Loading Emby.Webhooks, Version=1.0.35.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Emby.Webhooks.dll
2024-04-20 00:20:00.092 Info App: Loading Emby.Api, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading Emby.Web, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading MediaBrowser.Model, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading MediaBrowser.Common, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading MediaBrowser.Controller, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading Emby.Providers, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading Emby.Photos, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading Emby.Server.Implementations, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading Emby.LiveTV, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading Emby.ActivityLog, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading Emby.Server.MediaEncoding, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading Emby.LocalMetadata, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading Emby.Notifications, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading Emby.Web.GenericUI, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading Emby.Codecs.Dxva, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading Emby.Codecs, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading Emby.Server.Connect, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading Emby.Server.Sync, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.092 Info App: Loading EmbyServer, Version=4.8.3.0, Culture=neutral, PublicKeyToken=null
2024-04-20 00:20:00.400 Info SqliteUserRepository: Sqlite version: 3.42.0
2024-04-20 00:20:00.402 Info SqliteUserRepository: Sqlite compiler options: ATOMIC_INTRINSICS=1,COMPILER=gcc-10.3.0,DEFAULT_AUTOVACUUM,DEFAULT_CACHE_SIZE=-2000,DEFAULT_FILE_FORMAT=4,DEFAULT_JOURNAL_SIZE_LIMIT=-1,DEFAULT_MMAP_SIZE=0,DEFAULT_PAGE_SIZE=4096,DEFAULT_PCACHE_INITSZ=20,DEFAULT_RECURSIVE_TRIGGERS,DEFAULT_SECTOR_SIZE=4096,DEFAULT_SYNCHRONOUS=2,DEFAULT_WAL_AUTOCHECKPOINT=1000,DEFAULT_WAL_SYNCHRONOUS=2,DEFAULT_WORKER_THREADS=0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS4,ENABLE_FTS5,ENABLE_GEOPOLY,ENABLE_MATH_FUNCTIONS,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MALLOC_SOFT_LIMIT=1024,MAX_ATTACHED=10,MAX_COLUMN=2000,MAX_COMPOUND_SELECT=500,MAX_DEFAULT_PAGE_SIZE=8192,MAX_EXPR_DEPTH=1000,MAX_FUNCTION_ARG=127,MAX_LENGTH=1000000000,MAX_LIKE_PATTERN_LENGTH=50000,MAX_MMAP_SIZE=0x7fff0000,MAX_PAGE_COUNT=1073741823,MAX_PAGE_SIZE=65536,MAX_SCHEMA_RETRY=25,MAX_SQL_LENGTH=1000000000,MAX_TRIGGER_DEPTH=1000,MAX_VARIABLE_NUMBER=250000,MAX_VDBE_OP=250000000,MAX_WORKER_THREADS=8,MUTEX_PTHREADS,OMIT_LOOKASIDE,SECURE_DELETE,SYSTEM_MALLOC,TEMP_STORE=1,THREADSAFE=1
2024-04-20 00:20:00.402 Info SqliteUserRepository: Opening sqlite connection to /config/data/users.db
2024-04-20 00:20:00.417 Info SqliteUserRepository: Default journal_mode for /config/data/users.db is wal
2024-04-20 00:20:00.420 Info SqliteUserRepository: PRAGMA foreign_keys=1
2024-04-20 00:20:00.421 Info SqliteUserRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0
2024-04-20 00:20:00.421 Info SqliteUserRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0
2024-04-20 00:20:00.508 Info ActivityRepository: Opening sqlite connection to /config/data/activitylog.db
2024-04-20 00:20:00.511 Info ActivityRepository: Default journal_mode for /config/data/activitylog.db is wal
2024-04-20 00:20:00.511 Info ActivityRepository: PRAGMA foreign_keys=1
2024-04-20 00:20:00.511 Info ActivityRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0
2024-04-20 00:20:00.511 Info ActivityRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0
2024-04-20 00:20:00.533 Info NetworkManager: Detecting local network addresses
2024-04-20 00:20:00.534 Info NetworkManager: networkInterface: Ethernet eth0, Speed: 10000000000, Description: eth0
2024-04-20 00:20:00.534 Info NetworkManager: GatewayAddresses: 172.24.0.1
2024-04-20 00:20:00.535 Info NetworkManager: UnicastAddresses: 172.24.0.2
2024-04-20 00:20:00.535 Info NetworkManager: networkInterface: Loopback lo, Speed: -1, Description: lo
2024-04-20 00:20:00.535 Info NetworkManager: GatewayAddresses: 
2024-04-20 00:20:00.535 Info NetworkManager: UnicastAddresses: 127.0.0.1
2024-04-20 00:20:00.602 Info NetworkManager: Detected local ip addresses: [{"IPAddress":"172.24.0.2","HasGateWayAddress":true,"PrefixLength":16,"IPv4Mask":"255.255.0.0"},{"IPAddress":"127.0.0.1","HasGateWayAddress":false,"PrefixLength":8,"IPv4Mask":"255.0.0.0"}]
2024-04-20 00:20:00.606 Info SqliteDisplayPreferencesRepository: Opening sqlite connection to /config/data/displaypreferences.db
2024-04-20 00:20:00.607 Info SqliteDisplayPreferencesRepository: Default journal_mode for /config/data/displaypreferences.db is wal
2024-04-20 00:20:00.607 Info SqliteDisplayPreferencesRepository: PRAGMA foreign_keys=1
2024-04-20 00:20:00.607 Info SqliteDisplayPreferencesRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0
2024-04-20 00:20:00.607 Info SqliteDisplayPreferencesRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0
2024-04-20 00:20:00.618 Info App: Adding HttpListener prefix http://+:8097/
2024-04-20 00:20:00.671 Info AuthenticationRepository: Opening sqlite connection to /config/data/authentication.db
2024-04-20 00:20:00.673 Info AuthenticationRepository: Default journal_mode for /config/data/authentication.db is wal
2024-04-20 00:20:00.674 Info AuthenticationRepository: PRAGMA foreign_keys=1
2024-04-20 00:20:00.674 Info AuthenticationRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0
2024-04-20 00:20:00.674 Info AuthenticationRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0
2024-04-20 00:20:00.690 Info SqliteItemRepository: Opening sqlite connection to /config/data/library.db
2024-04-20 00:20:00.698 Info SqliteItemRepository: Default journal_mode for /config/data/library.db is wal
2024-04-20 00:20:00.699 Info SqliteItemRepository: PRAGMA cache_size=-98304
2024-04-20 00:20:00.699 Info SqliteItemRepository: PRAGMA page_size=4096
2024-04-20 00:20:00.699 Info SqliteItemRepository: PRAGMA foreign_keys=1
2024-04-20 00:20:00.699 Info SqliteItemRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0
2024-04-20 00:20:00.699 Info SqliteItemRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0
2024-04-20 00:20:00.771 Info SqliteItemRepository: Init Complete
2024-04-20 00:20:01.109 Info App: Emby
        Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3
        Operating system: Linux version 5.15.0-105-generic (buildd@lcy02-amd64-007) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #115-Ubun
        Framework: .NET 6.0.25
        OS/Process: x64/x64
        Runtime: system/System.Private.CoreLib.dll
        Processor count: 2
        Data path: /config
        Application path: /system
2024-04-20 00:20:01.110 Info App: Logs path: /config/logs
2024-04-20 00:20:01.110 Info App: Cache path: /config/cache
2024-04-20 00:20:01.110 Info App: Internal metadata path: /config/metadata
2024-04-20 00:20:01.110 Info App: Transcoding temporary files path: /config/transcoding-temp
2024-04-20 00:20:02.422 Info FfmpegManager: FFMpeg: /bin/ffmpeg
2024-04-20 00:20:02.422 Info FfmpegManager: FFProbe: /bin/ffprobe
2024-04-20 00:20:02.422 Info FfmpegManager: FFDetect: /bin/ffdetect
2024-04-20 00:20:02.431 Info Skia: SkiaSharp version: 2.88.0.0
2024-04-20 00:20:02.433 Info ImageProcessor: Adding image processor Skia
2024-04-20 00:20:02.465 Info libvips: NetVips version: 2.3.1.0
2024-04-20 00:20:02.465 Info ImageProcessor: Adding image processor libvips
2024-04-20 00:20:02.533 Info TaskManager: Daily trigger for Emby Server Backup set to fire at 04/21/2024 00:10:00, which is 1429.9577930983332 minutes from now.
2024-04-20 00:20:02.535 Info TaskManager: Daily trigger for Thumbnail image extraction set to fire at 04/20/2024 02:00:00, which is 99.95774068666667 minutes from now.
2024-04-20 00:20:02.882 Info TaskManager: Daily trigger for Rotate log file set to fire at 04/21/2024 00:00:00, which is 1419.951958945 minutes from now.
2024-04-20 00:20:02.908 Info TaskManager: Queueing task HardwareDetectionScheduledTask
2024-04-20 00:20:02.912 Info TaskManager: Executing Hardware Detection
2024-04-20 00:20:02.923 Info App: ServerId: 90c28209f84a4d6eb5b35a58d8d192c7
2024-04-20 00:20:02.961 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -version' Execute: /bin/ffmpeg -hide_banner -version
2024-04-20 00:20:02.992 Info App: Starting entry point Emby.Dlna.Main.DlnaEntryPoint
2024-04-20 00:20:03.000 Info FfmpegManager: ProcessRun 'ffmpeg -hide_banner -version' Process exited with code 0 - Succeeded
2024-04-20 00:20:03.032 Info FfmpegManager: FfmpegValidator.Validate complete
2024-04-20 00:20:03.219 Info App: Entry point completed: Emby.Dlna.Main.DlnaEntryPoint. Duration: 0.226789 seconds
2024-04-20 00:20:03.223 Info App: Starting entry point Emby.Server.Implementations.Networking.RemoteAddressEntryPoint
2024-04-20 00:20:03.228 Info App: Loading data from /config/data/wan.dat
2024-04-20 00:20:03.233 Info App: Entry point completed: Emby.Server.Implementations.Networking.RemoteAddressEntryPoint. Duration: 0.0098643 seconds
2024-04-20 00:20:03.234 Info App: Starting entry point Emby.Server.Connect.ConnectEntryPoint
2024-04-20 00:20:03.237 Info App: Loading data from /config/data/connect.txt
2024-04-20 00:20:03.239 Info App: Init BeginReceive on 0.0.0.0
2024-04-20 00:20:03.239 Info App: Init BeginReceive on 0.0.0.0
2024-04-20 00:20:03.239 Info App: Entry point completed: Emby.Server.Connect.ConnectEntryPoint. Duration: 0.005443 seconds
2024-04-20 00:20:03.240 Info App: Core startup complete
2024-04-20 00:20:03.250 Info App: Starting entry point MovieDb.Security.PluginStartup
2024-04-20 00:20:03.251 Info App: Entry point completed: MovieDb.Security.PluginStartup. Duration: 0.0009738 seconds
2024-04-20 00:20:03.251 Info App: Starting entry point Emby.PortMapper.ExternalPortForwarding
2024-04-20 00:20:03.252 Info App: Entry point completed: Emby.PortMapper.ExternalPortForwarding. Duration: 0.0008323 seconds
2024-04-20 00:20:03.252 Info App: Starting entry point MBBackup.ServerEntryPoint
2024-04-20 00:20:03.252 Info App: Entry point completed: MBBackup.ServerEntryPoint. Duration: 6.32E-05 seconds
2024-04-20 00:20:03.252 Info App: Starting entry point NfoMetadata.EntryPoint
2024-04-20 00:20:03.253 Info App: Entry point completed: NfoMetadata.EntryPoint. Duration: 0.0006206 seconds
2024-04-20 00:20:03.253 Info App: Starting entry point Tvdb.EntryPoint
2024-04-20 00:20:03.253 Info App: Entry point completed: Tvdb.EntryPoint. Duration: 6.14E-05 seconds
2024-04-20 00:20:03.253 Info App: Starting entry point Emby.Webhooks.MigrationEntryPoint
2024-04-20 00:20:03.263 Info App: Entry point completed: Emby.Webhooks.MigrationEntryPoint. Duration: 0.002926 seconds
2024-04-20 00:20:03.263 Info App: Starting entry point Emby.Server.Implementations.Udp.UdpServerEntryPoint
2024-04-20 00:20:03.265 Info App: Entry point completed: Emby.Server.Implementations.Udp.UdpServerEntryPoint. Duration: 0.0016933 seconds
2024-04-20 00:20:03.265 Info App: Starting entry point Emby.Server.Implementations.Playlists.PlaylistUpgradeEntryPoint
2024-04-20 00:20:03.269 Info App: Entry point completed: Emby.Server.Implementations.Playlists.PlaylistUpgradeEntryPoint. Duration: 0.0031783 seconds
2024-04-20 00:20:03.269 Info App: Starting entry point Emby.Server.Implementations.Library.DeviceAccessEntryPoint
2024-04-20 00:20:03.270 Info App: Entry point completed: Emby.Server.Implementations.Library.DeviceAccessEntryPoint. Duration: 0.0006636 seconds
2024-04-20 00:20:03.270 Info App: Starting entry point Emby.Server.Implementations.IO.LibraryMonitorStartup
2024-04-20 00:20:03.283 Info SoftwareCodecProvider: h264, libx264, x264, V-E-libx264
2024-04-20 00:20:03.284 Info SoftwareCodecProvider: hevc, libx265, x265, V-E-libx265
2024-04-20 00:20:03.285 Info SoftwareCodecProvider: mpeg4, mpeg4, MPEG-4 part 2, V-E-mpeg4
2024-04-20 00:20:03.285 Info SoftwareCodecProvider: msmpeg4v3, msmpeg4, MPEG-4 part 2 (MS Variant 3), V-E-msmpeg4
2024-04-20 00:20:03.285 Info SoftwareCodecProvider: vp8, libvpx, libvpx VP8, V-E-libvpx
2024-04-20 00:20:03.291 Info SoftwareCodecProvider: h264, libx264, x264, V-E-libx264
2024-04-20 00:20:03.292 Info SoftwareCodecProvider: hevc, libx265, x265, V-E-libx265
2024-04-20 00:20:03.292 Info SoftwareCodecProvider: mpeg4, mpeg4, MPEG-4 part 2, V-E-mpeg4
2024-04-20 00:20:03.292 Info SoftwareCodecProvider: msmpeg4v3, msmpeg4, MPEG-4 part 2 (MS Variant 3), V-E-msmpeg4
2024-04-20 00:20:03.292 Info SoftwareCodecProvider: vp8, libvpx, libvpx VP8, V-E-libvpx
2024-04-20 00:20:03.295 Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.0248056 seconds
2024-04-20 00:20:03.295 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint
2024-04-20 00:20:03.296 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint. Duration: 0.0007693 seconds
2024-04-20 00:20:03.296 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.KeepServerAwake
2024-04-20 00:20:03.297 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.KeepServerAwake. Duration: 0.0002309 seconds
2024-04-20 00:20:03.297 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier
2024-04-20 00:20:03.299 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier. Duration: 0.0018423 seconds
2024-04-20 00:20:03.299 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier
2024-04-20 00:20:03.311 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.0117179 seconds
2024-04-20 00:20:03.312 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard
2024-04-20 00:20:03.312 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 0.0004591 seconds
2024-04-20 00:20:03.312 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents
2024-04-20 00:20:03.313 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 0.0006732 seconds
2024-04-20 00:20:03.313 Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier
2024-04-20 00:20:03.314 Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 0.0002695 seconds
2024-04-20 00:20:03.314 Info App: Starting entry point Emby.Server.Implementations.Channels.ChannelsEntryPoint
2024-04-20 00:20:03.317 Info App: Entry point completed: Emby.Server.Implementations.Channels.ChannelsEntryPoint. Duration: 0.0032508 seconds
2024-04-20 00:20:03.318 Info App: Starting entry point Emby.LiveTV.EntryPoint
2024-04-20 00:20:03.322 Info LibraryMonitor: Watching directory with new FileSystemWatcher for /userdata/kodi.ddb/movies for item 4514
2024-04-20 00:20:03.325 Info LiveTV: Loading live tv data from /config/data/livetv/timers
2024-04-20 00:20:03.328 Info VaapiCodecProvider: ProcessRun 'ffdetect_vaencdec' Execute: /bin/ffdetect -hide_banner -show_program_version -loglevel 48 -show_error -show_log 40 vaencdec -print_format json 
2024-04-20 00:20:03.348 Info App: Entry point completed: Emby.LiveTV.EntryPoint. Duration: 0.0297033 seconds
2024-04-20 00:20:03.348 Info App: Starting entry point Emby.LiveTV.RecordingNotifier
2024-04-20 00:20:03.352 Info App: Entry point completed: Emby.LiveTV.RecordingNotifier. Duration: 0.0033374 seconds
2024-04-20 00:20:03.352 Info App: Starting entry point Emby.ActivityLog.ActivityLogEntryPoint
2024-04-20 00:20:03.357 Info App: Entry point completed: Emby.ActivityLog.ActivityLogEntryPoint. Duration: 0.0049484 seconds
2024-04-20 00:20:03.357 Info App: Starting entry point Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint
2024-04-20 00:20:03.359 Info App: Entry point completed: Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint. Duration: 0.0015033 seconds
2024-04-20 00:20:03.359 Info App: Starting entry point Emby.Notifications.NotificationManagerEntryPoint
2024-04-20 00:20:03.363 Info VaapiCodecProvider: ProcessRun 'ffdetect_vaencdec' Process exited with code 0 - Succeeded
2024-04-20 00:20:03.376 Info Notifications: Registering event nofitier Emby Server User Notifications
2024-04-20 00:20:03.382 Info App: Entry point completed: Emby.Notifications.NotificationManagerEntryPoint. Duration: 0.0227096 seconds
2024-04-20 00:20:03.382 Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
2024-04-20 00:20:03.385 Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0026962 seconds
2024-04-20 00:20:03.385 Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint
2024-04-20 00:20:03.385 Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 0.0002086 seconds
2024-04-20 00:20:03.385 Info App: All entry points have started
2024-04-20 00:20:03.468 Info QuickSyncCodecProvider: ProcessRun 'ffdetect_qsvencdec' Execute: /bin/ffdetect -hide_banner -show_program_version -loglevel 48 -show_error -show_log 40 qsvencdec -print_format json 
2024-04-20 00:20:03.490 Info QuickSyncCodecProvider: ProcessRun 'ffdetect_qsvencdec' Process exited with code 0 - Succeeded
2024-04-20 00:20:03.560 Info NvidiaCodecProvider: ProcessRun 'ffdetect_nvencdec' Execute: /bin/ffdetect -hide_banner -show_program_version -loglevel 48 -show_error -show_log 40 nvencdec -print_format json 
2024-04-20 00:20:03.566 Info NvidiaCodecProvider: ProcessRun 'ffdetect_nvencdec' Process exited with code 1 - Failed
2024-04-20 00:20:03.917 Info CodecManager: CodecList:
2024-04-20 00:20:03.918 Info TaskManager: Hardware Detection Completed after 0 minute(s) and 1 seconds
2024-04-20 00:20:05.878 Info TaskManager: Queueing task PluginUpdateTask
2024-04-20 00:20:05.878 Info TaskManager: Executing Check for plugin updates
2024-04-20 00:20:05.881 Info TaskManager: Queueing task SystemUpdateTask
2024-04-20 00:20:05.882 Info TaskManager: Executing Check for application updates
2024-04-20 00:20:05.912 Info HttpClient: GET https://www.mb3admin.com/admin/service/EmbyPackages.json
2024-04-20 00:20:05.914 Info TaskManager: Queueing task SubtitleOcrDataTask
2024-04-20 00:20:05.914 Info TaskManager: Executing Download OCR Data
2024-04-20 00:20:05.946 Info TaskManager: Download OCR Data Completed after 0 minute(s) and 0 seconds
2024-04-20 00:20:06.157 Info TaskManager: Check for application updates Completed after 0 minute(s) and 0 seconds
2024-04-20 00:20:06.728 Info TaskManager: Check for plugin updates Completed after 0 minute(s) and 0 seconds

and that’s it - it just halts after 6-7 seconds.

Is there a way we can get the log file to be more verbose to see where it’s halting?

Reminder: I can’t get into the web interface so we need to do this all on the command line.  And another reminder: it doesn’t halt if I recreate the Emby root directories so it has something to do with my old library/config files (which currently is 100% stock, no extra plug-ins)

Edited by dance4ever
Luke Emby Team

Luke 38841

Posted
Posted

Hi, please try removing all .dll files from /config/plugins and see if that helps.

dance4ever

dance4ever 11

Posted
  • Author
Posted (edited)

nuked all the DLL’s, recreated the container and the DLLs get regenerated but the log file still stops at the same place.

EDIT: I should note the process is still running if we can inspect it somehow: 

***       791681  7.2  2.1 3725012 210992 ?      Sl   18:24   0:07 /system/EmbyServer -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3
Edited by dance4ever
Q-Droid

Q-Droid 830

Posted
Posted

It looks like you changed your port from the default. The server is running but you might be trying to connect to the wrong port?

Quote

2024-04-20 00:20:00.618 Info App: Adding HttpListener prefix http://+:8097/

 

dance4ever

dance4ever 11

Posted
  • Author
Posted (edited)
1 minute ago, Q-Droid said:

It looks like you changed your port from the default. The server is running but you might be trying to connect to the wrong port?

 

yes, this was done intentionally.  to make sure this wasn’t the issue, I created a container with the default 8096 and it still has the same issue but thanks for noticing.

The container comes up on port 8097 just fine if I nuke all the config directories.

Edited by dance4ever
Q-Droid

Q-Droid 830

Posted
Posted

But if you nuke the config directories it will start on the default 8096, not 8097. The server is running and listening on 8097 with your config. Now, if your docker compose/run is mapping 8096:8097 or 8097:8097 then you should be able to connect. But if mapping 8096:8096 or 8097:8096 it will only work when the default port values are in use, when it's nuked.

Docker compose/run can set the port values for the host side but not for Emby inside the container. Only the Emby settings do that.

Q-Droid

Q-Droid 830

Posted
Posted

Another thing - when the server has nothing to do, like after a restart without media changes or user activity, that place in your log is pretty much where it stops until there is activity.

 

dance4ever

dance4ever 11

Posted
  • Author
Posted
13 minutes ago, Q-Droid said:

Now, if your docker compose/run is mapping 8096:8097 or 8097:8097 then you should be able to connect.

that’s correct - that’s exactly what I’ve done and what I love about Docker - keeps Emby happy with defaults and keeps user happy changing ports at will :)

7 minutes ago, Q-Droid said:

Another thing - when the server has nothing to do, like after a restart without media changes or user activity, that place in your log is pretty much where it stops until there is activity.

 

thanks for confirming that - that’s what I suspected to - that’s why I’m wondering if there is debug output as the web server seemingly doesn’t start/serve.

In an attempt to kill two birds with one stone, I started another emby container to see if it will initialize the library with all the exported resume time and favorites metadata in all the .nfo files.  Didn’t have any luck.  To keep this thread focused, I will start a new thread in regards to this issue.

I feel it probably is more straight forward to figure out why the server is blocked serving a web page after initial startup.

Q-Droid

Q-Droid 830

Posted
Posted

You can do a few things to check. This is to see if it's actually listening but not the why if it isn't.

From the Emby host you can run netstat -lnp to verify the container is listening on the host (external) port. Look for the host side port you mapped.

Run wget http://`hostname`:<port> from the host command line.

Go into the container and do the same.

docker exec -it  <your emby container> /bin/sh

netstat -lnp to verify the container (internal) port.

wget http://`hostname`:<port>/web/index.html

 

  • Thanks 1
Q-Droid

Q-Droid 830

Posted
Posted
10 hours ago, dance4ever said:

thanks for confirming that - that’s what I suspected to - that’s why I’m wondering if there is debug output as the web server seemingly doesn’t start/serve.

 

You can enable debug logging from the config files. Change this value to true:

<config path>/config/system.xml:  <EnableDebugLevelLogging>true</EnableDebugLevelLogging>

And remove this line if it's there:

<config path>/config/system.xml:  <RevertDebugLogging>rotate</RevertDebugLogging>

Then restart the container.

  • Thanks 1
dance4ever

dance4ever 11

Posted
  • Author
Posted (edited)

Thank you for providing some more detailed troubleshooting steps! 

$ wget http://192.168.0.100:8097
--2024-04-20 15:41:06--  http://192.168.0.100:8097/
Connecting to 192.168.0.100:8097... failed: Connection refused.

the container is lacking a lot of command line utilities (I had to go to Portainer to figure out the internal IP address of 172.24.0.2): 

root@***:/# docker exec -it emby4ddb /bin/sh
# nestat -lnp
/bin/sh: 1: nestat: not found
# wget http://172.24.0.2:8096/web/index.html
/bin/sh: 2: wget: not found

 

10 hours ago, Q-Droid said:

You can enable debug logging from the config files. Change this value to true:

<config path>/config/system.xml:  <EnableDebugLevelLogging>true</EnableDebugLevelLogging>

we only have 3 additional lines at the end: 

024-04-20 23:02:07.080 Info TaskManager: Check for application updates Completed after 0 minute(s) and 0 second
s
2024-04-20 23:02:08.060 Info TaskManager: Check for plugin updates Completed after 0 minute(s) and 1 seconds
2024-04-20 23:02:34.793 Debug XmlSerializer: Deserializing file /config/config/users/302b26036e1e41fb8db8f27eca7
a29dc/policy.xml
2024-04-20 23:02:34.805 Debug XmlSerializer: Deserializing file /config/config/users/f9a56fa9f0204fdeb72f5e839af
c1cd3/config.xml
2024-04-20 23:02:34.837 Debug XmlSerializer: Deserializing file /config/config/users/302b26036e1e41fb8db8f27eca7
a29dc/config.xml


it sounds like we need a full on debugger so we can attach to the process and see what it is is waiting for and inspect variables to see if the web server is indeed up - perhaps the code is in the state where it believes the web server is up and it is not.

a reminder I am on the latest release: v4.8.4

I appreciate all your help in getting my server back up and running 🙏🏼

Edited by dance4ever
dance4ever

dance4ever 11

Posted
  • Author
Posted (edited)

actually I did a grep on all the Debug statements and don’t understand what this means: 

2024-04-20 23:02:04.101 Debug App: Ping test result to http://192.168.0.100:8097/system/ping. Success: False An 
error occurred while sending the request

”Success” and “False” in the same statement 🤪

EDIT: I can only assume it means that ping was “successful” executing but the result returned was a failure :)  it sounds like the same result as the wget statement above - but shouldn’t it be http://172.24.0.2:8096 inside the container? 🤔

Edited by dance4ever
dance4ever

dance4ever 11

Posted
  • Author
Posted

ok I removed from `system.xml`

  <LocalNetworkAddresses>
    <string>192.168.0.100</string>
  </LocalNetworkAddresses>

and now we get:

2024-04-20 23:18:23.446 Debug App: Ping test result to http://172.30.0.2:8097/system/ping. Success: True

new internal IP as the container was restarted.   Does this mean the web server is up?  is system/ping a page on Emby’s web server?

I guess this is progress but the wget statement still fails:

$ wget http://192.168.0.100:8097
--2024-04-20 16:21:50--  http://192.168.0.100:8097/
Connecting to 192.168.0.100:8097... failed: Connection refused.

 

Happy2Play

Happy2Play 9142

Posted
Posted

According to Emby this is your address. 

2024-04-20 00:20:00.533 Info NetworkManager: Detecting local network addresses
2024-04-20 00:20:00.534 Info NetworkManager: networkInterface: Ethernet eth0, Speed: 10000000000, Description: eth0
2024-04-20 00:20:00.534 Info NetworkManager: GatewayAddresses: 172.24.0.1
2024-04-20 00:20:00.535 Info NetworkManager: UnicastAddresses: 172.24.0.2
2024-04-20 00:20:00.535 Info NetworkManager: networkInterface: Loopback lo, Speed: -1, Description: lo
2024-04-20 00:20:00.535 Info NetworkManager: GatewayAddresses: 
2024-04-20 00:20:00.535 Info NetworkManager: UnicastAddresses: 127.0.0.1
2024-04-20 00:20:00.602 Info NetworkManager: Detected local ip addresses: [{"IPAddress":"172.24.0.2","HasGateWayAddress":true,"PrefixLength":16,"IPv4Mask":"255.255.0.0"},{"IPAddress":"127.0.0.1","HasGateWayAddress":false,"PrefixLength":8,"IPv4Mask":"255.0.0.0"}]

 

Q-Droid

Q-Droid 830

Posted
Posted (edited)

What container image are you using? The official Emby container has netstat (not nestat) and wget.

The possible confusion with hostname and IP addresses inside and outside of the container is also why I suggested you use the commands I gave.

wget http://`hostname`:<port>/web/index.html

The `hostname` portion, with backticks (`) will return the name of the host and resolve to IP correctly. Whether in the shell on the OS or a shell inside the container.

 

Edited by Q-Droid
dance4ever

dance4ever 11

Posted
  • Author
Posted (edited)
3 minutes ago, Q-Droid said:

What container image are you using? The official Emby container has netstat (not nestat) and wget.

 

oh Ill switch back to the official container & report back. I had switched to the linuxserver.io one since it's the one CasaOS defaults to & was cleaning up clutter.

Edited by dance4ever
Q-Droid

Q-Droid 830

Posted
Posted
1 minute ago, dance4ever said:

oh Ill switch back to the official container & report back. I had switched to the linuxserver.io one since it's the one CasaOS defaults to & was cleaning up clutter.

Adding my update here in case my edit is missed.

The possible confusion with hostname and IP addresses inside and outside of the container is also why I suggested you use the commands I gave.

wget http://`hostname`:<port>/web/index.html

The `hostname` portion, with backticks (`) will return the name of the host and resolve to IP correctly. Whether in the shell on the OS or a shell inside the container for the virtual host and IP.

 

Q-Droid

Q-Droid 830

Posted
Posted

A small adjustment to the wget command for better repeatability.

wget http://`hostname`:<port>/web/index.html -O -

  • Like 1
  • Solution
dance4ever

dance4ever 11

Posted
  • Author
  • Solution
Posted (edited)

WE HAVE LIFTOFF! 🚀

Thank you for all your help troubleshooting - by isolating that the web server is alive in the container, I discovered because I was migrating this instance from macOS (not using docker) to Ubuntu Server (using docker and mapping in the compose file) - I needed to take out the mapping in the configuration. 

  <PublicPort>8097</PublicPort>
  <PublicHttpsPort>8921</PublicHttpsPort>
  <HttpServerPortNumber>8097</HttpServerPortNumber>
  <HttpsPortNumber>8921</HttpsPortNumber>

This explains why when you nuke the directories, the container comes up just fine because the server falls back to 8096.

This was one of the pain points I had administrating on macOS and I’m soooo happy that docker files take care of the remapping and you no longer need to do the dance to get the stars aligned.

Consider this case closed and you’re the champ! 💪🏼

 

Edited by dance4ever
  • Thanks 1
dance4ever

dance4ever 11

Posted
  • Author
Posted (edited)
On 4/19/2024 at 6:55 PM, Q-Droid said:

It looks like you changed your port from the default. The server is running but you might be trying to connect to the wrong port?

 

@Q-Droidcan I change this to the solution? :)  I’m realizing you were right all along.  Now that I have a better understanding of how Docker networking works, I failed to understand you were referring to the internal port Emby is serving on vs the intended public port outside the container - my mistake.

what caused the issue is the docker file expecting to map the default port internally (8096) to a custom public port (8097) (in my case, to allow multiple emby servers to serve different libraries).  thanks again for showing me how to isolate this w netstat and wget.

Edited by dance4ever
  • Thanks 1
Q-Droid

Q-Droid 830

Posted
Posted

It's your call. Whichever answer you think could best help others. 

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
 Share
Go to topic listing
×
×
  • Create New...