Bugzilla – Bug 15789
Plugin page no longer displays
Last modified: 2014-03-11 14:37:44 UTC
Version: 7.4.2 - r30215 @ Mon Feb 22 12:40:30 PST 2010 Hostname: jarmac.local Server IP Address: 127.0.0.1 Server HTTP Port Number: 9000 Operating system: Mac OS X 10.6.2 - EN - utf8 Platform Architecture: x86_64 Perl Version: 5.10.0 - darwin-thread-multi-2level MySQL Version: 5.0.22-standard Total Players Recognized: 2 Since upgrading to 7.4.2, the plugin page no longer displays. It just says "waiting for server." I tried this on OS X with Firefox and Safari and on Windows 7 with Firefox.
Actually, it is sitting waiting for timeouts. All the repositories are gone! Where did they go? If there was a change in architecture, why don't you notify users in some way? Bad repository http://alienbbc.googlecode.com/svn/trunk/testrepo.xml - Couldn't resolve IP address for: alienbbc.googlecode.com Bad repository http://www.mysqueezebox.com/public/plugins/other.xml - Couldn't resolve IP address for: www.mysqueezebox.com Bad repository http://www.mysqueezebox.com/public/plugins/logitech.xml - Couldn't resolve IP address for: www.mysqueezebox.com Bad repository http://www.stagessound.de/bluegaspode.xml - Couldn't resolve IP address for: www.stagessound.de Bad repository http://www.hickinbottom.com/sc-plugins/repo.xml - Couldn't resolve IP address for: www.hickinbottom.com Bad repository http://weathertime.googlecode.com/svn/trunk/repo.xml - Couldn't resolve IP address for: weathertime.googlecode.com Bad repository http://www.mysqueezebox.com/public/plugins/repository.xml - Couldn't resolve IP address for: www.mysqueezebox.com But the address resolves: jarmac:~ jar$ nslookup www.mysqueezebox.com Server: 75.75.75.75 Address: 75.75.75.75#53 Non-authoritative answer: Name: www.mysqueezebox.com Address: 66.150.114.115 note that this is using Comcast's new DNSSEC servers. Does the server have issues with this?
I changed the dns server back to the usual one, and the addresses still do not resolve in my server. So something is wrong in your code. jarmac:~ jar$ nslookup www.mysqueezebox.com Server: 68.87.68.162 Address: 68.87.68.162#53 Non-authoritative answer: Name: www.mysqueezebox.com Address: 66.150.114.115
The problem is the Norton firewall for the Mac. What is the process name that I must enable to get this to work? There is no squeezeboxserver running, which makes it very difficult to configure firewall permissions, both ingoing and outgoing.
perl5.10.0 on Snow Leopard - just check your activity monitor
Adrian - any idea why this failure would lock up the web page creation?
Plugin page generation generates a set of async http requests - one for each repo and only responds with the page when they return or an error comes back from async http. (they are all done in parallel) Perhaps the issues is that the error for dns lookups is too long give the appearance that it never comes back? Looking at the 7.5 code it doesn't look like we send a timeout to AnyEvent's dns resolver. However its documentation suggests the defaults are 3 retries of 2, 5 and 5 seconds. So I would hope it returns with an error after 12 seconds. If the problem can be recreated can you turn on logging for network.asyncdns.
I tried adding perl. It does not help. perl is running slimserver.pl, but it is imnpossible to add that because you have put it inside the preferencePane. It imposswible to descend into a preference pane in a GUI file chooser! So one cannot add it. Norton said you need to turn it into an application. Then it can be added. So, it if one turns on the application firewall, SqueezeboxServer will not start, and also, if it was already started, it cannot access any Web address. All Comcast customers now will have Norton, so this is a big issue.
It's perl5.10.0, not perl. And this is not in the pref pane, but in /usr/bin/perl5.10.0.
Yes, I added perl5.10.0. Did not help. And to do that, I had to unhide /usr
Norton claims that they are going to do something about this, hopefully soon. All is OK if you turn off the application firewall.
IMHO most likely a dupe of bug 17571
*** This bug has been marked as a duplicate of bug 17571 ***