2nd remote host can not be conected

[GoogleCodeExporter]

1.99.26c and 1.99.25

I configured two mpd servers in the network.

Both servers are accessable if the minion-client has one as localhost and 
the other as remote hosts configured. So far so good.

If both servers are remote ( on a 4th client)  I can't connect to the 2nd
server anymore, just the 1st server is accessable.

NOW:

I deleted both servers and just configured the one I couldn't connect
to earlier. Guess what. Now even that single connection didn't work.

I checked my network setup three times. Ping/SSH is working without issues.

How can I completely remove Minion for testing? Even after removing the
ADD-ON the config files do still exist.

Comment1: I am running two different mpd versions on the servers.

Original issue reported on code.google.com by kls.schlz@gmail.com on 17 Jul 2009 at 12:32

[GoogleCodeExporter]

The config files are stored in your home directory, on Windows this is: 
c:\documents and settings\%username%

The files in the format: .mpm_*.js

There are also preferences stored in firefox starting with: extensions.mpm.  
You can
get to this by typing about:config in firefox's address bar.

Original comment by cseic...@gmail.com on 17 Jul 2009 at 10:05

[GoogleCodeExporter]

BTW: I am running Linux (Mint Gloria)

Original comment by kls.schlz@gmail.com on 18 Jul 2009 at 3:32

[GoogleCodeExporter]

I'm sure you realized this, but just in case, home for linux is 
/home/your_username.

Did it help removing the config files and firefox preferences?

Since you are running the client on linux, a good troubleshhoting step you can 
do is
to launch firefox from the command line and watch the debug messages that 
minion will
dump to the console.  This could help both with this problem and issue 54.  
Lines of
particular interest would look like this:

socketTalker for server localhost:6601 created.

socketTalker for server localhost:6601 destroyed.

close status = 2152398861

Killing socket

Any time you see a close status other than 0 there is a problem.  This could 
also
show if the server name or port is getting mangled somehow.

Original comment by cseic...@gmail.com on 19 Jul 2009 at 4:57

[GoogleCodeExporter]

I experience exactly the same close status ID as you describe. 

Original comment by kls.schlz@gmail.com on 19 Jul 2009 at 9:26

[GoogleCodeExporter]

Hi

Can someone try again with a recent version of MPM please ? A test with a 2.0.6 
would
be great. I'm using a multi-server config with no problems at all.

Thanks

Original comment by aurelien...@gmail.com on 16 Apr 2010 at 9:19

[GoogleCodeExporter]

Drop this bug, as everything is working fine (so far) both linux and Windows.

Original comment by aurelien...@gmail.com on 25 Apr 2010 at 8:44

• Changed state: Invalid