Jump to content

keithc

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About keithc

  • Rank
    Newbie

Converted

  • Location
    San Francisco Bay Area
  1. I'll answer my own question. This issue is being reported on github. https://github.com/jellyfin/jellyfin/issues/3397
  2. Tried to attach to my jellyfin server via GUI and get a 'Forbidden' error. Not able to connect over the network either. Worked OK last night and no changes since last night. Tried 'nightly' build - was using 'latest', but same problem. Other docker containers OK. I do see this message repeated in the syslog when trying to connect: Jul 24 20:17:47 colossus nginx: 2020/07/24 20:17:47 [error] 8799#8799: *3857 connect() to unix:/var/tmp/jellyfin.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.40.137, server: , request: "GET /dockerterminal/jellyfin/token HTTP/1.1", upstream: "http://unix:/var/tmp/jellyfin.sock:/token", host: "192.168.1.30", referrer: "http://192.168.1.30/dockerterminal/jellyfin/" Here is the log: [2020-07-25 06:44:56.213 -07:00] [ERR] [130] Emby.Server.Implementations.HttpServer.HttpListenerHost: Error processing request: "The operation was canceled". URL: "http://192.168.1.30:8096/favicon.ico" [2020-07-25 06:44:56.213 -07:00] [ERR] [130] Emby.Server.Implementations.HttpServer.HttpListenerHost: Error while handling exception in response to "http://192.168.1.30:8096/favicon.ico" System.AggregateException: Error while handling request exception (The operation was canceled.) (Response Content-Length mismatch: too many bytes written (41 of 25).) ---> System.OperationCanceledException: The operation was canceled. at System.Threading.CancellationToken.ThrowOperationCanceledException() at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.Microsoft.AspNetCore.Http.Features.IHttpResponseBodyFeature.StartAsync(CancellationToken cancellationToken) at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionBody.StartAsync(CancellationToken token) at Microsoft.AspNetCore.Http.DefaultHttpResponse.StartAsync(CancellationToken cancellationToken) at Microsoft.AspNetCore.Http.HttpResponseWritingExtensions.WriteAsync(HttpResponse response, String text, Encoding encoding, CancellationToken cancellationToken) at Microsoft.AspNetCore.Http.HttpResponseWritingExtensions.WriteAsync(HttpResponse response, String text, CancellationToken cancellationToken) at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IHttpRequest httpReq, String urlString, String host, String localPath, CancellationToken cancellationToken) --- End of inner exception stack trace --- ---> (Inner Exception #1) System.InvalidOperationException: Response Content-Length mismatch: too many bytes written (41 of 25). 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.WritePipeAsync(ReadOnlyMemory`1 data, CancellationToken cancellationToken) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpResponseStream.WriteAsync(ReadOnlyMemory`1 source, CancellationToken cancellationToken) at System.IO.Compression.DeflateStream.FlushAsyncCore(CancellationToken cancellationToken) at System.IO.Pipelines.StreamPipeWriter.FlushAsyncInternal(CancellationToken cancellationToken) at Emby.Server.Implementations.HttpServer.HttpListenerHost.ErrorHandler(Exception ex, IRequest httpReq, Int32 statusCode, String urlToLog, Boolean ignoreStackTrace) at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IHttpRequest httpReq, String urlString, String host, String localPath, CancellationToken cancellationToken)<---
  3. Returned the motherboard and they discovered bent pins on the socket. I've built a dozen or so systems and never had that happen before. Odd since the system booted OK - just could not get the IPMI interface to work. Did not pursue it any further. Now running an Asus WS C246 PRO with an Intel E-2146G CPU. Works great with zero problems. I'll let you determine if the SM is worth it. Not sure I'd ever try them again.
  4. Trying to figure out how to get IPMI to function on this board. Seems simple enough, but I can not ping the IP once statically configured. DHCP fails to get an IP. Board shipped with latest firmware. Booted the system running Ubuntu and only one interface is seen. I noticed that the 'IPMI LAN Selection is set to 'Failover' which I believe should be 'Shared'. The GUI has locked that and I can not change the setting. Thanks for any help.