Container based setup migration issue

Container based setup migration issue

In the container-based setup with the new developer update, there is an error as below: (Access denied for user)

Please suggest how to fix this issue.


To fix this issue, kindly login into the database using the below command and create one more user.

1. Login to the database

mysql -uroot -proot -h0.0.0.0

2. Create a report user using the below command.

CREATE USER 'report'@'%' IDENTIFIED BY 'beta';

GRANT SELECT ON multicore.* TO 'report'@'%' IDENTIFIED BY 'beta';

FLUSH PRIVILEGES;
    • Related Articles

    • SOP for Docker based VuSmartMaps

      Introduction This document aims to provide standard operating procedure to handle diagnostics and troubleshooting of VuSmartMaps container based installations. Assumptions This SOP assumes a container installation of vuSmartMaps catering to the new ...
    • [ICICI] Issue With SMS Alerts After DR

      At ICICI setup, we are not getting proper SMS alerts, even in the notification index same fields are available. The SMS script is as shown below: This issue is being faced after moving to DR. Please suggest the solution. ANS -  Previous version 8.4r1 ...
    • Issue with analyser logstash

      Question: In intellect analyser logstash is in excited state. Even after restarting the service it’s again going into excited state. There is no space issue also . Data has stopped coming from last night 11:00pm.  Following errors seen in logstash ...
    • Issue in URL Monitoring

      We had an issue with the URL monitoring, on checking we found out that the network team started blocking HTTP traffic from their location (where our stand alone shipper is), so instead of using the stand alone shipper we used our main shipper (Cloud) ...
    • [RBL] Issue With Data Indexing

      There is following issue with the RBL project.  We are monitoring ESB as an application in RBL. Currently, I am not able to see proper data getting indexed. Redis queue building up and dequeuing is also happening properly. There is no error in ES as ...