Bug #582
no error message if mysql used on version compiled without mysql support
Status: | Closed | Start date: | 04/19/2011 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | - | |||
Target version: | - | |||
Resolution: | fixed | Pull request: | ||
Affected Versions: | OpenNebula 2.2 |
Description
If one tries to use mysql on a version compiled without mysql support, the server simply dies with to messages to the console or to the logs. When doing this, the server should emit an error that mysql is not supported by the compiled version being used.
History
#1 Updated by Ruben S. Montero about 10 years ago
Hi,
I can not reproduce this:
- OpenNebula compiled with
scons -j3 sqlite=yes mysql=no
- oned.conf
# Sample configuration for MySQL DB = [ backend = "mysql", server = "localhost", port = 0, user = "oneadmin", passwd = "oneadmin", db_name = "opennebula" ]
I obtain this:
> oned Aborting oned, MySQL support not compiled! > one start Aborting oned, MySQL support not compiled! oned failed to start
Maybe this is a compilation issue. gcc should not define MYSQL_DB for this to work.
#2 Updated by Charles Loomis about 10 years ago
I should have been more precise. There is no message when starting via the init.d script as the stderr/stdout are eaten and no message appears in the service log.
#3 Updated by Ruben S. Montero about 8 years ago
- Status changed from New to Closed
- Resolution set to fixed
- Affected Versions OpenNebula 2.2 added
Should be fixed by the packages...