Database Error 90003 Eve-ng -

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.

If you’ve spent any time building labs in EVE-NG, you know the feeling. You’re in the zone, dragging nodes onto the canvas, linking interfaces, and powering up routers. Suddenly, you hit a wall.

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.

If nothing else works:

First, stop the service:

systemctl stop mysql Now, run the MySQL safe recovery mode to force a repair of the EVE database:

EVE-NG relies on a local MySQL database to store everything: user credentials, lab topologies, node configurations, and permission settings. When the EVE-NG GUI (the web interface) cannot talk to the database backend, it throws this error. 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 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.

systemctl restart mysql Now, check if it is actually running: In this post, we’re going to dissect what

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

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.