[Note] Access denied for user 'cmonexporter'@'localhost' (using password: YES)

Comments

9 comments

  • Official comment
    Avatar
    Krzysztof Ksiazek

    Hi,

    We identified another issue related to the password handling for Prometheus exporters. The fix is ready but it has not yet been released. We hope to publish it soon: please look for the next version of ClusterControl (1.7.3). Sorry for the inconvenience.

    Please make sure that you restart the cmon process after the upgrade (service cmon restart) and that you re-deploy the agents (or kill them and let ClusterControl restart them).

    Thanks,

    Krzysztof

    Comment actions Permalink
  • Avatar
    Bart Oles

    Hello Lisandro,

    The problem has been addressed with one of the patches. You can find details here:

    https://support.severalnines.com/hc/en-us/articles/212425943-ChangeLog
    - 2019-05-16 clustercontrol-controller-1.7.2-3185 clustercontrol-1.7.2-6032
    "Monitoring/SCUMM: postgres_exporter and mysql exporter too URL password encoding

    Please update to the latest version and restart cmon service with

    $cmon service restart

    Kind regards,
    Bart

    0
    Comment actions Permalink
  • Avatar
    Lisandro Eloir Iuzviak

    I've udpated the cmon as you suggested but the problem persists. I've also disabled the dashboard, cleaning any user for cmonexporter and re-enabling just after reinstalling Prometheus and agents.

    ClusterControl UI Version
    1.7.2.6137-#c07278
    ClusterControl CMON Version
    1.7.2.3246
     
    2019-06-12T14:39:36.850805Z 361084 [Note] Access denied for user 'cmonexporter'@'localhost' (using password: YES)
    2019-06-12T14:39:46.850553Z 361095 [Note] Access denied for user 'cmonexporter'@'localhost' (using password: YES)
    2019-06-12T14:39:56.850755Z 361106 [Note] Access denied for user 'cmonexporter'@'localhost' (using password: YES)
    2019-06-12T14:40:06.850789Z 361117 [Note] Access denied for user 'cmonexporter'@'localhost' (using password: YES)
    2019-06-12T14:40:16.850629Z 361128 [Note] Access denied for user 'cmonexporter'@'localhost' (using password: YES)
    2019-06-12T14:40:26.851735Z 361139 [Note] Access denied for user 'cmonexporter'@'localhost' (using password: YES)
    2019-06-12T14:40:36.850871Z 361150 [Note] Access denied for user 'cmonexporter'@'localhost' (using password: YES)
    2019-06-12T14:40:46.850503Z 361161 [Note] Access denied for user 'cmonexporter'@'localhost' (using password: YES)
    2019-06-12T14:40:56.850440Z 361172 [Note] Access denied for user 'cmonexporter'@'localhost' (using password: YES)
    2019-06-12T14:41:06.850485Z 361183 [Note] Access denied for user 'cmonexporter'@'localhost' (using password: YES)
     
     
    0
    Comment actions Permalink
  • Avatar
    Simon Brown

    I can confirm the same issue persists after latest update: Controller: 1.7.2.3246, Frontend: 1.7.2.6137-#c07278

    2019-06-28 9:23:14 140252485011200 [Warning] Access denied for user 'cmonexporter'@'localhost' (using password: YES)
    2019-06-28 9:24:14 140252484704000 [Warning] Access denied for user 'cmonexporter'@'localhost' (using password: YES)
    2019-06-28 9:25:14 140250867279616 [Warning] Access denied for user 'cmonexporter'@'localhost' (using password: YES)

    0
    Comment actions Permalink
  • Avatar
    Lisandro Eloir Iuzviak

    the password used to authorize the cmonexporter was the cause of the problem.. after changing it to a new one, and reenabling the agent the mysql export started working. Thanks for pointing the way to solve it.

    0
    Comment actions Permalink
  • Avatar
    Simon Brown

    Hi, how did you change the password?

    0
    Comment actions Permalink
  • Avatar
    Krzysztof Ksiazek

    Hi,

    In /etc/cmon.d/cmon_X.cnf (where X is the ID of the cluster) you will find:

    db_exporter_password=somestring

    To make it work, remove all non-alphanumeric characters. Then restart cmon process (service cmon restart) and re-deploy the agents from the UI. This should make it work.

    0
    Comment actions Permalink
  • Avatar
    Lisandro Eloir Iuzviak

    First, you  can check whether your password was set properly

    1) Do this in the ClusterControl controller server
      grep 'exporter' /etc/cmon.d/cmon_<cluster_id>.cnf​

    save the result to use on step 2.

    2) Run this at least on one of the nodes in the cluster
    mysql -u<admin-user> -p -e "select user, host, authentication_string from mysql.user where user like '%exporter%'";
    mysql -u <admin-user> -p -e "select password('<the-password-from-#1-result>)';"

     

    If the result differs, there is a reason that might be causing you troubles.

    If they are the same then probably the password itself is causing troubles, sometimes a ' / '  or other special symbols do not work as they should, so I change the password on the cmon_<cluster_id>.conf file, to a password that I'm sure works , restart cmon service and re-enabled the agent. You may need to delete any user created on mysql prior to re-enabling, not sure this is really required, but I've done it anyway.

    0
    Comment actions Permalink
  • Avatar
    Simon Brown

    This worked. Thank you very much.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk