Getting nothing in server when I use getmenu

14 views
Skip to first unread message

Paul Coleman

unread,
Dec 29, 2022, 7:09:07 PM12/29/22
to Earthworm Community Forum
Running EW v 7.10 on Centos6.8. the campus where we are, is going through infrastructure changes so no net for a few days. However we have a private local network used for local stations. The server has 2 Ethernet ports connect to both networks. with the loss of the campus network, it should have been a simple matter of just switching the IP addresses that we use to connect the modules and the remote database(NAS). All IP addresses were changed to the local private network and the respective modules changed to reflect same but now getting no nothing in server from getmenu. Sniffwave shows that data is coming in from the local network still. I even when as far as to change the default gateway to the private network to see if that would assist but no change. is there any guidance that can be given on the issue?

Larry Baker

unread,
Dec 29, 2022, 7:30:45 PM12/29/22
to paul.ale...@gmail.com, Larry Baker, 'jona...@ntu.edu.sg' via Earthworm Community Forum
Paul,

What do the log files say?  Have you enabled any debug options to increase the verbosity?  Try traceroute to the waveserver port that you say is not responding to getmenu.  You don't say whether the getmenu client and the waveserver are on the same subnet.  This sounds like a network configuration issue.
On Dec 29, 2022, at 4:09 PM, Paul Coleman <paul.ale...@gmail.com> wrote:

Running EW v 7.10 on Centos6.8. the campus where we are, is going through infrastructure changes so no net for a few days. However we have a private local network used for local stations. The server has 2 Ethernet ports connect to both networks. with the loss of the campus network, it should have been a simple matter of just switching the IP addresses that we use to connect the modules and the remote database(NAS). All IP addresses were changed to the local private network and the respective modules changed to reflect same but now getting no nothing in server from getmenu. Sniffwave shows that data is coming in from the local network still. I even when as far as to change the default gateway to the private network to see if that would assist but no change. is there any guidance that can be given on the issue?

--
--
You received this message because you are subscribed to the Google
Groups "Earthworm Community Forum" group.
 
To post to this group, send an email to earthwo...@googlegroups.com
 
To unsubscribe from this group, send an email to
earthworm_for...@googlegroups.com
 
For more options, visit this group at
http://groups.google.com/group/earthworm_forum?hl=en

---
You received this message because you are subscribed to the Google Groups "Earthworm Community Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to earthworm_for...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/earthworm_forum/36ac123a-1f07-46b2-8e74-b77a08db436fn%40googlegroups.com.

Paul Coleman

unread,
Dec 29, 2022, 9:47:58 PM12/29/22
to Earthworm Community Forum
Hey Larry,
the NAS and the server are connected via a linksys router so they are on the same subnet, the export_generic log says that its not connecting and exiting. the setup was working just yesterday the only thing changed was the IP address due to the work on the campus Infrastructure making it unavailable right now.

Larry Baker

unread,
Dec 29, 2022, 10:01:47 PM12/29/22
to paul.ale...@gmail.com, Larry Baker, 'jona...@ntu.edu.sg' via Earthworm Community Forum
Paul,

You can use telnet, ping and traceroute to probe server ports.  You don't have to rely on the Earthworm software only.  For example, if the server that export_generic is trying to reach uses port 16002 at IP address 192.168.0.2, can you telnet 192.168.0.2 16002?  If the server is listening, telnet will connect, even though it will not be able to communicate.  If that fails, can you ping the server IP address?  I.e., ping 192.168.0.2.  If that fails, you have network configuration errors.  You can use traceroute to watch what the ping probe is doing.  I.e., traceroute 192.168.0.2.  Assuming you had no need to change port numbers, the fact that export_generic says it cannot connect is a pretty strong indication the network is not quite configured properly on one or more of your systems.  Have you examined the firewall rules on your systems?  If NFS is involved, make sure the server export rules allow the mounts you need.  Use showmount -e <server-IP-address> to show the export rules for the NFS server at <server-IP-address>.

Reply all
Reply to author
Forward
0 new messages