You try to start a node, save the topology, or even log in, and you’re met with a red pop-up: .
First, stop the service:
In this post, we’re going to dissect what Error 90003 actually means, why it happens, and—most importantly—how to fix it permanently. In simple terms, Error 90003 is a MySQL database connection failure. Database Error 90003 Eve-ng
systemctl status mysql If it shows active (running) , go back to your web browser, clear your cache, and refresh. If the error is gone—congratulations, you’re done. If MySQL fails to start or restarting didn't fix the GUI, the database tables are likely corrupted. You try to start a node, save the
If nothing else works:
mysql -u root eve_ng_prod Once inside the MySQL prompt ( mysql> ), run the repair command: systemctl status mysql If it shows active (running)
systemctl restart mysql Now, check if it is actually running:
You try to start a node, save the topology, or even log in, and you’re met with a red pop-up: .
First, stop the service:
In this post, we’re going to dissect what Error 90003 actually means, why it happens, and—most importantly—how to fix it permanently. In simple terms, Error 90003 is a MySQL database connection failure.
systemctl status mysql If it shows active (running) , go back to your web browser, clear your cache, and refresh. If the error is gone—congratulations, you’re done. If MySQL fails to start or restarting didn't fix the GUI, the database tables are likely corrupted.
If nothing else works:
mysql -u root eve_ng_prod Once inside the MySQL prompt ( mysql> ), run the repair command:
systemctl restart mysql Now, check if it is actually running: