tipex 2 Posted March 18, 2014 Posted March 18, 2014 Hi, in the past I used only one NAS (6TB) to store movies and shows. Everthing was working fine. Since I moved some of the media to a local HDD, I get sometimes the message that the item is off-line. Only for media on NAS. After I rebooted the system everything is fine. When the system goes to sleep mode and is coming back, it's more or less a fifty-fifty chance that I can play media from NAS. The NAS goes also to sleep mode and needs some seconds for wake-up. At the moment I have to restart the service that I can play the media. Going to the dashboard and start the library scan doesn't work. Is there a trick, except buying a second NAS? Regards and thank you for help. Server 3.0.5190.18410
tipex 2 Posted March 20, 2014 Author Posted March 20, 2014 Has nobody an idea or solution? Am I the only one with this problem.
Luke 42078 Posted March 20, 2014 Posted March 20, 2014 Can you post a server log of the library scan?
tipex 2 Posted March 21, 2014 Author Posted March 21, 2014 On Saturday I have time for it. I come back to you. 1
bigrizz 1 Posted March 24, 2014 Posted March 24, 2014 I'm having a simiar problem. I have been running MB3 happily for months and suddenly, I cannot access media on a local drive. I have created and MB3 Server that has a network path to my local hard drive. I can access the media and play it through the web client. It plays fine with WMP locally, I can happily browse to the media folder. But when I try to access any movies stored in the particular media folder from within MB3 Classic using WMC on my Windows 8.1 client, I get 'cannot play - item is off-line'. Oddly, another directory on the same local drive is also mapped to a colection on the server and I can access this without issue. I tried removing the folder and re-adding it with no success. Everything else seems to work fine. I'm using MB3 Server Version 3.0.5192.19560 and MB3 Classic client 3.0.142.0 3-18.1, I've rebooted, restarted MB3, restarted WMC etc. No go. Any help would be appreciated.
ebr 16184 Posted March 24, 2014 Posted March 24, 2014 Did you define the path to the server either with a UNC path or use the path substitution feature? A log is almost always required to provide much help. In this case, the MBC log when you get that error.
tipex 2 Posted March 24, 2014 Author Posted March 24, 2014 I guess you need translation for: "Der Netzwerkpfad wurde nicht gefunden" -> "The network path was not found"
ebr 16184 Posted March 24, 2014 Posted March 24, 2014 I solved it for now by disabling in the server the media library scan but now I need to maually scan once in a while to see new media appear. Why not just remove the "Wake from sleep" trigger and keep a periodic one. Then you don't have to do it manually.
Pirlo1966 22 Posted March 24, 2014 Posted March 24, 2014 Why not just remove the "Wake from sleep" trigger and keep a periodic one. Then you don't have to do it manually. Like "On an interval - every hour" ? Or will that setting also start a scan as soon as MB server is launched?
ebr 16184 Posted March 24, 2014 Posted March 24, 2014 Yes, an interval. Are you actually shutting down the machine/server, or just letting it sleep?
ebr 16184 Posted March 24, 2014 Posted March 24, 2014 Letting it sleep. S5 I believe. Then you should be able to just remove the trigger to scan on wake. 1
tipex 2 Posted March 24, 2014 Author Posted March 24, 2014 Sorry, during the week the NAS was running whole the time ... Today I got the message again. I'm using UNC like "\\kino\filme\a", I didn't set up path substitution. Today library scan stucks at 40.4% fo a long time ... but finally it finished. server-63531218553.zip
Luke 42078 Posted March 25, 2014 Posted March 25, 2014 well i might need you to translate some of the errors but i can already see we're having difficulty accessing your nas. when we do that we consider the media offline. 2014-03-24 17:04:48.2176 Error - App: Error resolving path \\kino\filme\#-9 Der Netzwerkpfad wurde nicht gefunden. System.IO.IOException 2014-03-24 17:04:48.2176 Error - App: Error resolving path \\kino\filme\a Der Netzwerkpfad wurde nicht gefunden. System.IO.IOException 2014-03-24 17:04:48.2176 Error - App: Error resolving path \\kino\filme\b Der Netzwerkpfad wurde nicht gefunden. The server is unable to access those locations.
Pirlo1966 22 Posted March 25, 2014 Posted March 25, 2014 Yes, an interval. Are you actually shutting down the machine/server, or just letting it sleep? Letting it sleep. S5 I believe.
Pirlo1966 22 Posted March 25, 2014 Posted March 25, 2014 Well I had similar problems. Since a few weeks I often got the message that an item was offline. The reason is that when we wanna watch a movie we wake from sleep both the HTPC and the NAS with the actual media. HTPCs starts up in seconds, the NAS needs about 60 seconds. Therefore it seems that the server running on the htpc cannot find the path to the nas and concludes the media to be offline. Once we bet the offline message we need to restart mediabrowser in order to be able to launch the media. Is it really not possible to delay the media scanning for let's say a minute or so. Why the hurry? I guess there a lot of NAS users out there who do wake their media from sleep. I solved it for now by disabling in the server the media library scan but now I need to maually scan once in a while to see new media appear. Is it not possible to scan by default for new media only after a minute or so or to add a trigger "at application startup but delayed for xx seconds".
tipex 2 Posted March 26, 2014 Author Posted March 26, 2014 Why not just remove the "Wake from sleep" trigger and keep a periodic one. Then you don't have to do it manually. is this also the solution for my Problem?
ebr 16184 Posted March 26, 2014 Posted March 26, 2014 is this also the solution for my Problem? Can't be sure but it is worth a try.
tipex 2 Posted April 5, 2014 Author Posted April 5, 2014 Unfortunately not. It's still offline after wake-up.
tipex 2 Posted May 30, 2014 Author Posted May 30, 2014 Hi, I still have the problem that the content from NAS is offline after wake up. Has somebody a solution for this issue? Can it be fixed with next release?
throgmorton 96 Posted July 15, 2016 Posted July 15, 2016 I'm having a similar issue, where all my media is on a NAS which is put to sleep while I'm at the office or sleeping, while Emby Server is basically on 24/7. Now when its up and functional and I browse to any movie or show it gives me the same error can't play as item is offline. Now from what I've seen if I run the clean database task followed by the scan media task this fixes the problem. So from what I gather there must be something that is switching the flag in the DB to offline. So I'm trying to understand if this is a scheduled task or some other feature like realtime monitoring that goes off when the NAS is sleeping and then switches basically all the movies and shows to offline. I have already switched over the tasks like scan media and clean database to only go off when the NAS is up like once a day at like midnight. But would things like subtitle downloading and chapter extraction also cause this offline flag to be set?
throgmorton 96 Posted July 15, 2016 Posted July 15, 2016 Where do you get this error? Basically when I'm in Emby For WMC I click play and it pops up CANNOT PLAY Item is offline. I'm guessing it's coming from the application.cs from this code as this is the exact statement it says: if (item.BaseItem.LocationType == LocationType.Offline) { if (!Directory.Exists(Path.GetDirectoryName(item.Path) ?? "")) { DisplayDialog("Item is off-line.", "Cannot Play"); return; } else { item.BaseItem.LocationType = LocationType.FileSystem; item.BaseItem.IsOffline = false; } } Not sure what sets the LocationType but maybe some background process on the server goes off when my NASs are sleeping and see that it doesn't exist anymore so switches it to offline...
Jack Burton 98 Posted July 15, 2016 Posted July 15, 2016 When looking at the movies/tv list, is there a red "offline" tag on the poster?
ebr 16184 Posted July 16, 2016 Posted July 16, 2016 Throg, that means that your library scan must be running when the drives are not available. However, as you can see in the code you posted, I do test at the time of playback and only deny it if the location is still not available at that time...
throgmorton 96 Posted July 16, 2016 Posted July 16, 2016 Throg, that means that your library scan must be running when the drives are not available. However, as you can see in the code you posted, I do test at the time of playback and only deny it if the location is still not available at that time... I figured that was the issue originally so I had set the scan to go off at 11pm several hours before the NASs shut down (3am). From manually running the media scan it seems to only take like 5 minutes or so, but I've looked a little bit closer at the server logs to see what is happening. I see its starting as suppose to and finished like a minute and 19 seconds later. 2016-07-15 23:00:00.0109 Info TaskManager: DailyTrigger fired for task: Scan media library 2016-07-15 23:00:00.0109 Info TaskManager: Queueing task RefreshMediaLibraryTask 2016-07-15 23:00:00.0109 Info TaskManager: Executing Scan media library 2016-07-15 23:00:00.0109 Info App: Validating media library 2016-07-15 23:00:51.4335 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: 2016-07-15 23:00:51.4335 Info HttpServer: HTTP Response 200 to 192.168.1.155. Time: 0ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml 2016-07-15 23:01:19.9254 Info TaskManager: Scan media library Completed after 1 minute(s) and 19 seconds 2016-07-15 23:01:19.9254 Info TaskManager: ExecuteQueuedTasks 2016-07-15 23:01:20.9957 Info TaskManager: Daily trigger for Scan media library set to fire at 7/16/2016 11:00:00 PM, which is 1438.65007121833 minutes from now. 2016-07-15 23:21:01.4487 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: 2016-07-15 23:21:01.4487 Info HttpServer: HTTP Response 200 to 192.168.1.155. Time: 0ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml 2016-07-15 23:41:10.4387 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: 2016-07-15 23:41:10.4387 Info HttpServer: HTTP Response 200 to 192.168.1.155. Time: 5ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml 2016-07-15 23:56:52.4936 Info HttpClient: HttpClientManager GET: http://192.168.1.25:10184/ 2016-07-15 23:56:52.4936 Info HttpClient: HttpClientManager GET: http://192.168.1.25:10184/ 2016-07-15 23:56:52.5136 Info HttpClient: HttpClientManager GET: http://192.168.1.25:10184/MediaRenderer_RenderingControl/scpd.xml 2016-07-15 23:56:52.5336 Info HttpClient: HttpClientManager GET: http://192.168.1.25:10184/MediaRenderer_AVTransport/scpd.xml 2016-07-15 23:56:52.5336 Info HttpClient: HttpClientManager GET: http://192.168.1.25:10184/MediaRenderer_RenderingControl/scpd.xml 2016-07-15 23:56:52.5436 Info HttpClient: HttpClientManager GET: http://192.168.1.25:10184/MediaRenderer_AVTransport/scpd.xml 2016-07-15 23:56:52.5686 Info Dlna: DLNA Session created for WDTVLiveHub - WD TV Live Hub 2016-07-15 23:57:24.2463 Info HttpClient: HttpClientManager GET: http://192.168.1.25:10184/ 2016-07-15 23:57:24.2613 Info HttpClient: HttpClientManager GET: http://192.168.1.25:10184/MediaRenderer_RenderingControl/scpd.xml 2016-07-15 23:57:24.2613 Info HttpClient: HttpClientManager GET: http://192.168.1.25:10184/MediaRenderer_AVTransport/scpd.xml 2016-07-15 23:57:24.2963 Info Dlna: DLNA Session created for WDTVLiveHub - WD TV Live Hub 2016-07-15 23:58:27.0616 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com 2016-07-15 23:58:27.4517 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=6c81740455ad31a477b5f66f9beb05b8 2016-07-15 23:58:27.6568 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=6c81740455ad31a477b5f66f9beb05b8 2016-07-15 23:58:30.4024 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: FDSSDP 2016-07-15 23:58:30.4024 Info HttpServer: HTTP Response 200 to 192.168.1.30. Time: 0ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml 2016-07-15 23:58:32.3379 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: DAFUPnP 2016-07-15 23:58:32.3379 Info HttpServer: HTTP Response 200 to 192.168.1.30. Time: 0ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml 2016-07-15 23:58:32.3579 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0 2016-07-15 23:58:32.3579 Info HttpServer: HTTP Response 200 to 192.168.1.30. Time: 0ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml 2016-07-15 23:58:32.3729 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/icons/logo240.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50 2016-07-15 23:58:32.3729 Info HttpServer: HTTP Response 200 to 192.168.1.30. Time: 5ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/icons/logo240.png 2016-07-15 23:58:32.3729 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/icons/logo240.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50 2016-07-15 23:58:32.3729 Info HttpServer: HTTP Response 200 to 192.168.1.30. Time: 0ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/icons/logo240.jpg 2016-07-15 23:58:32.3929 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/icons/logo120.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50 2016-07-15 23:58:32.3929 Info HttpServer: HTTP Response 200 to 192.168.1.30. Time: 0ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/icons/logo120.png 2016-07-15 23:58:32.3929 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/icons/logo120.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50 2016-07-15 23:58:32.3929 Info HttpServer: HTTP Response 200 to 192.168.1.30. Time: 0ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/icons/logo120.jpg 2016-07-15 23:58:32.4029 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/icons/logo48.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50 2016-07-15 23:58:32.4029 Info HttpServer: HTTP Response 200 to 192.168.1.30. Time: 0ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/icons/logo48.png 2016-07-15 23:58:32.4029 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/icons/logo48.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50 2016-07-15 23:58:32.4029 Info HttpServer: HTTP Response 200 to 192.168.1.30. Time: 0ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/icons/logo48.jpg 2016-07-15 23:58:32.4029 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/contentdirectory/contentdirectory.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0 2016-07-15 23:58:32.4029 Info HttpServer: HTTP Response 200 to 192.168.1.30. Time: 0ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/contentdirectory/contentdirectory.xml 2016-07-15 23:58:33.3782 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: DAFUPnP But then I get all these other INFO stuff happening right up till 3am when my NASs shut down.... 2016-07-16 02:56:33.3851 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/icons/logo48.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50 2016-07-16 02:56:33.3851 Info HttpServer: HTTP Response 200 to 192.168.1.30. Time: 1ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/icons/logo48.jpg 2016-07-16 02:56:33.4051 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/contentdirectory/contentdirectory.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0 2016-07-16 02:56:33.4051 Info HttpServer: HTTP Response 200 to 192.168.1.30. Time: 0ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/contentdirectory/contentdirectory.xml 2016-07-16 02:58:15.7371 Error MediaEncoder: ffmpeg image extraction failed for file:"\\192.168.1.200\movies\..." 2016-07-16 02:58:15.7371 Error MediaEncoder: I-frame image extraction failed, will attempt standard way. Input: file:"\\192.168.1.200\movies\..." 2016-07-16 02:58:15.7791 Error MediaEncoder: ffmpeg image extraction failed for file:"\\192.168.1.200\movies\..." 2016-07-16 02:58:15.7791 Error App: Error extracting chapter images for \\192.168.1.200\movies\... *** Error Report *** Version: 3.0.5986.0 Command line: C:\Users\Robert Hobbins\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Operating system: Microsoft Windows NT 6.2.9200.0 Processor count: 8 64-Bit OS: True 64-Bit Process: True Program data path: C:\Users\Robert Hobbins\AppData\Roaming\Emby-Server Application Path: C:\Users\Robert Hobbins\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe ffmpeg image extraction failed for file:"\\192.168.1.200\movies\..." System.ApplicationException at MediaBrowser.MediaEncoding.Encoder.MediaEncoder.<ExtractImageInternal>d__37.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.MediaEncoding.Encoder.MediaEncoder.<ExtractImage>d__30.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Server.Implementations.MediaEncoder.EncodingManager.<RefreshChapterImages>d__0.MoveNext() I'm not sure if its the Refresh People which is causing it based on this segment of the log, which is set to fire off daily at 1am and maybe its taking way longer than I think and is still going when my NASs shut down causing things like Clean database (triggered at 1am, but actually went off at 3am) to go off after my NASs are shutdown. 2016-07-16 02:58:46.3245 Info App: People validation complete 2016-07-16 02:58:46.4166 Info TaskManager: Refresh people Completed after 0 minute(s) and 18 seconds 2016-07-16 02:58:46.4166 Info TaskManager: ExecuteQueuedTasks 2016-07-16 02:58:46.4876 Info TaskManager: Executing Clean Database 2016-07-16 02:58:47.4958 Info TaskManager: Daily trigger for Refresh people set to fire at 7/17/2016 1:00:00 AM, which is 1321.20840199667 minutes from now. 2016-07-16 02:59:21.8562 Info TaskManager: IntervalTrigger fired for task: Convert media 2016-07-16 02:59:21.8562 Info TaskManager: Queueing task SyncConvertScheduledTask 2016-07-16 03:02:50.4331 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: 2016-07-16 03:02:50.4331 Info HttpServer: HTTP Response 200 to 192.168.1.155. Time: 2ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml 2016-07-16 03:03:23.2081 Info TaskManager: Setting SuspendTriggers to False 2016-07-16 03:03:23.2081 Info TaskManager: Clean Database Completed after 4 minute(s) and 36 seconds 2016-07-16 03:03:23.2081 Info TaskManager: ExecuteQueuedTasks 2016-07-16 03:03:23.2931 Info TaskManager: Executing Convert media 2016-07-16 03:03:23.2931 Info TaskManager: Convert media Completed after 0 minute(s) and 0 seconds 2016-07-16 03:03:23.2931 Info TaskManager: ExecuteQueuedTasks 2016-07-16 03:03:24.2944 Info TaskManager: Daily trigger for Clean Database set to fire at 7/17/2016 2:00:00 AM, which is 1376.59509304333 minutes from now. 2016-07-16 03:23:00.4363 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: 2016-07-16 03:23:00.4363 Info HttpServer: HTTP Response 200 to 192.168.1.155. Time: 2ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml 2016-07-16 03:43:10.4306 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: 2016-07-16 03:43:10.4326 Info HttpServer: HTTP Response 200 to 192.168.1.155. Time: 2ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml 2016-07-16 04:03:21.4371 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: 2016-07-16 04:03:21.4371 Info HttpServer: HTTP Response 200 to 192.168.1.155. Time: 2ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml 2016-07-16 04:23:31.4413 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: 2016-07-16 04:23:31.4413 Info HttpServer: HTTP Response 200 to 192.168.1.155. Time: 1ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml 2016-07-16 04:43:40.4293 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: 2016-07-16 04:43:40.4323 Info HttpServer: HTTP Response 200 to 192.168.1.155. Time: 3ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml 2016-07-16 05:03:51.4188 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: 2016-07-16 05:03:51.4188 Info HttpServer: HTTP Response 200 to 192.168.1.155. Time: 2ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml 2016-07-16 05:24:00.4268 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: 2016-07-16 05:24:00.4268 Info HttpServer: HTTP Response 200 to 192.168.1.155. Time: 2ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml 2016-07-16 05:44:10.4260 Info HttpServer: HTTP GET http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml. UserAgent: 2016-07-16 05:44:10.4260 Info HttpServer: HTTP Response 200 to 192.168.1.155. Time: 2ms. http://192.168.1.155:8096/dlna/a517ad27ca130ecae3a8822447c8487a/description.xml 2016-07-16 05:58:27.0760 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com 2016-07-16 05:58:27.4661 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=6c81740455ad31a477b5f66f9beb05b8 2016-07-16 05:58:27.6242 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=6c81740455ad31a477b5f66f9beb05b8 2016-07-16 05:59:21.0592 Info TaskManager: IntervalTrigger fired for task: Refresh Guide 2016-07-16 05:59:21.0592 Info TaskManager: Queueing task RefreshChannelsScheduledTask 2016-07-16 05:59:21.0592 Info TaskManager: Executing Refresh Guide 2016-07-16 05:59:21.0592 Info App: Refreshing guide with 14 days of guide data 2016-07-16 05:59:21.0592 Info TaskManager: Refresh Guide Completed after 0 minute(s) and 0 seconds 2016-07-16 05:59:21.0592 Info TaskManager: ExecuteQueuedTasks 2016-07-16 06:03:23.3093 Info TaskManager: IntervalTrigger fired for task: Convert media 2016-07-16 06:03:23.3093 Info TaskManager: Queueing task SyncConvertScheduledTask 2016-07-16 06:03:23.3093 Info TaskManager: Executing Convert media 2016-07-16 06:03:23.3093 Info TaskManager: Convert media Completed after 0
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