Hide Forgot
Description of problem: As zabbix-server-mysql is named to specify mysql it would seem appropriate that it firstly check if mysql-server is already installed and if not, install it. Since zabbix may use differing DB this package would seem the best place to satisfy that dependency. I of course discovered the lack of mysql-server and it was somewhat amazed that installation of zabbix-server-mysql didn't pull in mysql-server. Version-Release number of selected component (if applicable): How reproducible: yum install zabbix-server-mysql ; start mysql server = fail Steps to Reproduce: 1. yum install zabbix-server-mysql (on target machine without existing mysql server). 2. start the mysql server 3. Actual results: If the install target has no mysql-server one isn't provided by zabbix-server-mysql Expected results: Check that there is indeed a mysql server on target and provide one if not upon zabbix-server-mysql installation. Additional info:
The zabbix package can't require that the database server must be installed on the same host as the zabbix server. So the actual dependency on the database server's client access library is sufficient.
(In reply to comment #1) > The zabbix package can't require that the database server must be installed on > the same host as the zabbix server. So the actual dependency on the database > server's client access library is sufficient. Ok, then which component of the zabbix package group resolves the lack of a mysql server or at least checks and outputs to an admin the lack of same either local target or one which is available to the local target? This package is intended to optimize zabbix-server for mysql .. if there is no mysql server available either on target or available to target then an action should be taken of some form that is apparent to the installer. This package seemed to me the best place to resolve that and I see your point as valid so I will amend: Check for existence of mysql server either on target or available to target.
The existence or non-existence of a MySQL server isn't really something we can check for, especially given the limited tools. I personally prefer to run my database servers on a dedicated host, especially for large databases that see lots of I/O or run complex queries. Having a package force the installation of a database server on a host that I don't want it on would irritate me greatly. At some point you need to trust the server admin to know what they are doing and figure out that they need to install a MySQL server...