Pandora FMS Community

agent fails to communicate with server

pmitchel · 11 mar 2015, 21:01 · 5 mensajes · 72 visitas

  1. Inicio del debate

    Hello,   I'm getting the following error in the pandora_agent.log (note agent is running on a redhat linux box trying to communicate to the pandora_server which is on a Windows 2008 Server): 2015/03/11 12:54:08 - [error] - Error sending file '/tmp/samdev-pnet03.itcc.unc.edu.1425675766.data': [err] Cannot connect to eomonitor.ad.unc.edu on port : Connection timed out. (Note: I the pandora_agent.conf has the following within it: # Listening TCP port for remote server. By default is 41121 (for tentacle) # if you want to use SSH use 22, and FTP uses 21. server_port 41121 # Transfer mode: tentacle, ftp, ssh or local transfer_mode tentacle Looking at this, I opened up the group policy firewall and specifically opened port 41121 via a firewall incoming rule. (This is displayed under the "Server Policy:" pandora_agent (41121) TCP) If I open up the Inbound Rules local firewall on my Server box, I see the following: pandora_agent                                        ALL pandora agent (41121) TCP                    ALL (which are the descriptions I gave in the Group Policy), so I think they're active. If I load tcpview, however, nothing on my Server is monitoring, or listening to port 41121. So my question is: is there a tentacle application on the server that I need to launch in order for the agent to communicate? Thanks, Paul Mitchell

  2. Hello Paul, Exactly. You must start the tentacle server:        /etc/init.d/tentacle_serverd start Regards, Sergio

  3. Hello Sergio,     The pandora_agent, on the redhat box seems to have a tentacle daemon in operation: ps -ef | grep tent root    13476 31637  0 09:33 ?        00:00:00 sh -c tentacle_client -v -a eomonitor.ad.unc.edu -p 41121  "/tmp/samdev-pnet03.itcc.unc.edu.1425699398.data" 2>&1 >/dev/null root    13477 13476  0 09:33 ?        00:00:00 /usr/bin/perl /usr/bin/tentacle_client -v -a eomonitor.ad.unc.edu -p 41121 /tmp/samdev-pnet03.itcc.unc.edu.1425699398.data Furthermore, there is no /etc/init.d/tentacle_serverd file (which doesn't surprise me, as the Linux machine is the client). The pandora server is a windows box, hence,  there is no /etc/init.d directory. And the only tentacle app I find on the Windows box is tentacle_client in the util directory.  Is there no Windows tentacle server app? Note: had I been able to load the pandora_server onto the redhat machine, this problem wouldn't exists, but there I could not make the following work with the OS:  perl-Encode-Locale-, perl-base, and a version of glibc which worked with what already existed on the server and pandorafms_server-5.1SP2-150304.noarch.rpm Paul

  4. Ok, then we will do the following: configured in the agent configuration file as follows: xml_buffer 1 Send the XML file manually this way: tentacle_client -a file.data See what happens. Also run a Telnet to port 41121, just in case the Windows firewall is blocking it. Regards, Sergio

  5. Hello, the manual run times out, and the telnet never connects (for security reasons, we may not have a telnet daemonrunning on the Windows side). tentacle_client -a 152.2.46.56  samdev-pnet03.itcc.unc.edu.1426253573.data [err] Cannot connect to 152.2.46.56 on port 41121: Connection timed out. Looking at the firewall on the Pandora server (windows). please see first attachement (eomonitor.JPG) As for the group firewall defs, see the second attachment (group_eomonitor.JPG Note: I've just talked with the fellow who maintains the firewall in networking, we checked and the TCP packets are flowing through the firewall, eomonitor (the Pandora server) is simply not listening. The last attachment is a shot of tcpview on eomonitor, with the open ports listed numerically. Not there is nothing there for 41121. What does it take to get the Pandora_server to listen to port 41121 (by definition, isn't that what it's supposed to do)? Thanks, Paul Mitchell

    [

    ](//pandorafms.com/community/media/forum/0/18240=786-tcpview_eomonitor.JPG)

Entra en tu cuenta para publicar.