PDA

View Full Version : "Problem: There is already another copy of the SlimServerrunning on this machine"



Mike Hollick
2004-04-06, 11:24
I just got my Squeezebox today and I'm having a hard time getting the
server running on my machine (Win2K Pro SP2). I get an error stating
that another copy of the server is running. I've looked over the
archives and I see that this is generated when it can't get port 3483.
I checked using netstat -a and I don't see anything using the port; I
also used nc as suggested in one of the messages (I think it was nc -l
-u -p 3483) and I didn't see any errors.

Any suggestions on how I can proceed other than reinstalling the OS?
The server runs fine on another machine on my network (WinXP), but the
Win2K machine is the one I have running 24/7 so I've got to get it
working there. Any ideas would be appreciated!

-->Mike

Mike Hollick
2004-04-06, 22:30
In case anyone is interested - I spent some time on this tonight and
have it working, though I'm not sure exactly why. I downloaded the perl
source for the server and started hacking around with it using
ActivePerl 5.6.1.635. I eliminated possible causes like the port being
used, firewall problems, etc. by copying the perl that opens the ports
into a small test file - that worked fine. I then started adding code
from the real server to that test file until I was able to get it to
fail, then traced from there.

Anyway - to get it working I had to do the following:

- Stub out Slim::Utils::Misc::hostaddr(). My server has a pretty
complicated networking setup - it connects to a VPN, then acts as a NAT
router for the remote network for other machines on my LAN. So maybe
something about that configuration is confusing things.

- Add a call to checkVersion() in slimserver.pl right after the
initsettings() call in the init sub (line 246 in the current version).
I have no idea why this is necessary, but it is - perhaps something
about checking for the new version makes subsequent connections work. I
had found that I needed to delete my prefs file every time for it to
work - I narrowed that down to the need to delete the checkVersion entry
in that file. It looks like when that entry is missing it triggers some
code that calls checkVersion earlier than if you just set it to 1. Once
I got to that point it was easier to just call it via brute force than
write a script that would perform surgery on my prefs every time I start
the server.

Anyway, hopefully this will be of some help. If someone more familiar
with the server source would like me to run any experiments to help
track down the real issues I'd be glad to - I'd rather not have to put
these hacks in myself every time a new version comes out, anyway :)

-->Mike

> I just got my Squeezebox today and I'm having a hard time getting the
> server running on my machine (Win2K Pro SP2). I get an error stating
> that another copy of the server is running. I've looked over the
> archives and I see that this is generated when it can't get port 3483. I
> checked using netstat -a and I don't see anything using the port; I
> also used nc as suggested in one of the messages (I think it was nc -l
> -u -p 3483) and I didn't see any errors.
>
> Any suggestions on how I can proceed other than reinstalling the OS? The
> server runs fine on another machine on my network (WinXP), but the Win2K
> machine is the one I have running 24/7 so I've got to get it working
> there. Any ideas would be appreciated!
>
> -->Mike
>
>

dean
2004-04-07, 08:30
Hi Mike,

Wow, this is a new one. Can you send me details about your networking
setup so we can try to reproduce the problem? I'd also like to know
what this does from the command line:

perl -e "use Sys::Hostname; print hostname() . \"\\n\";"

Thanks!

-dean

On Apr 6, 2004, at 10:30 PM, Mike Hollick wrote:

> In case anyone is interested - I spent some time on this tonight and
> have it working, though I'm not sure exactly why. I downloaded the
> perl source for the server and started hacking around with it using
> ActivePerl 5.6.1.635. I eliminated possible causes like the port
> being used, firewall problems, etc. by copying the perl that opens the
> ports into a small test file - that worked fine. I then started
> adding code from the real server to that test file until I was able to
> get it to fail, then traced from there.
>
> Anyway - to get it working I had to do the following:
>
> - Stub out Slim::Utils::Misc::hostaddr(). My server has a pretty
> complicated networking setup - it connects to a VPN, then acts as a
> NAT router for the remote network for other machines on my LAN. So
> maybe something about that configuration is confusing things.
>
> - Add a call to checkVersion() in slimserver.pl right after the
> initsettings() call in the init sub (line 246 in the current version).
> I have no idea why this is necessary, but it is - perhaps something
> about checking for the new version makes subsequent connections work.
> I had found that I needed to delete my prefs file every time for it to
> work - I narrowed that down to the need to delete the checkVersion
> entry in that file. It looks like when that entry is missing it
> triggers some code that calls checkVersion earlier than if you just
> set it to 1. Once I got to that point it was easier to just call it
> via brute force than write a script that would perform surgery on my
> prefs every time I start the server.
>
> Anyway, hopefully this will be of some help. If someone more familiar
> with the server source would like me to run any experiments to help
> track down the real issues I'd be glad to - I'd rather not have to put
> these hacks in myself every time a new version comes out, anyway :)
>
> -->Mike
>
>> I just got my Squeezebox today and I'm having a hard time getting the
>> server running on my machine (Win2K Pro SP2). I get an error stating
>> that another copy of the server is running. I've looked over the
>> archives and I see that this is generated when it can't get port
>> 3483. I checked using netstat -a and I don't see anything using the
>> port; I also used nc as suggested in one of the messages (I think it
>> was nc -l -u -p 3483) and I didn't see any errors.
>> Any suggestions on how I can proceed other than reinstalling the OS?
>> The server runs fine on another machine on my network (WinXP), but
>> the Win2K machine is the one I have running 24/7 so I've got to get
>> it working there. Any ideas would be appreciated!
>> -->Mike
>>