The cause can be due to several things. First thing to check is if the system where your pandora server is installed actually can ping the remote system you want to monitor with host alive. If ping against that systems is working, then we can check some other things.
1. Check if the networkserver is enabled. It should if you are able to create the module, but it is worth it to check it just in case. Status of the networkserver can be checked on the tactical view. And you should find this line on the pandora_server.conf file:
2. Check if the system firewall/selinux is causing problems. To discard this posibility you can just disable it (In CentOS 7: "service firewalld stop", in CentOS 6: "service iptables stop" ; in both of them: "setenforce 0").
3. The module should initialize on few seconds after creating it if there is no external networki issues (security, congestion, etc.).
4. If the module is doesn't initialize, it is possible to modify the verbosity value of the server to increase the detail level of pandora_server.log file. Setting it to 10 like this:
verbosity 10And then monitoring the file pandora_server.log with "tail -f" for example should give us more information. Remember that the server daemon needs to be restarted after any .conf changes. To do it:
service pandora_server restart
Also, on the agent view there is a button to force the remote modules (fat green circumference), doing this with verbosity at 10 should display useful information on pandora_server.log. Remember to decrease the value of the verbosity paramenter after the testing, or the log may grow to problematic levels.