Developer Portal Analytics Error: "Error fetching 'Analytics' or 'Bill' details"

[#1]

I am currently trying to setup a demo to show some of the capabilities of API-M. For my scenario I am using the trial version. The API Portal seems to be working fine for me but problems start occuring on the Dev Portal side.

Steps i've done on API Portal side:

• Create API
• Create Rate Plan
• Create Product with API and Rate Plan

Steps i've done on Dev Portal side:

• Register User for Application
• Create Application for User with specific API

Afterwards I made some API calls against the particular endpoint with the assigned API key.

On the Dev Portal side if I open the Application Info, no analytics data is shown with the message "No Data".

Also on the "My Workspace" tab under "Cost" i am receiving the Error Message "An error occurred while fetching 'Analytics' or 'Bill' details. For further assistance, please contact support".

Thanks for any input in advance.

[former_member814031]

These problems are indicated by the output of the status command showing the cluster members database status as anything other than Active (Primary), unless a transitory operation is running.

For a transitory operation, the status command might show various statuses other than Active (Primary) during clustering operations and upgrades; these statuses are usually Starting, Stopping, SST-Running-X% and sometimes, for a few minutes, Preparing. These states are not a cause for concern unless the operation completed more than 15 minutes earlier, or it returned an error message.

Make the following checks:

Check that all members of the cluster are listed in the output of the status command when run on every node. If there is a mismatch between nodes, this can be corrected by explicitly setting the cluster members on each node with the set_cluster_members <member_1_IP> <member_2_IP> <member_3_IP> ... command.

On one of the nodes, run the command bootstrap_cluster -bf; this will try to restart the database on all the nodes, forcing it to stop and restart.

You can use the stop_db and start_db commands to attempt to restart the database on an individual node.

Check the log file /var/log/syslog for MySQL errors.

Do not attempt to modify the MySQL configuration; if problems persist after checking the above then gather logs with the generate_logs command and open a support ticket.

Regards,

Rachel Gomez

[former_member751036]

Any inputs will be highly appreciated

[former_member751036]

Hello Kevin,

Is your issue resolved. Can you please share resolution