Bugzilla – Bug 3071
Web interface becomes inaccessible after a while
Last modified: 2009-09-08 09:32:09 UTC
After SlimServer has been running for a while - its difficult to tell how long exactly, but it's at least 3 - 4 hours, the web interface becomes inaccessible. Connecting to my SlimServer via a browser I simply get a page loading browser screen and eventually it times out. Restarting the SlimServer service clears the problem and the web interface is then fine. I have been having this problem now since around 6.2.1 and I am currently running 6.2.2 - 6337. The web interface is password protected. The SqueezeBox continues to function correctly.
Stuart - can you try the latest 6.2.2 nightly and let me know if this still happens? Thanks.
I have downloaded the latest 6.2.2 nightly (25/4/2006) and installed. I think that what is actually happening is that the web interface is taking a while to fire up. When I conect to the web server from another device it takes a long while to come up and the Squeezebox reports that it has lost comms with the server. After about 2 minutes it comes back and the web page displays. My server spec is - 1.8Ghz AMD proccessor with 768Mb RAM. My music collection is approx 27000 songs. I have disabled the Library statistics in the performance settings as with them enabled it made the web server even more unresponsive. Once the web page completes loading, from that point on it seems fine. After leacing it for a while though, it then becomes unresponsive and takes about 2 mins to load again.
Stuart, is it possible that in that time SlimServer is swapping out? Can you check the memory situation on the machine and/or try changing the priority of the service?
Is this still an issue with the latest 6.5? Thanks
I strongly suspect the split scanner in 6.5 will solve this issue. Please reopen if it's still happening.