Jump to content

AFTV: VolleyError com.android.TimeoutError


Tanamur

Recommended Posts

Tanamur

Platform: NUC i5,16GB RAM, Win10 Pro, Gigabit Wired, Internet 10mbit/s Fiber UP/DOWN

Platform: AFTV-GEN1, 0S5.0.5.1, Gigabit Wired Edit: Correction-AFTV Gen1&2 ports are only 10/100mbit ports (see here), Internet 10mbit/s Fiber UP/DOWN

Server: Version 3.0.5971.0

AFTV App: 1.1.90

3rd Party App: IMDB IBN People Downloader V2

 

Error: post-442-0-89149600-1464088614_thumb.jpg

Forum/Devs -

 

This error has been occuring for quite some time. When using Emby on my AFTV1 and viewing a movie

library I am given the Option at the bottom to view Suggested, All Items, By Letter, Genres and

Performers. I can view all options with no problem except Performers. When I enter Performers all

image frames freeze their "loading circles" and after about 30 seconds I get the VolleyError (see

pic).

 

I am still able to exit the app but the Volley error keeps appearing in every other app I use

including BBC, NPR, Weather, etc. The only way to get it to stop is to reboot the AFTV1.

After the most recent server upgrade a few days ago, I cleared the cache and data, uninstalled the

app locally and in the cloud then reinstalled from my Amazon account delivery. Still the same

error.

I use IMDB IBN People Downloader V2 to populate the Performers and there is no problem viewing

Performer images throughout the rest of the app.

 

Any suggestions? Everything is wired with gigabit ports so no lags communicating from the AFTV1

to the server.

Thanks, Tanamur

Edited by Tanamur
Link to comment
Share on other sites

Do you use any other apps?

 

This is most likely the server just responding too slowly.

Link to comment
Share on other sites

Tanamur

Hi @@CBers and @@ebr - Attached is the server log in debug mode and a couple more images showing what is happening. I restarted Emby so there would be a clean log. Also, I do have only a few apps loaded on the AFTV1 (BBC, NPR One, Weather, PBS and....Plex).

 

Edit: Let me mention the NUC server is a dedicated media server. Clean install of Win10 Pro (RTM) with SSD System disk and separate internal 1TB HDD for all metadata with custom paths. All libraries are set up with UNC paths. 16GB RAM and hardwired to D-Link DIR-868L Router with gigabit ports and CAT-6 cables. 2x4TB WD External HDD via USB3 for daily content. The server runs Emby, Plex and Newsbin Pro (SB). I think it is a pretty clean config.

 

Here is the sequence I ran through for the log:

 

03:38 2016-05-25
  1. Enable Debug Logging
  2. Restarted Server
  3. Ran Clean Database
  4. Ran Scan Media Library
  5. Started AFTV1 and entered Movies (Recent) Library
  6. Entered Suggested, All Items, By Letter, Genres and Performers.
  7. ~30 secs after entering Performers the VolleyError occurs and the alphabet listing moves forward like it is trying the next block at 30 sec intervals (A-C, D-F, G-I,....X-Z then Empty) - See Photos

server-63599744120.zip

post-442-0-24878600-1464301211_thumb.jpg

post-442-0-25032400-1464301202_thumb.jpg

post-442-0-24908600-1464301193_thumb.jpg

post-442-0-39674300-1464301180_thumb.jpg

post-442-0-45564900-1464301165_thumb.jpg

 

 

post-442-0-48371000-1464301119_thumb.jpg

post-442-0-04625000-1464301154_thumb.jpg

Edited by Tanamur
Link to comment
Share on other sites

The server is simply responding too slowly for whatever reason.  It isn't an app issue.

 

The slowness appears to be across the board too as I saw a 20 second response time to the dashboard reporting on a running scheduled task.

Link to comment
Share on other sites

Tanamur

The server is simply responding too slowly for whatever reason.  It isn't an app issue.

 

The slowness appears to be across the board too as I saw a 20 second response time to the dashboard reporting on a running scheduled task.

 

post-442-0-59644700-1464128637_thumb.png

 

Hi @@ebr - Thanks for the quick reply. Attached is the Task Manager view. I am currently logged into the server via Remote Desktop (RDP) and composing this in MS Edge (just a clean stock install). Radeon's People grabber is running, Newsbin (SB) and 4 tabs in Edge. The server is idling as it appears to me.

 

I will go back and kill:

  1. Plex
  2. MS Edge browser
  3. Newsbin Pro (SB)
  4. Everything other than Emby

I will then retest the error creation process. Any other suggestions on what to kill or do for the test?

 

EDIT: AFTV Gen 1&2 have only 10/100 Mbs ports (see here)

 

EDIT for Results:

 

Okay, with only Emby running everything was completed (Clean Database, Scan Library) and the server was basically idling. Nothing on the CPU or network (see Task Manager below):

5744f4de8dcef_EmbyOnlyPostLibraryScanRea

 

Now, after rebooting the AFTV1 I entered the movie library and entered each of the Suggested, ABC, etc with no problem and browed down into performers in each area and viewed performers with no problem.

 

Next I entered Performers. The Volley error repeated itself just as before. I was monitoring the Task Manager and the CPU went to 100% on all 4 cores and didn't come down until several minutes after all letters

of the Performers was tried and failed.

 

5744f631415e2_EmbyOnlyPerformersAFTVEmby

 

Server log attached server-63599759308.txt

 

Pending your feedback my planned next steps would be:

 

  1. Delete all Libraries and add back small library and test again
  2. Failing positive results, uninstall and reinstall Emby (Emby folder already backed up with all metadata which is NOT stored with content)

 

Thank again for the help, Tanamur

Edited by Tanamur
Link to comment
Share on other sites

waverly360

So, I was getting this exact same error on a significant portion of my Anime episodes...I *just* upgraded to the newest emby-server version tonight, and now I'm not getting an error, but the video isn't playing either.   It looks like ffmpeg is just dying on the video file.  

 

2016-05-24 20:46:10.1746 Info HttpServer: HTTP GET http://192.168.1.90:8096/emby/Users/3e50f851f6214c2a949f09b857d63e12/Items?Years=&IsVirtualUnaired=false&EnableImageTypes=&ArtistIds=&Filters=&Fields=MediaSources,MediaStreams,Path,Chapters,Overview,PrimaryImageAspectRatio&Genres=&MediaTypes=&Ids=&PersonTypes=&recursive=false&ExcludeLocationTypes=&ExcludeItemTypes=&AirDays=&SortBy=SortName&StudioIds=&PersonIds=&ImageTypes=&IncludeItemTypes=Episode&VideoTypes=&LocationTypes=&SeriesStatuses=&MinIndexNumber=10&ParentId=a6510d9d92badfaa85f3754c50cc0076&format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1; AFTM Build/LMY47O)

2016-05-24 20:46:10.8068 Info HttpServer: HTTP Response 200 to 192.168.1.188. Time: 634ms. http://192.168.1.90:8096/emby/Users/3e50f851f6214c2a949f09b857d63e12/Items?Years=&IsVirtualUnaired=false&EnableImageTypes=&ArtistIds=&Filters=&Fields=MediaSources,MediaStreams,Path,Chapters,Overview,PrimaryImageAspectRatio&Genres=&MediaTypes=&Ids=&PersonTypes=&recursive=false&ExcludeLocationTypes=&ExcludeItemTypes=&AirDays=&SortBy=SortName&StudioIds=&PersonIds=&ImageTypes=&IncludeItemTypes=Episode&VideoTypes=&LocationTypes=&SeriesStatuses=&MinIndexNumber=10&ParentId=a6510d9d92badfaa85f3754c50cc0076&format=json

2016-05-24 20:46:13.6563 Info HttpServer: HTTP GET http://192.168.1.90:8096/emby/Items/768ab87259ae73d2c38c247a74e79cf8/PlaybackInfo?UserId=3e50f851f6214c2a949f09b857d63e12&format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1; AFTM Build/LMY47O)

2016-05-24 20:46:13.6945 Info HttpServer: HTTP Response 200 to 192.168.1.188. Time: 39ms. http://192.168.1.90:8096/emby/Items/768ab87259ae73d2c38c247a74e79cf8/PlaybackInfo?UserId=3e50f851f6214c2a949f09b857d63e12&format=json

2016-05-24 20:46:13.8637 Info HttpServer: HTTP GET http://192.168.1.90:8096/emby/Studios/Fuji+TV/Images/Primary?MaxHeight=60&EnableImageEnhancers=true. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1; AFTM Build/LMY47O)

2016-05-24 20:46:13.8703 Info HttpServer: HTTP GET http://192.168.1.90:8096/emby/Items/a6510d9d92badfaa85f3754c50cc0076/Images/Primary?MaxHeight=600&EnableImageEnhancers=true. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1; AFTM Build/LMY47O)

2016-05-24 20:46:13.9356 Info HttpServer: HTTP GET http://192.168.1.90:8096/emby/videos/768ab87259ae73d2c38c247a74e79cf8/stream.mkv?DeviceId=224af64d6f61e88a&MediaSourceId=768ab87259ae73d2c38c247a74e79cf8&VideoCodec=h264&AudioCodec=aac&AudioStreamIndex=2&SubtitleStreamIndex=3&VideoBitrate=14340726&AudioBitrate=128000&MaxAudioChannels=2&PlaySessionId=77ed49b684274239a65c191637408e5f&CopyTimestamps=true&ForceLiveStream=false&SubtitleMethod=Encode. UserAgent: EMVideoView 2.5.6 (25600) / Android 5.1 / AFTM

2016-05-24 20:46:13.9417 Info HttpServer: HTTP Response 304 to 192.168.1.188. Time: 72ms. http://192.168.1.90:8096/emby/Items/a6510d9d92badfaa85f3754c50cc0076/Images/Primary?MaxHeight=600&EnableImageEnhancers=true

2016-05-24 20:46:13.9562 Error DtoUtils: ServiceBase<TRequest>::Service Exception

*** Error Report ***

Version: 3.0.5971.0

Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -restartpath /usr/lib/emby-server/restart.sh

Operating system: Unix 4.2.8.300

Processor count: 64

64-Bit OS: True

64-Bit Process: True

Program data path: /var/lib/emby-server

Mono: 4.2.3 (Stable 4.2.3.4/832de4b Tue Mar 15 11:39:54 EDT 2016)

Application Path: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe

Fuji TV does not have an image of type Primary

MediaBrowser.Common.Extensions.ResourceNotFoundException

  at MediaBrowser.Api.Images.ImageService.GetImage (MediaBrowser.Api.Images.ImageRequest request, IHasImages item, Boolean isHeadRequest) <0x4142ad60 + 0x00993> in <filename unknown>:0 

  at MediaBrowser.Api.Images.ImageService.Get (MediaBrowser.Api.Images.GetItemByNameImage request) <0x41429e60 + 0x00047> in <filename unknown>:0 

  at (wrapper dynamic-method) System.Object:lambda_method (System.Runtime.CompilerServices.Closure,object,object)

  at ServiceStack.Host.ServiceRunner`1[TRequest].Execute (IRequest request, System.Object instance, ServiceStack.Host.TRequest requestDto) <0x41225590 + 0x003d4> in <filename unknown>:0 

 

2016-05-24 20:46:13.9642 Error HttpServer: Error processing request for /emby/Studios/Fuji+TV/Images/Primary?MaxHeight=60&EnableImageEnhancers=true

*** Error Report ***

Version: 3.0.5971.0

Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -restartpath /usr/lib/emby-server/restart.sh

Operating system: Unix 4.2.8.300

Processor count: 64

64-Bit OS: True

64-Bit Process: True

Program data path: /var/lib/emby-server

Mono: 4.2.3 (Stable 4.2.3.4/832de4b Tue Mar 15 11:39:54 EDT 2016)

Application Path: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe

Fuji TV does not have an image of type Primary

ServiceStack.HttpError

No Stack Trace Available

 

2016-05-24 20:46:13.9695 Error NotFoundHttpHandler: 192.168.1.90:8096 Request not found: /emby/Studios/Fuji+TV/Images/Primary?MaxHeight=60&EnableImageEnhancers=true

2016-05-24 20:46:13.9707 Info HttpServer: HTTP Response 404 to 192.168.1.188. Time: 107ms. http://192.168.1.90:8096/emby/Studios/Fuji+TV/Images/Primary?MaxHeight=60&EnableImageEnhancers=true

2016-05-24 20:46:14.0165 Info HttpServer: HTTP POST http://192.168.1.90:8096/emby/Sessions/Playing. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1; AFTM Build/LMY47O)

2016-05-24 20:46:14.0655 Info HttpServer: HTTP Response 204 to 192.168.1.188. Time: 49ms. http://192.168.1.90:8096/emby/Sessions/Playing

2016-05-24 20:46:14.0679 Info App: /var/lib/emby-server/ffmpeg/20160215/ffmpeg -fflags +genpts -i file:"/data/Media/Video/TV/HD/Dragon Ball Kai/Season 1/Dragon Ball Kai - S01E09 - 009 - Yamucha's Struggle! The Terrifying Saibaimen.mkv" -map 0:0 -map 0:2 -codec:v:0 libx264 -force_key_frames expr:gte(t,n_forced*5) -copyts -vf "scale=trunc(min(max(iw\,ih*dar)\,720)/2)*2:trunc(ow/dar/2)*2,subtitles='/data/Media/Video/TV/HD/Dragon Ball Kai/Season 1/Dragon Ball Kai - S01E09 - 009 - Yamucha'\\\''s Struggle! The Terrifying Saibaimen.mkv:si=0'" -avoid_negative_ts disabled -start_at_zero -pix_fmt yuv420p -preset superfast -crf 23 -b:v 929061 -maxrate 929061 -bufsize 1858122 -vsync vfr -map_metadata -1 -threads 0 -codec:a:0 aac -strict experimental -ac 2 -ab 128000 -af "aresample=async=1" -y "/var/lib/emby-server/transcoding-temp/d559ea8d3c882385a9b625b73b0d45da.mkv"

2016-05-24 20:46:14.4491 Debug App: Disposing stream resources

2016-05-24 20:46:14.4530 Info App: FFMpeg exited with code 1

2016-05-24 20:46:16.9162 Info HttpServer: HTTP Response 200 to 192.168.1.188. Time: 2982ms (slow). http://192.168.1.90:8096/emby/videos/768ab87259ae73d2c38c247a74e79cf8/stream.mkv?DeviceId=224af64d6f61e88a&MediaSourceId=768ab87259ae73d2c38c247a74e79cf8&VideoCodec=h264&AudioCodec=aac&AudioStreamIndex=2&SubtitleStreamIndex=3&VideoBitrate=14340726&AudioBitrate=128000&MaxAudioChannels=2&PlaySessionId=77ed49b684274239a65c191637408e5f&CopyTimestamps=true&ForceLiveStream=false&SubtitleMethod=Encode

2016-05-24 20:46:17.6028 Info HttpServer: HTTP POST http://192.168.1.90:8096/emby/Sessions/Playing/Stopped. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1; AFTM Build/LMY47O)

2016-05-24 20:46:17.6057 Debug App: ReportPlaybackStopped PlaySessionId: 77ed49b684274239a65c191637408e5f

2016-05-24 20:46:17.6113 Debug App: KillTranscodingJob - JobId a5bd2651065f4aef90dbb61eb8f5af89 PlaySessionId 77ed49b684274239a65c191637408e5f. Killing transcoding

2016-05-24 20:46:17.6144 Info App: Deleting partial stream file(s) /var/lib/emby-server/transcoding-temp/d559ea8d3c882385a9b625b73b0d45da.mkv

2016-05-24 20:46:17.6465 Debug ProviderManager: Saving /data/Media/Video/TV/HD/Dragon Ball Kai/Season 1/Dragon Ball Kai - S01E09 - 009 - Yamucha's Struggle! The Terrifying Saibaimen.mkv to Nfo.

2016-05-24 20:46:17.6515 Info HttpServer: HTTP Response 204 to 192.168.1.188. Time: 49ms. http://192.168.1.90:8096/emby/Sessions/Playing/Stopped

 

 

 

if I play the same media file through the Emby web interface it works fine and I get the following logs:

 

2016-05-24 20:50:24.5661 Info HttpServer: HTTP GET http://192.168.1.90:8096/emby/Users/3e50f851f6214c2a949f09b857d63e12/Items/768ab87259ae73d2c38c247a74e79cf8. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

2016-05-24 20:50:24.6035 Info HttpServer: HTTP Response 200 to 192.168.1.185. Time: 38ms. http://192.168.1.90:8096/emby/Users/3e50f851f6214c2a949f09b857d63e12/Items/768ab87259ae73d2c38c247a74e79cf8

2016-05-24 20:50:24.6100 Info HttpServer: HTTP GET http://192.168.1.90:8096/emby/Shows/b9fcec453c089e7783936b59d12295e8/Episodes?IsVirtualUnaired=false&IsMissing=false&UserId=3e50f851f6214c2a949f09b857d63e12&Fields=MediaSources,Chapters. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

2016-05-24 20:50:24.8518 Info HttpServer: HTTP Response 200 to 192.168.1.185. Time: 242ms. http://192.168.1.90:8096/emby/Shows/b9fcec453c089e7783936b59d12295e8/Episodes?IsVirtualUnaired=false&IsMissing=false&UserId=3e50f851f6214c2a949f09b857d63e12&Fields=MediaSources,Chapters

2016-05-24 20:50:24.9107 Info HttpServer: HTTP GET http://192.168.1.90:8096/emby/Users/3e50f851f6214c2a949f09b857d63e12/Items/768ab87259ae73d2c38c247a74e79cf8/Intros. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

2016-05-24 20:50:24.9664 Info HttpServer: HTTP Response 200 to 192.168.1.185. Time: 56ms. http://192.168.1.90:8096/emby/Users/3e50f851f6214c2a949f09b857d63e12/Items/768ab87259ae73d2c38c247a74e79cf8/Intros

2016-05-24 20:50:24.9717 Info HttpServer: HTTP GET http://192.168.1.90:8096/emby/Playback/BitrateTest?Size=1000000. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

2016-05-24 20:50:24.9904 Info HttpServer: HTTP GET http://192.168.1.90:8096/emby/Playback/BitrateTest?Size=2400000. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

2016-05-24 20:50:24.9907 Info HttpServer: HTTP Response 200 to 192.168.1.185. Time: 19ms. http://192.168.1.90:8096/emby/Playback/BitrateTest?Size=1000000

2016-05-24 20:50:25.1666 Info HttpServer: HTTP POST http://192.168.1.90:8096/emby/Items/768ab87259ae73d2c38c247a74e79cf8/PlaybackInfo?UserId=3e50f851f6214c2a949f09b857d63e12&StartTimeTicks=0. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

2016-05-24 20:50:25.2075 Info App: Profile: Unknown Profile, Path: /data/Media/Video/TV/HD/Dragon Ball Kai/Season 1/Dragon Ball Kai - S01E09 - 009 - Yamucha's Struggle! The Terrifying Saibaimen.mkv, isEligibleForDirectPlay: True, isEligibleForDirectStream: True

2016-05-24 20:50:25.2176 Info App: Profile: Unknown Profile, No direct play profiles found for Path: /data/Media/Video/TV/HD/Dragon Ball Kai/Season 1/Dragon Ball Kai - S01E09 - 009 - Yamucha's Struggle! The Terrifying Saibaimen.mkv

2016-05-24 20:50:25.2402 Info App: Profile: Unknown Profile, Path: /data/Media/Video/TV/HD/Dragon Ball Kai/Season 1/Dragon Ball Kai - S01E09 - 009 - Yamucha's Struggle! The Terrifying Saibaimen.mkv, isEligibleForDirectPlay: True, isEligibleForDirectStream: True

2016-05-24 20:50:25.2402 Info App: Profile: Unknown Profile, No direct play profiles found for Path: /data/Media/Video/TV/HD/Dragon Ball Kai/Season 1/Dragon Ball Kai - S01E09 - 009 - Yamucha's Struggle! The Terrifying Saibaimen.mkv

2016-05-24 20:50:25.2407 Info App: Profile: Unknown Profile, Path: /data/Media/Video/TV/HD/Dragon Ball Kai/Season 1/Dragon Ball Kai - S01E09 - 009 - Yamucha's Struggle! The Terrifying Saibaimen.mkv, isEligibleForDirectPlay: True, isEligibleForDirectStream: True

2016-05-24 20:50:25.2407 Info App: Profile: Unknown Profile, No direct play profiles found for Path: /data/Media/Video/TV/HD/Dragon Ball Kai/Season 1/Dragon Ball Kai - S01E09 - 009 - Yamucha's Struggle! The Terrifying Saibaimen.mkv

2016-05-24 20:50:25.2568 Info HttpServer: HTTP Response 200 to 192.168.1.185. Time: 91ms. http://192.168.1.90:8096/emby/Items/768ab87259ae73d2c38c247a74e79cf8/PlaybackInfo?UserId=3e50f851f6214c2a949f09b857d63e12&StartTimeTicks=0

2016-05-24 20:50:25.4380 Info HttpServer: HTTP Response 200 to 192.168.1.185. Time: 448ms. http://192.168.1.90:8096/emby/Playback/BitrateTest?Size=2400000

2016-05-24 20:50:25.5818 Info HttpServer: HTTP GET http://192.168.1.90:8096/emby/Items/b9fcec453c089e7783936b59d12295e8/Images/Backdrop/0?maxWidth=2560&tag=e0ae0e065dffe03025da357cac2faf4e&quality=80. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

2016-05-24 20:50:25.5818 Info HttpServer: HTTP GET http://192.168.1.90:8096/emby/Items/b9fcec453c089e7783936b59d12295e8/Images/Logo?height=42&tag=c79639133bebd8b0e10487e126d77c2e&quality=90. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

2016-05-24 20:50:25.5818 Info HttpServer: HTTP GET http://192.168.1.90:8096/emby/Items/b9fcec453c089e7783936b59d12295e8/Images/Primary?width=400&tag=43cb56362c7ccba3b25a327173f93751&quality=90. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

2016-05-24 20:50:25.5995 Info HttpServer: HTTP Response 200 to 192.168.1.185. Time: 18ms. http://192.168.1.90:8096/emby/Items/b9fcec453c089e7783936b59d12295e8/Images/Primary?width=400&tag=43cb56362c7ccba3b25a327173f93751&quality=90

2016-05-24 20:50:25.6058 Info HttpServer: HTTP Response 200 to 192.168.1.185. Time: 24ms. http://192.168.1.90:8096/emby/Items/b9fcec453c089e7783936b59d12295e8/Images/Logo?height=42&tag=c79639133bebd8b0e10487e126d77c2e&quality=90

2016-05-24 20:50:25.8879 Info HttpServer: HTTP Response 200 to 192.168.1.185. Time: 307ms. http://192.168.1.90:8096/emby/Items/b9fcec453c089e7783936b59d12295e8/Images/Backdrop/0?maxWidth=2560&tag=e0ae0e065dffe03025da357cac2faf4e&quality=80

2016-05-24 20:50:25.8887 Info HttpServer: HTTP GET http://192.168.1.90:8096/emby/Videos/768ab87259ae73d2c38c247a74e79cf8/768ab87259ae73d2c38c247a74e79cf8/Subtitles/3/0/Stream.vtt. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

2016-05-24 20:50:25.8916 Info HttpServer: HTTP GET http://192.168.1.90:8096/emby/videos/768ab87259ae73d2c38c247a74e79cf8/stream.mkv?DeviceId=bd63f8dc5e5636ca9ca68641db504dfe&MediaSourceId=768ab87259ae73d2c38c247a74e79cf8&VideoCodec=h264&AudioCodec=mp3&AudioStreamIndex=2&VideoBitrate=210282959&AudioBitrate=128000&MaxAudioChannels=6&Level=51&Profile=high&PlaySessionId=0ffbb30754f14251af3f26fbf322309d&CopyTimestamps=true&ForceLiveStream=false. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

2016-05-24 20:50:25.8998 Info App: /var/lib/emby-server/ffmpeg/20160215/ffmpeg -fflags +genpts -i file:"/data/Media/Video/TV/HD/Dragon Ball Kai/Season 1/Dragon Ball Kai - S01E09 - 009 - Yamucha's Struggle! The Terrifying Saibaimen.mkv" -map 0:0 -map 0:2 -map -0:s -codec:v:0 libx264 -force_key_frames expr:gte(t,n_forced*5) -vf "scale=trunc(min(max(iw\,ih*dar)\,720)/2)*2:trunc(ow/dar/2)*2" -copyts -avoid_negative_ts disabled -start_at_zero -pix_fmt yuv420p -preset superfast -crf 23 -b:v 929061 -maxrate 929061 -bufsize 1858122 -vsync vfr -profile:v high -level 51 -map_metadata -1 -threads 0 -codec:a:0 libmp3lame -ac 2 -ab 128000 -af "aresample=async=1" -y "/var/lib/emby-server/transcoding-temp/95d94f9a7ca3d4038c013ebd77e1d7c5.mkv"

2016-05-24 20:50:25.9625 Info SubtitleEncoder: /var/lib/emby-server/ffmpeg/20160215/ffmpeg -i file:"/data/Media/Video/TV/HD/Dragon Ball Kai/Season 1/Dragon Ball Kai - S01E09 - 009 - Yamucha's Struggle! The Terrifying Saibaimen.mkv" -map 0:3 -an -vn -c:s copy "/var/lib/emby-server/data/subtitles/e/e27032d0-9c25-8f5a-998e-0167a6c365b2.srt"

2016-05-24 20:50:26.5957 Info SubtitleEncoder: ffmpeg subtitle extraction completed for file:"/data/Media/Video/TV/HD/Dragon Ball Kai/Season 1/Dragon Ball Kai - S01E09 - 009 - Yamucha's Struggle! The Terrifying Saibaimen.mkv" to /var/lib/emby-server/data/subtitles/e/e27032d0-9c25-8f5a-998e-0167a6c365b2.srt

2016-05-24 20:50:26.6495 Info HttpServer: HTTP Response 200 to 192.168.1.185. Time: 761ms. http://192.168.1.90:8096/emby/Videos/768ab87259ae73d2c38c247a74e79cf8/768ab87259ae73d2c38c247a74e79cf8/Subtitles/3/0/Stream.vtt

2016-05-24 20:50:27.2962 Info HttpServer: HTTP POST http://192.168.1.90:8096/emby/Sessions/Playing. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

2016-05-24 20:50:27.4106 Info HttpServer: HTTP Response 204 to 192.168.1.185. Time: 115ms. http://192.168.1.90:8096/emby/Sessions/Playing

 

 

I don't want to hijack this thread..it just seems like my issues are very similar.  My server version is emby-server-3.0.5971-18.1.x86_64 (running on linux, likely obviously :) )

Link to comment
Share on other sites

Tanamur

Hi @@waverly360 - No problem for me and I appreciate your contribution. I have some time to focus on the problem today so I am going to stay at it and report troubleshooting results back here.

Link to comment
Share on other sites

waverly360

Ah, yknow what..I just figured out the correlation between the files not working, and the files that are...the files that don't work all have an apostrophe in the filename...looks like that's not being handled correctly in the firestick app.

 

I bet that's not your problem, is it?

Link to comment
Share on other sites

Hi, please make sure to attach complete log files as well as transcoding logs (if present). thanks.

Link to comment
Share on other sites

Tanamur

Okay, I have done the following for the next test:

 

  1. Deleted (after cache backup) all libraries except one movie library with 1300  movies.
  2. Cleaned and Rescanned libraries
  3. Rebooted AFTV1
  4. Entered all movie library options again
  5. Performs failed with same Volley Error

Next Test

  1. Removed large folder of 1300 movies from library
  2. Added folder of only 10 movies to library for small test
  3. Clean and rescan
  4. Retested and Success: Performers now opens without VolleyError (NOTE: Performers/Cast/Crew library only displays for people in the 10 movies in library...as expected I guess)

Next Test

  1. Add folder containing 1300 movies back into the library and test Performers
  2. ...back later with update edits...
  3. Library scan ran for hours and never finished - *nuked install and starting over*
  4. Reinstalling Emby from scratch after all traces uninstalled
  5. ...back later with update edits...
  6. Everything reinstalled, custom paths, supporter pass, and all done pretty quickly. Perhaps drastic but working perfectly with small library
  7. Will move to local metadata storage

 

Thanks for all of the help @@CBers and @@ebr!

Edited by Tanamur
  • Like 1
Link to comment
Share on other sites

Tanamur

Hi, please make sure to attach complete log files as well as transcoding logs (if present). thanks.

 

Hi @@Luke - Is there way to set a custom path for logs or do they have to live at C:\Users\USER\AppData\Roaming\Emby-Server\logs?

Link to comment
Share on other sites

Tanamur

Ah, yknow what..I just figured out the correlation between the files not working, and the files that are...the files that don't work all have an apostrophe in the filename...looks like that's not being handled correctly in the firestick app.

 

I bet that's not your problem, is it?

 

@@waverly360 - sorry for the late reply, I had my head down doing my testing. For the first small library of 10 movies, none of the titles included a comma and there were no problems viewing that library. I am now adding TV Series as a new library and as I look through the titles there are a few with commas (e.g. Stop, Search, Seize and Underworld, Inc.). I just noticed that the Stop, Search, Seize does include the commas in the folder name but Underworld, Inc. does not.

 

The first scan of the TV library has been running for several hours and I will not test the entry into the Performers section on the AFTV until that finishes. I'll report back here when that is done.

Link to comment
Share on other sites

This error has been occuring for quite some time. When using Emby on my AFTV1 and viewing a movie

library I am given the Option at the bottom to view Suggested, All Items, By Letter, Genres and

Performers. I can view all options with no problem except Performers. When I enter Performers all

image frames freeze their "loading circles" and after about 30 seconds I get the VolleyError (see

pic).

Yeah, I know why. Some time ago, I tried adding that endpoint that grabs people (/persons?includeitemtypes=movies,boxsets&isfavorite=true...) to the roku. I only tried adding favorite people with movie content and noticed it took over a minute to populate that row. I can see how grabbing all people with content may timeout all the time. Especially with a large library.

 

@@ebr are you using the /persons endpoint with a combination of includeitemtypes for movies,series,episodes and such? I never found an acceptable way speed-wise to deal with people other than cast&crew and using search. You may find the same solution too. Why arent you showing people with your search? You also arent showing tv series, only episodes. Was this intentional or just an oversight? You are missing some critical item types in your search.

 

IncludeItemTypes: "Movie,BoxSet,Series,Episode,Trailer,Channel,ChannelVideoItem,Video,AdultVideo,MusicVideo,Genre,MusicGenre,MusicArtist,MusicAlbum,Person,People,Studio,Audio"

 

names = ["Movies", "Shows", "Episodes", "People", "Trailers", "Videos", "Genres", "Artists", "Albums", "Songs", "Studios"]

 

Look at all the ones I allow in the blueneon app. Adding these rows adds functionality in search. This helps when you cant use the /persons endpoint directly. I am sure many users would appreciate it. Just food for thought.

 

956033e79a43743e0a895fae35cdbf35.jpg

 

This is what you are eventually greeted with. No people ever appear.

Edited by speechles
Link to comment
Share on other sites

I am searching for people but, for a long time, the server hasn't been including any people results.  It still isn't for me so I need to investigate why.

 

My search results are all presented categorized to make it easier to find what you are really looking for and not bust through the limit before getting to the item you want.

Link to comment
Share on other sites

Luke - I use IncludeItemTypes to narrow search results.  This works great for everything except People it looks like.  If I have that as an include type, I get zero results...

05-26 10:44:06.457 11783-11783/tv.emby.embyatv I/System.out: Response received from: http://192.168.1.120:8096/emby/Search/Hints?Limit=50&SearchTerm=Tom&UserId=5b48ed3999042084abe16d27a0e88e9c&IncludePeople=true&IncludeMedia=true&IncludeItemTypes=Person&IncludeGenres=true&IncludeArtists=true&IncludeStudios=true&format=json
05-26 10:44:06.463 11783-11783/tv.emby.embyatv I/System.out: Search result for Person 0 items

Link to comment
Share on other sites

@@ebr

http://192.168.1.120:8096/emby/Search/Hints?Limit=50&SearchTerm=Tom&UserId=5b48ed3999042084abe16d27a0e88e9c&IncludePeople=true&IncludeMedia=true&IncludeItemTypes=People,Person&format=json

It works for me with "IncludeItemTypes=People,Person" . This is the only difference I see in your query that doesn't work versus mine that does work.

 

&IncludeArtists=true&IncludeStudios=true&IncludeGenres=true

Why do you include this in your people query? Shouldn't these all be false when pulling people? I have these set to false on my query.

 

If your includeItemtypes = musicartist, studio, musicgenre or genre those being true would make sense.

Edited by speechles
Link to comment
Share on other sites

CBers

I seem to get a lot of these volley timeout messages and if I do, I just clear the app's data and cache and it then loads first time.

 

I know I shouldn't have to do that, but it gets very frustrating waiting for it all to load.

 

It doesn't take 30 seconds to amend the couple of settings I prefer to have different from the defaults.

 

Could there be something that the app is "holding on to" that causes an issue?

 

Should it die gracefully if not re-opened after a period of time?

 

Just a thought :)

 

.

Edited by CBers
Link to comment
Share on other sites

@@ebr

http://192.168.1.120:8096/emby/Search/Hints?Limit=50&SearchTerm=Tom&UserId=5b48ed3999042084abe16d27a0e88e9c&IncludePeople=true&IncludeMedia=true&IncludeItemTypes=People,Person&format=json

It works for me with "IncludeItemTypes=People,Person" . This is the only difference I see in your query that doesn't work versus mine that does work.

 

Thanks, using "People" works.  That's a mistake in this particular end point though as everywhere else in the system, that item type is "Person".

 

 

&IncludeArtists=true&IncludeStudios=true&IncludeGenres=true

Why do you include this in your people query? Shouldn't these all be false when pulling people? I have these set to false on my query.

 

If your includeItemtypes = musicartist, studio, musicgenre or genre those being true would make sense.

 

Those are legacy attributes.  Pretty sure the server is ignoring them but the common code I'm using still has references to them (probably just so things that used them wouldn't break).

Link to comment
Share on other sites

I seem to get a lot of these volley timeout messages and if I do, I just clear the app's data and cache and it then loads first time.

 

I think if you just waited, without clearing app data, and then tried again, you would see the same thing.

Link to comment
Share on other sites

CBers

I think if you just waited, without clearing app data, and then tried again, you would see the same thing.

Possibly, but it's too annoying to have to wait. It's quicker to clear data and start afresh.

 

Something needs sorting out with the server, as there are too many people having the same issues across multiple clients.

Link to comment
Share on other sites

Pretty sure the server is ignoring them but the common code I'm using still has references to them (probably just so things that used them wouldn't break).

If the server isnt ignoring them this could cause slower responses in app versus other apps. On roku for example, the ones unrequired are always false.

 

@@Luke Does this slow the server search when using include... on items that dont match the includeitemtypes?

For example: includepeople=true&includestudios=true&includeitemtypes=people,person

 

 

 

Sent from my Nexus 7 using Tapatalk

Edited by speechles
Link to comment
Share on other sites

@@Luke Does this slow the server search when using include... on items that dont match the includeitemtypes?

For example: includepeople=true&includestudios=true&includeitemtypes=people,person

 

I'm almost positive they are completely discarded.

 

In the early days, those attributes were how you told the query what to search for.  Then the IncludeItemTypes was implemented to supplant it.

 

It has been long enough now we can probably remove them from the ApiClient implementations.

Link to comment
Share on other sites

Something needs sorting out with the server, as there are too many people having the same issues across multiple clients.

 

I'm not arguing that and it is being worked on.

 

I'm just saying your "clear data" routine is just a placebo affect.  The real thing that speeds it up is executing the queries at least once.

Link to comment
Share on other sites

CBers

I'm not arguing that and it is being worked on.

 

I'm just saying your "clear data" routine is just a placebo affect. The real thing that speeds it up is executing the queries at least once.

Possibly, but I've also tried force stopping the app and even rebooting my Shield and/or the Nexus Player but I still see these volley timeout messages.

 

Until the server side is sorted, clearing the app's data and cache is a weapon in our armoury agains the problems :)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...