1. Home
  2. Knowledge Base
  3. Problems (EN)
  4. Node server does not start in Metaconsole Environment due to connectivity failure

Node server does not start in Metaconsole Environment due to connectivity failure

When a node server does not start in a Metaconsole environment, it is necessary to check the following:

  • Check status of the MySQL service of the Metaconsole DB:
[root@metaconsole ~]# service mysqld status
  • If it is stopped, start it with.
[root@metaconsole ~]# service mysqld start
  • Check¬† the connectivity from the node server to the meta:
172.21.0.100
[root@node ~]# mysql -u pandora -p pandora -h ipDBmeta
  • It may be that permissions have been lost, in case of not connecting:
[root@metaconsole ~]# mysql -u root -p
<mysql> grant all privileges on `pandora`.* to 'pandora'@'ipServerNode' identified by 'password';
Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support

Recent Discussions