Bug 5727 - Blank home page when trying to display New Default skin
: Blank home page when trying to display New Default skin
Status: RESOLVED DUPLICATE of bug 5626
Product: Logitech Media Server
Classification: Unclassified
Component: Web Interface
: 7.0
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-10-08 15:39 UTC by Philip Meyer
Modified: 2007-10-30 07:15 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Meyer 2007-10-08 15:39:32 UTC
I updated to SVN 13681 and restarted the server.  I opened the webUI (default skin), and got an empty home page (left hand panel).  I saw the following errors in the output stream:

[23:12:58.2260] Slim::Utils::Scanner::__ANON__ (523) Error: Can't connect to remote server to retrieve playlist: Timed out waiting for data.
[23:12:58.3276] Slim::Networking::Async::_dns_error (173) Couldn't resolve IP address for: www.squeezenetwork.com
[23:12:58.3286] Slim::Networking::Async::_async_error (370) Error: [Couldn't resolve IP address for: www.squeezenetwork.com]
[23:12:58.3292] Slim::Networking::Async::HTTP::_http_error (262) Error: [Couldn't resolve IP address for: www.squeezenetwork.com]
[23:12:58.3296] Slim::Networking::SimpleAsyncHTTP::onError (183) Failed to connect to http://www.squeezenetwork.com:3000/api/v1/prefs/can_sync (Couldn't resolve IP address for: www.squeezenetwork.com)
[23:12:58.3301] Slim::Networking::SqueezeNetwork::PrefSync::_init_error (116) Unable to get list of prefs to sync with SqueezeNetwork, sync is disabled: Couldn't resolve IP address for: www.squeezenetwork.com

I refreshed the browser, and the page displayed without any subsequent errors.

It appears that if the server can't see SqueezeNetwork, it prevents the webUI from opening correctly.
Comment 1 KDF 2007-10-08 16:01:58 UTC
I do not believe they are linked.
home page often needs cache clearing when updating.
Comment 2 KDF 2007-10-10 15:29:59 UTC
see bug 5626.  The possible cause is that the browser is trying to get data before the server has started up properly, instead getting partially cached data.   To test if this is really the SN connection, work with a functional SC with working web page and then disconnect the router from your ISP so that SN is not reachable.  If this is only a startup case, then this is basically a duplicate of bug 5626 
Comment 3 Michael Herger 2007-10-30 07:15:55 UTC

*** This bug has been marked as a duplicate of 5626 ***