New install - Cluster details cannot be retrieved

Follow

Indy Nagpal

• July 19, 2017 04:49

I am new to ClusterControl and currently trying it out.

I've installed Controller: 1.4.2.1981, Frontend: 1.4.2.3465

I've tried to add an existing MySQL Cluster that is setup in the following fashion:

master > replica > replica

The cluster seems to be added successfully. When I go to Settings > Clusters, I can see it there, with a green dot on the left.

However on the main page (the one after logging in), I'm getting the following message:

Cluster details cannot be retrieved. Please check the CMON process status (service cmon status). Also, ensure the dcps.apis token matches the rpc_key in /etc/cmon.cnf.

I have ensured that CMON process is running. I've checked that the relevant ports are open:

tcp        0      0 127.0.0.1:9500          0.0.0.0:*               LISTEN      65607/cmon
tcp        0      0 127.0.0.1:9501          0.0.0.0:*               LISTEN      65607/cmon
tcp6       0      0 :::9510                 :::*                    LISTEN      1207/cmon-events
tcp6       0      0 :::9511                 :::*                    LISTEN      1200/cmon-ssh

I've validated that the token matches everywhere.

I've restarted the CMON and Apache services.

I've rebooted the server.

However, I get the same error.

Any help in debugging and sorting this would be appreciated.

Thanks

Indy

0

• Official comment

  

  Ashraf Sharif

  • July 20, 2017 03:07

  Hi Indy,

  The problem was due to internal DNS system that you use resolves to the primary IP address. Thus, CMON has to listen to the primary IP address (it was default to 127.0.0.1 only). To do this, add the following line inside /etc/default/cmon:

  RPC_BIND_ADDRESSES="127.0.0.1,{primary IP address}"

  Then, restart CMON service.

  Regards,
  Ashraf

  Comment actions Permalink
• 

  Ashraf Sharif

  • July 19, 2017 06:10

  Hi Indy,

  On ClusterControl server, ensure the value of 'token' inside dcps.apis table is identical with 'rpc_key' inside /etc/cmon.cnf. You can use the following command to retrieve and update it:

  $ mysql -uroot -p -e 'select * from dcps.apis'
  $ grep rpc_key /etc/cmon.cnf
  {rpc_key value}
  $ mysql -uroot -p -e 'update dcps.apis set token = {rpc_key value} where id = 1'

  Then, verify if the database cluster can be seen from ClusterControl UI.

  Regards,
  Ashraf

  0

  Comment actions Permalink
• 

  Indy Nagpal

  • July 19, 2017 09:26

  Thanks for your quick response Ashraf.

  As I said earlier that I had validated that the token is the same everywhere...

  However, I've once again validated that by using the commands your provided above. The token is the same everywhere.

  After updating the token as per the commands you had provided, I tried to add the cluster again.

  But the same error:

  Cluster details cannot be retrieved. Please check the CMON process status (service cmon status). Also, ensure the dcps.apis token matches the rpc_key in /etc/cmon.cnf.

  Is there any way for me to get some more visibility on what is going behind the scenes?

   

  0

  Comment actions Permalink
• 

  Ashraf Sharif

  • July 19, 2017 23:28

  Hi Indy,

  I'd like to see the environment you are running to expedite the troubleshooting. Would it possible for you to set up a screen sharing session via Teamviewer or join.me? I suggest you to create a support ticket for this and provide the login credentials so we can jump in.

  Regards,
  Ashraf

  0

  Comment actions Permalink
• 

  Indy Nagpal

  • July 20, 2017 00:24
  • Edited

  Hi Ashraf

  Sure, I can setup a join.me meeting. I'm in New Zealand Time Zone. What timezone are you in? And what time suits?

  I've logged a ticket at: https://support.severalnines.com/hc/en-us/requests/3943

  0

  Comment actions Permalink
• 

  Russell Holley

  • July 02, 2019 17:41

  Hello, I am having the same problem. I confirmed the keys match and added the bind address but no luck.

  0

  Comment actions Permalink
• 

  Paul Namuag

  • July 02, 2019 21:52

  Hi Russell Holley,

  Have you filed a Zendesk ticket about this? I'm not sure if you had but similar issue has been filed earlier. If not please create a ticket and we'll help you through Zendesk.

  Thanks.

  0

  Comment actions Permalink

Please sign in to leave a comment.