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 stop mysql Now, run the MySQL safe recovery mode to force a repair of the EVE database:
repair table auth_behavior; repair table labs; repair table nodes; repair table users; exit; Finally, kill the safe mode process and restart normally: Database Error 90003 Eve-ng
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.
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. In this post, we’re going to dissect what
You try to start a node, save the topology, or even log in, and you’re met with a red pop-up: .
mysql -u root eve_ng_prod Once inside the MySQL prompt ( mysql> ), run the repair command: When the EVE-NG GUI (the web interface) cannot
It’s vague. It’s frustrating. And it usually brings your lab building session to a screeching halt.