Austin_Yeahbaby 0 Posted October 7, 2020 Share Posted October 7, 2020 Hi, I’ve recently started getting volley error timeout on my Sony Android TV client. Samsung all working fine but I have to forget the server on the Sony and then search for server and connect each time I go into the cloent Current se4ver version is 4.05.50 on qnap nas Full errror is "volleyError com.android .volley.timeoutError: looking at the log I can see an error report ad follows... any thoughts ? 2020-10-07 21:27:00.768 Info HttpServer: HTTP GET http://192.168.0.98:8096/emby/System/Logs/embyserver.txt. UserAgent: Mozilla/5.0 (iPad; CPU OS 14_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0 Mobile/15E148 Safari/604.1 2020-10-07 21:27:00.845 Error HttpServer: Error processing request *** Error Report *** Version: 4.5.0.50 Command line: /share/CACHEDEV4_DATA/.qpkg/EmbyServer/system/EmbyServer.dll -programdata /share/CACHEDEV4_DATA/.qpkg/EmbyServer/programdata -ffdetect /share/CACHEDEV4_DATA/.qpkg/EmbyServer/bin/ffdetect -ffmpeg /share/CACHEDEV4_DATA/.qpkg/EmbyServer/bin/ffmpeg -ffprobe /share/CACHEDEV4_DATA/.qpkg/EmbyServer/bin/ffprobe -defaultdirectory /share/CACHEDEV1_DATA -updatepackage emby-server-qnap_{version}_x86_64.qpkg Operating system: Linux version 4.14.24-qnap (root@U16BuildServer49) (gcc version 4.9.2 (toolchain config: [gcc-4.9.2 binutils-2.25 glibc-2.21])) #1 SMP Fri Sep 25 01:0 Framework: .NET Core 3.1.7 OS/Process: x64/x64 Runtime: share/CACHEDEV4_DATA/.qpkg/EmbyServer/system/System.Private.CoreLib.dll Processor count: 4 Data path: /share/CACHEDEV4_DATA/.qpkg/EmbyServer/programdata Application path: /share/CACHEDEV4_DATA/.qpkg/EmbyServer/system System.InvalidOperationException: System.InvalidOperationException: Response Content-Length mismatch: too many bytes written (321744 of 321498). at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ThrowTooManyBytesWritten(Int32 count) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.VerifyAndUpdateWrite(Int32 count) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.Advance(Int32 bytes) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpResponsePipeWriter.Advance(Int32 bytes) at System.IO.Pipelines.PipeWriter.CopyFromAsync(Stream source, CancellationToken cancellationToken) at Emby.Server.Implementations.HttpServer.FileWriter.WriteToAsync(IResponse response, CancellationToken cancellationToken) at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost appHost, IRequest httpReq, IResponse httpRes, RestPath restPath, String responseContentType, CancellationToken cancellationToken) at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IRequest httpReq, ReadOnlyMemory`1 urlString, ReadOnlyMemory`1 localPath, CancellationToken cancellationToken) Source: Microsoft.AspNetCore.Server.Kestrel.Core TargetSite: Void ThrowTooManyBytesWritten(Int32) Link to comment Share on other sites More sharing options...
neik 837 Posted October 7, 2020 Share Posted October 7, 2020 (edited) Volleyerror usually is a hint for network problems. So, you might wanna check the connection on the client. Edited October 7, 2020 by neik Link to comment Share on other sites More sharing options...
Austin_Yeahbaby 0 Posted October 7, 2020 Author Share Posted October 7, 2020 Thanks, everything else is working fine, YouTube, Spotify etc and when I remove the server from the Emby client and search for it again, it works fine. it’s like the client is keeping an incorrect server reference on each startup it’s produces an error above so hopefully easy to track down Link to comment Share on other sites More sharing options...
ebr 14910 Posted October 7, 2020 Share Posted October 7, 2020 Make sure the address shown on your server dashboard is correct. If not, use the network settings to correct it. Before you do that, though, look to upgrade to 4.5.1 or 2. Thanks. Link to comment Share on other sites More sharing options...
ramsesaguirre20 0 Posted May 19, 2021 Share Posted May 19, 2021 I have the same problem with android tv equipment and roku sends me the following error and for the video playback 2021-05-19 02:09:21.186 Error Server: Error processing request │ │ *** Error Report *** │ │ Version: 4.5.4.0 │ │ Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/│ │ Operating system: Linux version 5.4.0-72-generic (buildd@lcy01-amd64-019) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #80-Ubuntu SMP Mon Apr 1│ │ Framework: .NET Core 3.1.8 │ │ OS/Process: x64/x64 │ │ Runtime: opt/emby-server/system/System.Private.CoreLib.dll │ │ Processor count: 4 │ │ Data path: /var/lib/emby │ │ Application path: /opt/emby-server/system │ │ System.InvalidOperationException: System.InvalidOperationException: Response Content-Length mismatch: too many bytes written (13622483 of 13619787). │ │ at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ThrowTooManyBytesWritten(Int32 count) │ │ at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.VerifyAndUpdateWrite(Int32 count) │ │ at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.Advance(Int32 bytes) │ │ at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpResponsePipeWriter.Advance(Int32 bytes) │ │ at System.IO.Pipelines.PipeWriter.CopyFromAsync(Stream source, CancellationToken cancellationToken) │ │ at Emby.Server.Implementations.HttpServer.FileWriter.WriteToAsync(IResponse response, CancellationToken cancellationToken) │ │ at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost appHost, IRequest httpReq, IResponse httpRes, RestPath│ │ at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IRequest httpReq, ReadOnlyMemory`1 urlString, ReadOnlyMemory`1 localPath│ │ Source: Microsoft.AspNetCore.Server.Kestrel.Core │ │ TargetSite: Void ThrowTooManyBytesWritten(Int32) Link to comment Share on other sites More sharing options...
Carlo 4330 Posted May 19, 2021 Share Posted May 19, 2021 The actual message is a bit unusual "Too Many Bytes Written" but would fit with a network error which is what a "Volley Error" is. The first thing I would do is look at your network setup. If using WIFI see if there is any way to change over to Ethernet instead. This is DOUBLE IMPORTANT for the server IMHO. If using WIFI it could be a simple as trying to use a different WIFI channel. WIFI that has been working well could just start having an issue due to a neighbor who changed WIFI parameters and now causes you issues. Lot of things can cause WIFI issue. If you signal is on the weaker side moving the AP closer is usually a good thing to do, etc. We really need more information on your setup and how often you are getting errors. Link to comment Share on other sites More sharing options...
Luke 37060 Posted May 19, 2021 Share Posted May 19, 2021 9 hours ago, ramsesaguirre20 said: I have the same problem with android tv equipment and roku sends me the following error and for the video playback 2021-05-19 02:09:21.186 Error Server: Error processing request │ │ *** Error Report *** │ │ Version: 4.5.4.0 │ │ Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/│ │ Operating system: Linux version 5.4.0-72-generic (buildd@lcy01-amd64-019) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #80-Ubuntu SMP Mon Apr 1│ │ Framework: .NET Core 3.1.8 │ │ OS/Process: x64/x64 │ │ Runtime: opt/emby-server/system/System.Private.CoreLib.dll │ │ Processor count: 4 │ │ Data path: /var/lib/emby │ │ Application path: /opt/emby-server/system │ │ System.InvalidOperationException: System.InvalidOperationException: Response Content-Length mismatch: too many bytes written (13622483 of 13619787). │ │ at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ThrowTooManyBytesWritten(Int32 count) │ │ at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.VerifyAndUpdateWrite(Int32 count) │ │ at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.Advance(Int32 bytes) │ │ at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpResponsePipeWriter.Advance(Int32 bytes) │ │ at System.IO.Pipelines.PipeWriter.CopyFromAsync(Stream source, CancellationToken cancellationToken) │ │ at Emby.Server.Implementations.HttpServer.FileWriter.WriteToAsync(IResponse response, CancellationToken cancellationToken) │ │ at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost appHost, IRequest httpReq, IResponse httpRes, RestPath│ │ at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IRequest httpReq, ReadOnlyMemory`1 urlString, ReadOnlyMemory`1 localPath│ │ Source: Microsoft.AspNetCore.Server.Kestrel.Core │ │ TargetSite: Void ThrowTooManyBytesWritten(Int32) Hi there, can you please attach the complete emby server log? Thanks. Link to comment Share on other sites More sharing options...
ramsesaguirre20 0 Posted May 19, 2021 Share Posted May 19, 2021 It is a dedicated server and nothing is over wifi is via ethernet embyserver.txt Link to comment Share on other sites More sharing options...
ebr 14910 Posted May 19, 2021 Share Posted May 19, 2021 Hi. How many subtitle tracks exist in this particular item? Can you also post the ffmpeg log from that playback? Link to comment Share on other sites More sharing options...
ramsesaguirre20 0 Posted May 19, 2021 Share Posted May 19, 2021 2021-05-19 21:17:05.635 Error Server: Error processing request │ │ *** Error Report *** │ │ Version: 4.5.4.0 │ │ Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/│ │ Operating system: Linux version 5.4.0-72-generic (buildd@lcy01-amd64-019) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #80-Ubuntu SMP Mon Apr 1│ │ Framework: .NET Core 3.1.8 │ │ OS/Process: x64/x64 │ │ Runtime: opt/emby-server/system/System.Private.CoreLib.dll │ │ Processor count: 4 │ │ Data path: /var/lib/emby │ │ Application path: /opt/emby-server/system │ │ System.InvalidOperationException: System.InvalidOperationException: Response Content-Length mismatch: too many bytes written (77606099 of 77602126). │ │ at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ThrowTooManyBytesWritten(Int32 count) │ │ at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.VerifyAndUpdateWrite(Int32 count) │ │ at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.Advance(Int32 bytes) │ │ at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpResponsePipeWriter.Advance(Int32 bytes) │ │ at System.IO.Pipelines.PipeWriter.CopyFromAsync(Stream source, CancellationToken cancellationToken) │ │ at Emby.Server.Implementations.HttpServer.FileWriter.WriteToAsync(IResponse response, CancellationToken cancellationToken) │ │ at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost appHost, IRequest httpReq, IResponse httpRes, RestPath│ │ at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IRequest httpReq, ReadOnlyMemory`1 urlString, ReadOnlyMemory`1 localPath│ │ Source: Microsoft.AspNetCore.Server.Kestrel.Core │ │ TargetSite: Void ThrowTooManyBytesWritten(Int32) embyserver (1).txt ffmpeg-transcode-9cfb9a11-7ec7-4199-91df-6a884dde622b_1.txt ffmpeg-transcode-20d409b8-5762-48ae-b0de-cd961553f489_1.txt ffmpeg-directstream-d3372b12-aee4-4d75-8392-8353926d9b42_1.txt Link to comment Share on other sites More sharing options...
Luke 37060 Posted May 21, 2021 Share Posted May 21, 2021 Hi, can you please try the new Emby Server 4.6 release and let us know how that compares? Thanks. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now