Database Error 90003 Eve-ng Official

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. Database Error 90003 Eve-ng

repair table auth_behavior; repair table labs; repair table nodes; repair table users; exit; Finally, kill the safe mode process and restart normally:

systemctl restart mysql Now, check if it is actually running:

If nothing else works:

killall mysqld systemctl start mysql systemctl restart eve-ng Warning: This resets user accounts to default (admin/eve). It does NOT delete your lab topologies or images.

mysql -u root eve_ng_prod Once inside the MySQL prompt ( mysql> ), run the repair command:

It’s vague. It’s frustrating. And it usually brings your lab building session to a screeching halt. You try to start a node, save the

Bookmark this guide. If you run EVE-NG long enough, you will see this error again. When you do, just SSH in, restart MySQL, and get back to learning.

mysqld --datadir=/var/lib/mysql --skip-grant-tables --skip-networking & Next, log into MySQL manually (no password required due to skip-grant):