jEmplode Ethernet Problem

Posted by: zexpe

jEmplode Ethernet Problem - 05/09/2005 17:29

Doh. Upgraded my Linux box to Fedora Core 4, installed Sun Java 1.5, and now jEmplode can't see my empeg over ethernet. Downgraded java back to 1.4.2, and still, same problem.

Anyone else have jEmplode working with Fedora Core 4??

Cheers,
Ross
Posted by: mschrag

Re: jEmplode Ethernet Problem - 05/09/2005 21:16

Any exceptions printing on the console?
Posted by: zexpe

Re: jEmplode Ethernet Problem - 06/09/2005 18:51

Good to see that you're still providing support Mike!

I can ping and telnet into my empeg no problem so the network connection is fine. Here's the output from both v56 and v70 of jEmplode:
Posted by: zexpe

Re: jEmplode Ethernet Problem - 06/09/2005 18:52

Only one attachment per post... so here's the jemplode70 output:
Posted by: mschrag

Re: jEmplode Ethernet Problem - 07/09/2005 11:05

So you are doing a direct connection (i.e. ip address is typed in) vs a broadcast, right? You might try broadcast to see if it makes a difference? Double check the address that is typed in in the options dialog to make sure it's valid and doesn't have any spaces or something weird around it?

Do you have more than one network interface on there?
Posted by: zexpe

Re: jEmplode Ethernet Problem - 07/09/2005 17:44

The direct connection worked before, but in fact I had both broadcast and direct connection options checked. Choosing broadcast only I receive the "No devices found" message after a while. Occasionally I receive this console output too (see attachment - doesn't look good!).

I have other network connections set-up (e.g. wireless), but all are deactivated when I'm connecting to the empeg via a direct cross-over cable connection with static ip addresses. The network is working, the pc can both see and access the empeg, it's just jEmplode can't see the empeg.

It's very mysterious, and I'm fairly sure I'm not doing anything stupid (though I've said that too soon before...).

Ross
Posted by: mschrag

Re: jEmplode Ethernet Problem - 07/09/2005 21:57

can you run it

java -Ddebuglevel=30 -jar jemplode.jar

also

java -fullversion

and post the output?
Posted by: Mataglap

Re: jEmplode Ethernet Problem - 08/09/2005 19:07

Offtopic, but maybe someone's willing to answer a question. How is -fullversion more useful than -version?

Quote:
C:\Documents and Settings\nbardsley>java -version
java version "1.4.2_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_07-b05)
Java HotSpot(TM) Client VM (build 1.4.2_07-b05, mixed mode)

C:\Documents and Settings\nbardsley>java -fullversion
java full version "1.4.2_07-b05"

C:\Documents and Settings\nbardsley>
Posted by: mschrag

Re: jEmplode Ethernet Problem - 08/09/2005 20:52

-version didn't print all that back in the day ... it used to be that fullversion just printed slightly more than "1.4.2". now it's just muscle memory
Posted by: Mataglap

Re: jEmplode Ethernet Problem - 08/09/2005 22:44

Cool, thanks! I've sucessfully forgotten all of the annoying details about earlier JDKs.
Posted by: zexpe

Re: jEmplode Ethernet Problem - 09/09/2005 14:34

1) java -fullversion:
java full version 1.4.2_02-b03

2) java -Ddebuglevel=30 -jar jemplode.jar:

2a) when broadcasting:
SSDPDiscoverer.startDiscovery0: null
SSDPDiscoverer.startDiscovery0: capella/152.78.192.72
Broadcasting on 255.255.255.255...
Broadcasting on 152.255.255.255...
Broadcasting on 152.78.255.255...
Broadcasting on 152.78.192.255...

2b) when connecting to a specified IP address:
see attachment

Hope this helps,
Ross
Posted by: mschrag

Re: jEmplode Ethernet Problem - 09/09/2005 17:12

is that 152.xxx ip address range correct?
Posted by: mschrag

Re: jEmplode Ethernet Problem - 09/09/2005 17:13

Invalid argument or cannot assign requested address ?? What in the world ... What specifically is the value in the unicast address field in options?
Posted by: mschrag

Re: jEmplode Ethernet Problem - 09/09/2005 17:15

from a google search on this error:
"fetch/store fails immediately with a stack trace starting as follows:

ERROR [SwingWorker] 2005-06-28 18:16:28,748:
edu.gemini.oodb.OodbClientBase - Connection problem
java.net.SocketException: Invalid argument or cannot assign requested
address
...with several more lines...
This is a known problem with the Fedora Core 4 people. The FC4 installation notes suggest that users upgrade their JRE to the latest 1.5_04 distribution from Sun at http://java.sun.com. We've tested this and confirmed that it fixes the fetch/store problem. After additional testing, we will make a special FC4 version available on the Gemini ftp site."
Posted by: zexpe

Re: jEmplode Ethernet Problem - 11/09/2005 20:04

Quote:
is that 152.xxx ip address range correct?


Yes

Quote:
Invalid argument or cannot assign requested address ?? What in the world ... What specifically is the value in the unicast address field in options?


The "Connections Options" specific address is:
152.78.192.74

Pinging this extract string works fine:
[rsc@capella ~]$ ping 152.78.192.74
PING 152.78.192.74 (152.78.192.74) 56(84) bytes of data.
64 bytes from 152.78.192.74: icmp_seq=0 ttl=255 time=0.672 ms
64 bytes from 152.78.192.74: icmp_seq=1 ttl=255 time=0.664 ms

Quote:
The FC4 installation notes suggest that users upgrade their JRE to the latest 1.5_04 distribution from Sun


I gave the 1.4.2 output as I knew that was working fine in FC1... as I mentioned earlier 1.5.0 also isn't working, but I didn't use it in this test in case it was a secondary issue of using 1.5.0! Anyway, 1.5.0 doesn't give much in the way of debug output:

[rsc@capella lib]$ java -fullversion
java full version "1.5.0_04-b05"

[rsc@capella lib]$ java -Ddebuglevel=30 -jar jemplode.jar
SSDPDiscoverer.startDiscovery0: null
SSDPDiscoverer.startDiscovery0: capella/152.78.192.72
SocketConnection (10923757): actually open

Does "actually open" mean "already open" or "OK, it's open" ??

Thanks for your help so far,
Ross
Posted by: mschrag

Re: jEmplode Ethernet Problem - 11/09/2005 23:29

Go back to the unicast and turn off broadcast and send me the output w/ 1.5? "Actually open" is my debug output that says when the socket is truly opened (vs just creating the object that encapsulates the connection)
Posted by: zexpe

Re: jEmplode Ethernet Problem - 12/09/2005 07:02

Er, Mike, that was just a specific address connection in the last debug option, I didn't have broadcast turned on in that example... should I be seeing more debug output?? I could leave it running for a while longer to see if anything happens. That debug output is all I see for just a minute or so, before I give up and close down jEmplode.

Ross
Posted by: mschrag

Re: jEmplode Ethernet Problem - 12/09/2005 13:44

There was no exception on the last debug output -- Did it actually fail?
Posted by: zexpe

Re: jEmplode Ethernet Problem - 12/09/2005 19:23

No... but it didn't succeed either! ;-)

It doesn't find the empeg and it doesn't seem to time-out within 5-10 minutes. That's all the debug output it provides in that time.

Ross
Posted by: mschrag

Re: jEmplode Ethernet Problem - 12/09/2005 22:56

This is a really odd problem ... Can you run it, let it get into discovery, then send it a kill -QUIT and send me all the output that prints out on the console?
Posted by: mlord

Re: jEmplode Ethernet Problem - 13/09/2005 00:30

Mmm.. I wonder if this is the buggy empeg ethernet issue showing up..

None of my empegs will talk to (J)Emplode or anything else until after I ping them once or twice. Well, sometimes they work without the ping, but..

Cheers
Posted by: zexpe

Re: jEmplode Ethernet Problem - 13/09/2005 19:16

You asked for it! ;-)

See attachment.

Ross
Posted by: mschrag

Re: jEmplode Ethernet Problem - 13/09/2005 22:07

Interesting -- it appears to be hung trying to download the installed version # from hijack. It actually found and connected to your player, though.

Did you reinstall and not install Hijack maybe? Try turning off "use hijack when possible" in options and see if that connects?
Posted by: tfabris

Re: jEmplode Ethernet Problem - 13/09/2005 23:09

And if that's the issue, perhaps Jemplode could, in a future version, be a bit more robust in how it checks for Hijack?
Posted by: mschrag

Re: jEmplode Ethernet Problem - 14/09/2005 00:43

Actually it passed the preliminary check for hijack -- As far as jEmplode is concerned he has hijack, it's just hanging trying to read data from it. I'm not really sure what happens if you let the socket timeout, which it eventually will. I've never seen it hang where it is ... Really weird problem.
Posted by: zexpe

Re: jEmplode Ethernet Problem - 14/09/2005 07:57

Quote:
Did you reinstall and not install Hijack maybe?


Nope... I haven't messed around with the empeg since upgrading to Fedora 4. I suspect my old Fedora 1 PC will still be able to connect to the empeg, though I couldn't say for sure (I won't go into the various reasons why I can't test that right now!). Of course, it's possible something has gone screwy on the empeg which is just coincident with my OS upgrade...

I'll try turning off "use hijack" tonight.

Thanks,
Ross
Posted by: zexpe

Re: jEmplode Ethernet Problem - 14/09/2005 18:10

Quote:
Try turning off "use hijack when possible" in options and see if that connects?


Hey, that worked! :-) It's nice to see the player's database again!

So what does the "Use Hijack When Possible" option do; i.e. what am I missing out on by turning it off?

Thanks for your support - this must be the best internet forum in history.

Still, none the wiser about what caused the problem though...

Cheers,
Ross
Posted by: mlord

Re: jEmplode Ethernet Problem - 14/09/2005 18:48

Quote:

Still, none the wiser about what caused the problem though...


If you want to help diagnose/fix it, then turn that option back on, and connect up a serial console while you try it again. Anything Hijack has an issue with, gets reported on the serial console.

Cheers
Posted by: mschrag

Re: jEmplode Ethernet Problem - 14/09/2005 20:30

You really don't WANT that option off -- It means you're not going to use Hijack for anything, which means you fall back to old Empeg protocol (specifically uploading and downloding are done entirely with FTP when you have hijack enabled). But follow Mark's instructions now and maybe it will reveal itself ...

Oh wait.

Is it possible you have a software firewall that is blocking passive ftp connections back to your machine from the Empeg?
Posted by: mlord

Re: jEmplode Ethernet Problem - 14/09/2005 20:35

Actually, Hijack does not work with passive FTP. I think you meant to ask about (active) FTP connections.

Cheers
Posted by: mschrag

Re: jEmplode Ethernet Problem - 14/09/2005 22:04

Yep -- My bad ...
Posted by: zexpe

Re: jEmplode Ethernet Problem - 16/09/2005 16:27

Quote:

Oh wait.

Is it possible you have a software firewall that is blocking passive ftp connections back to your machine from the Empeg?


The solution is always an obvious one!! Yep, I dug around in the system settings; disabled all firewalls and hey presto I can connect to the empeg using Hijack again. Seems Fedora 4 has some more stringent default firewall settings than Fedora 1. After a bit more fiddling I now have both a firewall and a decent empeg connection. Thanks for the conversation! Problem solved.

Cheers,
Ross