Where Does OpenNebula Store Config and Credentials?
Where OpenNebula keeps its daemon config and admin credentials on Linux, and what breaks password changes.
Last updated
OpenNebula keeps its frontend config in etc with the main daemon file naming drivers and defaults. Admin credentials live separately in the service home with strict permissions. Logs accumulate under var log per daemon.
Password changes fail when the file and the database drift apart, which is the classic lockout. The frontend runs on Linux only, so all paths here are Linux paths. Environment overrides can relocate auth for fenced or container installs. Cluster drivers and hook scripts reference the config tree, so version it together.
Where OpenNebula stores this, by platform
/etc/one/oned.conf
Main daemon config plus per user auth files in the service home. Logs sit under var log per daemon. Password changes need file plus database updates together.
Frequently asked questions
I changed the oneadmin password and login fails. How do I fix it?
Update the one_auth file plus the user record with the password command, then restart the service. The daemon reads the file at startup while the database holds its own copy. Changing one without the other locks the login.
Where are OpenNebula logs when the daemon will not start?
Open the oned and scheduler logs under the var log tree for startup failures. Auth files use strict permissions that break when copied loosely. The environment variable can redirect auth elsewhere for fenced setups.
Notice an outdated path? Let us know.