AnsweredAssumed Answered

mcollective ping doesn't find new decoder appliance behind firewall SA 10.4.0.2

Question asked by David Mechsner on Dec 9, 2014
Latest reply on Dec 9, 2014 by Mudit

Like • Show 1 Like1
Comment • 6

While enabling an appliance at the SA 10.4 gui the script "/etc/puppet/scripts/addNode.py" is called the mco ping command.

In our environment, the new decoder appliance does not response the mco ping, altought the ampqs port is open

[root@saserver ~]# mco rpc rpcutil ping -I 0555a385-15aa-42bb-ac7f-568cf2406265

| [ > ] 0 / 1

Finished processing 0 / 1 hosts in 12017.67 ms

No response from:

0555a385-15aa-42bb-ac7f-568cf2406265

[root@saserver ~]#

Does anybody has an idea, how to trace that "mco rpc rpcutil ping" and which ports/direction should be opened in FW for mcollective/rabbitmq/puppet.

TIA

Mudit Dec 9, 2014 11:11 AM

Correct Answer

Then there would be some other reason why the ping is failing.

is there a time diff between SA and the device ?

See the reply in context

No one else had this question

Outcomes

Mudit Dec 9, 2014 10:48 AM

Please do the following: "Open firewall ports 8140 and 61614 from all non-SA Appliances to SA Server appliance. You must open these ports so that the SA server can discover all your appliances and services."

Actions

David Mechsner @ Mudit on Dec 9, 2014 11:02 AM

These ports are already open.

192.168.0.100 is our puppetmaster.local (sa-server).

[root@LogDecoder ~]# curl -v telnet://192.168.0.100:8140

* About to connect() to 192.168.0.100 port 8140 (#0)

* Trying 192.168.0.100... connected

* Connected to 192.168.0.100 (192.168.0.100) port 8140 (#0)

[root@LogDecoder ~]# curl -v telnet://192.168.0.100:61614

* About to connect() to 192.168.0.100 port 61614 (#0)

* Trying 192.168.0.100... connected

* Connected to 192.168.0.100 (192.168.0.100) port 61614 (#0)

It seems that the server still requires different ports during discovering.

Actions

Mudit @ David Mechsner on Dec 9, 2014 11:11 AM

Then there would be some other reason why the ping is failing.

is there a time diff between SA and the device ?

Actions

David Mechsner @ Mudit on Dec 9, 2014 11:18 AM

There is 1 hour difference.

[root@Decoder ~]# date

Tue Dec 9 18:16:41 CET 2014

[root@saserver ~]# date

Tue Dec 9 17:16:44 CET 2014

Actions

David Mechsner @ Mudit on Dec 9, 2014 11:24 AM

After ntp sync, it works! thanks a lot

Actions

Mudit @ David Mechsner on Dec 9, 2014 10:07 PM

Great.

Puppet and mco are heavily dependent on time sync.

It would fail even if there is few minutes difference.

Actions

6 Replies

Mudit Dec 9, 2014 10:48 AM
Mark Correct
Correct Answer
Please do the following: "Open firewall ports 8140 and 61614 from all non-SA Appliances to SA Server appliance. You must open these ports so that the SA server can discover all your appliances and services."
Like • Show 0 Likes0
Actions
- David Mechsner @ Mudit on Dec 9, 2014 11:02 AM
  Mark Correct
  Correct Answer
  These ports are already open.
  
  192.168.0.100 is our puppetmaster.local (sa-server).
  
  [root@LogDecoder ~]# curl -v telnet://192.168.0.100:8140
  * About to connect() to 192.168.0.100 port 8140 (#0)
  * Trying 192.168.0.100... connected
  * Connected to 192.168.0.100 (192.168.0.100) port 8140 (#0)
  
  [root@LogDecoder ~]# curl -v telnet://192.168.0.100:61614
  * About to connect() to 192.168.0.100 port 61614 (#0)
  * Trying 192.168.0.100... connected
  * Connected to 192.168.0.100 (192.168.0.100) port 61614 (#0)
  
  It seems that the server still requires different ports during discovering.
  Like • Show 1 Like1
  Actions
  - Mudit @ David Mechsner on Dec 9, 2014 11:11 AM
    Unmark Correct
    Correct Answer
    Then there would be some other reason why the ping is failing.
    is there a time diff between SA and the device ?
    Like • Show 0 Likes0
    Actions
    - David Mechsner @ Mudit on Dec 9, 2014 11:18 AM
      Mark Correct
      Correct Answer
      There is 1 hour difference.
      
           [root@Decoder ~]# date
           Tue Dec 9 18:16:41 CET 2014
      
           [root@saserver ~]# date
           Tue Dec 9 17:16:44 CET 2014
      Like • Show 0 Likes0
      Actions
    - David Mechsner @ Mudit on Dec 9, 2014 11:24 AM
      Mark Correct
      Correct Answer
      After ntp sync, it works! thanks a lot
      Like • Show 0 Likes0
      Actions
      - Mudit @ David Mechsner on Dec 9, 2014 10:07 PM
        Mark Correct
        Correct Answer
        Great.
        Puppet and mco are heavily dependent on time sync.
        It would fail even if there is few minutes difference.
        Like • Show 0 Likes0
        Actions

mcollective ping doesn't find new decoder appliance behind firewall SA 10.4.0.2

Outcomes

Related Content

Recommended Content