Trouble connecting agent to master in PESTPP-SEN parallel run (NetPackage::send error) #344
-
|
I am trying to implement parallel runs for pestpp-sen using the Manager to Agent communication mode. I have fully configured all necessary files according to the PEST++ user manual. First, I opened a working folder and successfully started the master with the command:C:\Users\MSI-PC\Desktop\new\all_site\json_230101_SoilMax_FullIrr_Corn>pestpp-sen Corn.pst /H :4040 Then, I made a complete copy of the working directory and attempted to start an agent from the copied folder using the command:
I would greatly appreciate any help or advice on how to solve this problem. Thank you very much! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
This is almost always a network security thing...can you try "localhost" instead of "MSI" for the hostname? |
Beta Was this translation helpful? Give feedback.
-
|
I just tried it, and even after switching to a different computer, the same error still occurs. It seems that this is an error unrelated to the computer itself. |
Beta Was this translation helpful? Give feedback.
-
|
Are you using a VPN? Do you have a firewall and/or real-time threat detection active? All of that security-theater stuff can interfere with tcp/ip comms...Do you have access to an um-managed/free-range computer that you can test with? |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much for our discussion. I’ve now figured out the core issue—it all comes down to whether the selected port is open for TCP communication. If you use this as a keyword to search online, you’ll find many helpful posts on the topic. On most computers, the TCP access on many ports is blocked or restricted in some way. Fortunately, we can manually designate a specific port to allow TCP access and remember its number. The tutorial I followed came from: https://cn.windows-office.net/?p=15057 This was a perfect troubleshooting process. Thank you—I’m very happy today! |
Beta Was this translation helpful? Give feedback.
-
|
I'm very sorry—turns out this issue was actually a misunderstanding. It wasn’t as complicated as I originally thought. The reason it wasn’t running before was simply because there were Chinese characters in the file path. Once I changed everything to numbers, the problem disappeared. I really didn’t expect that to be the cause! |
Beta Was this translation helpful? Give feedback.
I'm very sorry—turns out this issue was actually a misunderstanding. It wasn’t as complicated as I originally thought. The reason it wasn’t running before was simply because there were Chinese characters in 10000 the file path. Once I changed everything to numbers, the problem disappeared. I really didn’t expect that to be the cause!