admincenter and test the connectivity Warnning
Afficher commentaires plus anciens
Unable to identify the problem
Matlab is working fine but these warnings are not resolved by the application. When i use admincenter and test the connectivity the following warning occurs
Kindly Guide Me How To Fix It
ID # Start Time Stop Time Executing Node Subject Node Test Category Test Description Result Message
1 Sep 19, 2012 7:26:48 PM Sep 19, 2012 7:26:50 PM ac2-pc ac2-pc PORT_CONNECT PingServerSocketHost Test SUCCESS
2 Sep 19, 2012 7:26:48 PM Sep 19, 2012 7:26:50 PM aclp2 ac2-pc PORT_CONNECT PingServerSocketHost Test *WARNING Host AC2-PC does not respond to java.net.InetAddress.isReachable(). *
3 Sep 19, 2012 7:26:49 PM Sep 19, 2012 7:26:52 PM ac2-pc aclp2 PORT_CONNECT PingServerSocketHost Test *WARNING Host ACLP2 does not respond to java.net.InetAddress.isReachable(). *
4 Sep 19, 2012 7:26:52 PM Sep 19, 2012 7:26:52 PM ac2-pc aclp2 PORT_CONNECT ConnectToServerSocket Test (remote port 27355) SUCCESS
5 Sep 19, 2012 7:26:53 PM Sep 19, 2012 7:26:53 PM ac2-pc ac2-pc PORT_CONNECT ConnectToServerSocket Test (remote port 27355) SUCCESS
6 Sep 19, 2012 7:26:53 PM Sep 19, 2012 7:26:54 PM aclp2 ac2-pc
Réponses (5)
Jason Ross
le 20 Sep 2012
You have a name resolution problem.
You need to check and possibly modify:
Firewall settings (if firewalls are in use)
DNS records (forward and reverse lookup)
DNS search domains
For each of the problematic hosts.
I can't tell you any exact fixes because you don't indicate what operating systems are in use, and these settings may or may not be accessible to you -- you will likely need root/Administrator privileges to change them. These settings can also vary widely by site, as well -- so you might need to contact networking staff (if you have them) to get the proper settings to make it work.
Please open new questions. Don't add on to existing ones that have been resolved for some time.
leo
le 21 Sep 2012
0 votes
3 commentaires
Jason Ross
le 21 Sep 2012
If you have two machines, you have a client-server environment. One is running the job manager, that's the server. The other is the client. They need to be able to talk to one another, and that means that their network settings must be correct.
If you have eliminated the firewall as the source of the error, then you need to move onto name resolution. I don't know how your site is set up in terms of DNS infrastructure, but you should be able to do the following in the Command Prompt, substituting the machine names and IP addresses where appropriate:
from machineA:
- ping (machineA IP address)
- ping machineA
- ping machineA.full.machine.name
- ping (machineB.ip.address)
- ping machineB
- ping machineB.full.machine.name
from machineB:
- ping (machineB IP address)
- ping machineB
- ping machineB.full.machine.name
- ping (machineA IP address)
- ping machineA
- ping machineA.full.machine.name
As for the exact settings to change, I can't tell you. They will most likely be in the following locations:
Computer Properties (Start, Computer, right-click, properties) gives you the "Name" and "Full Computer Name" properties.
You can change them under "Advanced System Settings" -- but you may need to be a Domain Administrator to (or have the right) to change the machine's name on the domain. Please, if you don't know what you are doing here, find someone who does -- if you change this setting and do not have the correct permissions, you'll remove your computer from the domain entirely and you'll likely be worse off than you are now. Proceed with caution!
The second location will be in the IPv4 Properties panel. You can get there by looking at the properties of your networking connection, selecting the "Internet Protocol Version 4" entry, clicking the "Advanced" tab, and then looking at the "DNS" tab. Items of interest here are the DNS search domains and DNS suffix.
Again, if you do not know what you are doing here, find someone who knows the proper settings for your environment. If you set up things improperly, you can end up with a machine that is in a worse state than now. And it's highly possible that your site has a certain way of setting this up, as well -- if you don't know what that is, find out first.
And please, please, please stop commenting on unrelated posts.
Jason Ross
le 21 Sep 2012
Modifié(e) : Jason Ross
le 21 Sep 2012
Leave the firewalls off until you get the DNS stuff figured out.
If you are using hostfiles, make sure that the above tests work with the short hostname and fully qualified one both ways.
Also, ensure that the NetBIOS setting is as you expect. It's a second level of name resolution beyond DNS, and it can add another place for the names to be inconsistent.
I would also make the assumption that both machines are on the same subnet as well as (likely) the same switch? Or are there other things on the network between the two hosts?
For port blocking, you can check with netstat -a and use "<matlabroot>\toolbox\distcomp\bin\nodestatus -infolevel 2" to see more information. But you must get the name resolution items down before you move on, as they are the foundation things build on.
Also, be on the lookout for multiple NICs where you might not expect them -- for example if you are on a laptop with a wireless connection and a wired connection -- that can cause confusion, especially if there is a duplicate hostname out on the network and it gets resolved first, since I think Windows favors a DNS response over the hosts file.
1 commentaire
Jason Ross
le 25 Sep 2012
You will need to populate the hosts file with the ip addresses and hostnames in the ways they will be addressed. According to Microsoft, this is one entry per line. So you would need these entries in the file. Make sure to use the same file on both PCs.
192.168.0.8 AC2-PC
192.168.0.8 ac2-pc
192.168.0.8 AC2-PC.YOURDOMAIN.COM
192.168.0.8 ac2-pc.yourdomain.com
192.168.0.11 ACLP2
192.168.0.11 aclp2
192.168.0.11 ACLP2.YOURDOMAIN.COM
192.168.0.11 aclp2.yourdomain.com
Note that the hostnames above are case-sensitive!!!! Were I doing this, I would keep everything lower-case, as is Internet convention. You also need to be sure that in DNS, the "Use hosts file for name resolution" is checked, to ensure that these names are resolved. You also need to replace "yourdomain.com" with the DNS domain settings for your network.
192.168.0.1 is by convention the preferred gateway for a network -- but that's a convention. You need to confirm it with the people who run your network.
DNS is another setting that is per-network. You need to check with the people who run your network what the DNS Server(s) should be set to. I have no way of knowing.
The bottom line here is that you need to get the network working properly. Right now it's not working properly, and you really need to reach out to people who understand how the network you are running on is configured, as correct hostname resolution is an absolute requirement for any clustered system to work.
leo
le 2 Oct 2012
0 votes
9 commentaires
Jason Ross
le 2 Oct 2012
Good to know that progress is being made!
This technote describes the ports that need to be open on the clients, workers and job managers -- be very careful as they are not all the same ports, and it's also version dependent.
Jason Ross
le 3 Oct 2012
Modifié(e) : Jason Ross
le 3 Oct 2012
From the technote:
In MATLAB 7.9 (R2009b) and later, the port range 27370 through 27470 should be open.
That's pretty straightforward. Open those on all client hosts. Onto the job manager and workers:
BASEPORT through BASEPORT + 5 + N TCP ports (where N is the number of worker nodes in your cluster). If you plan on running parallel jobs, or if you plan to use MATLAB pool or pmode, you will also need to open BASEPORT+1000 through BASEPORT+1000+5+ N TCP ports.
BASEPORT=27350
N=4
27350+5+4=27359.
So the first range is 27350-27359.
For the second range you add 1000 to each number to get 28350-28359.
Open these ports on the jobmanager and worker hosts.
Jason Ross
le 3 Oct 2012
Modifié(e) : Jason Ross
le 3 Oct 2012
Yes, I've had to test this with winxp before and added the ports. You might have some luck with the "netsh" command. There are some differences between capabilities in XP and Vista/7, but it might be helpful. Google for exact syntax in regards to the firewall and it's settings.
The technote explains the second set of ports:
If you plan on running parallel jobs, or if you plan to use MATLAB pool or pmode, you will also need to open BASEPORT+1000 through BASEPORT+1000+5+ N TCP ports.
I'm expecting that you'll be using matlabpool and/or parallel jobs. That's why you need to add them.
I've given you all the ports you should need to open on the client machines, worker machines and jobmanager host. Please refer to the tech note I referenced above for a full explanation.
leo
le 3 Oct 2012
Jason Ross
le 3 Oct 2012
If you are connecting from a client, 27370-27470 should be open, as well.
Jason Ross
le 3 Oct 2012
And you are already up and running ... it's just fiddling with the firewall settings that's tripping you up a bit. Once you get that figured out you are good to go.
Catégories
En savoir plus sur Job and Task Creation dans Centre d'aide et File Exchange
Produits
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!