Jump to content

emby awfully slow and unreliable after update


kro

Recommended Posts

hello

 

i upgraded to emby-server 3.1.0-9.1 with apt-get on debian (i don't remember what was the previous version).

and now emby is very slow and only display the complete homescreen once every 10 times

sometimes i also have this kind of message :

0 0 HTTP/1.1 304 NotModified X-UA-Compatible: IE=Edge Access-Control-Allow-Headers: Content-Type, Authorization, Range, X-MediaBrowser-Token, X-Emby-Authorization Access-Control-Allow-Methods: GET, POST, PUT, DELETE, PATCH, OPTIONS Access-Control-Allow-Origin: * Vary: Accept-Encoding ETag: "f78c63cc3676190f75b5db292707ad1d" Server: Mono-HTTPAPI/1.1, UPnP/1.0 DLNADOC/1.50 Content-Type: text/html; charset=UTF-8 Date: Wed, 21 Dec 2016 07:18:19 GMT Transfer-Encoding: chunked 0 0

some other times the round spinning circle never fade away and the home screen never displays.
network toolbar on chrome doesn't show any pending request though...

is there anything to do after an upgrade ? any operation to clean the database or clear the cache e.g. (how) ?

 

thanks !

Link to comment
Share on other sites

wirehack7

I have the same problem. And I'm running a reverse proxy. The config is as following:

<IfModule mod_ssl.c>
NameVirtualHost *:80
NameVirtualHost *:443
SSLStrictSNIVHostCheck off

<VirtualHost *:443>
        ServerName jaxclass.com
        ServerAlias jaxclass.com

        ProxyVia On
        ProxyRequests Off
        ProxyPreserveHost On
        #SSLProxyEngine On
        Timeout 600
        ProxyTimeout 600

        #ProxyPass / https://127.0.0.1:8920/
        #ProxyPassReverse / https://127.0.0.1:8920/


        <Location />
                ProxyPass        http://127.0.0.1:8096/
                ProxyPassReverse http://127.0.0.1:8096/
        </Location>

        <Location /embywebsocket>
                ProxyPass        ws://127.0.0.1:8096/embywebsocket
                ProxyPassReverse ws://127.0.0.1:8096/embywebsocket
        </Location>

SSLCertificateFile /etc/letsencrypt/live/pyload.jaxclass.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/pyload.jaxclass.com/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>

</IfModule>

Before the new update it worked like a charm. Now I have problems that the site is not viewable. I get the errors like @@kro describes, also I get this error in browser:

unreachable code after return statement[Weitere Informationen]  navdrawer.js:101:12

I checked the logs. The client (aka browser) is not even doing a connection to the server. Apache Log is empty for access and error, so is syslog.

Link to comment
Share on other sites

wirehack7

585a432b5abea_Skizze.png

 

And then it loads forever.

 

When I reload then again the network log is empty and it also loads forever with a white blank screen.

 

Deleted all cache and cookies in browser. Site loads normal for 1 time. Then I get the errors again. Also I see errors now in my Apache Log for the second connection, after that none:

[Wed Dec 21 09:54:39.373852 2016] [proxy_http:error] [pid 3305] (70007)The timeout specified has expired: [client ***:49911] AH01110: error reading response, referer: https://jaxclass.com/web/login.html?serverid=1f459b88051e4187b06872e12ca1fac7
[Wed Dec 21 09:55:23.398061 2016] [proxy_http:error] [pid 3344] (70007)The timeout specified has expired: [client ***:49926] AH01110: error reading response, referer: https://jaxclass.com/web/bower_components/emby-webcomponents/fonts/roboto/style.css?v=3.1.0.0
[Wed Dec 21 09:55:37.453856 2016] [proxy_http:error] [pid 3473] (70007)The timeout specified has expired: [client ***:58375] AH01110: error reading response, referer: https://jaxclass.com/web/home.html
[Wed Dec 21 09:58:16.166136 2016] [proxy_http:error] [pid 3309] (70007)The timeout specified has expired: [client ***:58454] AH01110: error reading response, referer: https://jaxclass.com/web/index.html
[Wed Dec 21 09:58:31.816508 2016] [proxy_http:error] [pid 3351] (70007)The timeout specified has expired: [client ***:58464] AH01110: error reading response, referer: https://jaxclass.com/web/index.html
[Wed Dec 21 09:58:31.816534 2016] [proxy_http:error] [pid 3347] (70007)The timeout specified has expired: [client ***:58459] AH01110: error reading response, referer: https://jaxclass.com/web/index.html
[Wed Dec 21 09:58:31.816549 2016] [proxy_http:error] [pid 3502] (70007)The timeout specified has expired: [client ***:58461] AH01110: error reading response, referer: https://jaxclass.com/web/index.html
[Wed Dec 21 09:58:45.465286 2016] [proxy_http:error] [pid 3879] (70007)The timeout specified has expired: [client ***:58467] AH01110: error reading response, referer: https://jaxclass.com/web/index.html
[Wed Dec 21 09:59:23.003923 2016] [proxy_http:error] [pid 3348] (70007)The timeout specified has expired: [client ***:58498] AH01110: error reading response
[Wed Dec 21 09:59:31.592560 2016] [proxy_http:error] [pid 3883] (70007)The timeout specified has expired: [client ***:58503] AH01110: error reading response, referer: https://jaxclass.com/web/index.html
[Wed Dec 21 09:59:52.466879 2016] [proxy_http:error] [pid 3306] (70007)The timeout specified has expired: [client ***:58518] AH01110: error reading response, referer: https://jaxclass.com/web/index.html
[Wed Dec 21 09:59:52.466895 2016] [proxy_http:error] [pid 3506] (70007)The timeout specified has expired: [client ***:58517] AH01110: error reading response, referer: https://jaxclass.com/web/index.html

It does not depend on the Apache reverse proxy. I tested it directly to Emby HTTPS port know:

unreachable code after return statement[Weitere Informationen]  itemdetailpage.js:1415:8

Same error as above, but here without Apache2 in the middle. When trying to play something I get this:

ReferenceError: $ is not defined[Weitere Informationen]  theme.js:357:9

So that's maybe a bug which came with the new version of Emby, independent of any proxy between.

Edited by wirehack7
Link to comment
Share on other sites

dcrdev

585a432b5abea_Skizze.png

 

And then it loads forever.

 

When I reload then again the network log is empty and it also loads forever with a white blank screen.

 

Deleted all cache and cookies in browser. Site loads normal for 1 time. Then I get the errors again. Also I see errors now in my Apache Log for the second connection, after that none:

[Wed Dec 21 09:54:39.373852 2016] [proxy_http:error] [pid 3305] (70007)The timeout specified has expired: [client ***:49911] AH01110: error reading response, referer: https://jaxclass.com/web/login.html?serverid=1f459b88051e4187b06872e12ca1fac7
[Wed Dec 21 09:55:23.398061 2016] [proxy_http:error] [pid 3344] (70007)The timeout specified has expired: [client ***:49926] AH01110: error reading response, referer: https://jaxclass.com/web/bower_components/emby-webcomponents/fonts/roboto/style.css?v=3.1.0.0
[Wed Dec 21 09:55:37.453856 2016] [proxy_http:error] [pid 3473] (70007)The timeout specified has expired: [client ***:58375] AH01110: error reading response, referer: https://jaxclass.com/web/home.html
[Wed Dec 21 09:58:16.166136 2016] [proxy_http:error] [pid 3309] (70007)The timeout specified has expired: [client ***:58454] AH01110: error reading response, referer: https://jaxclass.com/web/index.html
[Wed Dec 21 09:58:31.816508 2016] [proxy_http:error] [pid 3351] (70007)The timeout specified has expired: [client ***:58464] AH01110: error reading response, referer: https://jaxclass.com/web/index.html
[Wed Dec 21 09:58:31.816534 2016] [proxy_http:error] [pid 3347] (70007)The timeout specified has expired: [client ***:58459] AH01110: error reading response, referer: https://jaxclass.com/web/index.html
[Wed Dec 21 09:58:31.816549 2016] [proxy_http:error] [pid 3502] (70007)The timeout specified has expired: [client ***:58461] AH01110: error reading response, referer: https://jaxclass.com/web/index.html
[Wed Dec 21 09:58:45.465286 2016] [proxy_http:error] [pid 3879] (70007)The timeout specified has expired: [client ***:58467] AH01110: error reading response, referer: https://jaxclass.com/web/index.html
[Wed Dec 21 09:59:23.003923 2016] [proxy_http:error] [pid 3348] (70007)The timeout specified has expired: [client ***:58498] AH01110: error reading response
[Wed Dec 21 09:59:31.592560 2016] [proxy_http:error] [pid 3883] (70007)The timeout specified has expired: [client ***:58503] AH01110: error reading response, referer: https://jaxclass.com/web/index.html
[Wed Dec 21 09:59:52.466879 2016] [proxy_http:error] [pid 3306] (70007)The timeout specified has expired: [client ***:58518] AH01110: error reading response, referer: https://jaxclass.com/web/index.html
[Wed Dec 21 09:59:52.466895 2016] [proxy_http:error] [pid 3506] (70007)The timeout specified has expired: [client ***:58517] AH01110: error reading response, referer: https://jaxclass.com/web/index.html

It does not depend on the Apache reverse proxy. I tested it directly to Emby HTTPS port know:

unreachable code after return statement[Weitere Informationen]  itemdetailpage.js:1415:8

Same error as above, but here without Apache2 in the middle. When trying to play something I get this:

ReferenceError: $ is not defined[Weitere Informationen]  theme.js:357:9

So that's maybe a bug which came with the new version of Emby, independent of any proxy between.

 

See my post here https://emby.media/community/index.php?/topic/42693-page-doesn%C2%B4t-reload-304-status-code/page-2&do=findComment&comment=398542 setting those environment variables in your vitualhost will serve as an interim solution.

 

Also the theme.js^ error above when trying to play something - have you got the christmas theme enabled? If you do disable it via the info icon at the top of the screen - it's causing issues.

  • Like 2
Link to comment
Share on other sites

wirehack7

I set the variables, works so far. I'm wondering here why the error occurs also to the direct port of Emby then. Strange behaviour. This should be traced.

 

I deactivated the christmas theme, reference error also vanished.

 

Thank you!

 

Hopefully the errors are not coming back again.

Link to comment
Share on other sites

Hi @@kro, are you running a reverse proxy by chance?

yes !

sorry i forgot to specify this. do you need my config ?

 

 

 

Ok I now believe there is some kind of race occurring between each request and serviceworker.js which is causing a timeout in some browsers.

 

I don't have an ideal solution but - for now you can close the connection forcefully after each request is made.

 

For Apache this is done via the environment variables:

SetEnv proxy-nokeepalive 1

SetEnv proxy-sendchunked 1

 

this totally did the trick for me as well ! it seems to work perfectly now. thanks a lot !

 

here are 2 screenshots with 2 different cases of failure if that's of any use (first one was ending with only a black screen, and the second was spinning forever without any pending request) :

 

585a96ac7f884_emby1.png

 

 

585a96d4e7c23_emby2.png

Edited by kro
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...