Hi all,
today I gave the latest available appliance a try.
We are running ESXi and vCenter 5.1 (soon: 5.5).
We had 2.0.6 running in a separate VM but wanted to upgrade to a 64bit OS.
While deployment and basic startup was fine, the configuration was way more tricky than before.
I copied the "old" MySQL DB to the new system and for now everything is running fine.
But now the "rants":
- why the heck you zabbix guys have removed almost all of the available Yast2 modules? That makes configuration a lot more complicated.
- for what reason zabbix database is NOT using the "innodb_file_per_table" setting?
- why is there no rule for Suse's firewall which allows incoming zabbix trapper connections? Or at least a file in /etc/sysconfig/SuSEfirewall2.d/services to enable the selection of "zabbix" as an allowed service?
- /usr/sbin/fping* for ping checks seem to have wrong permissions. Mine have "-rws--x--- root zabbix" now...
- no swap configured. Ok, that was consistent to the 2.0.6 appliance and I can live w/o it
- frontend. Some php files still use "getUrl()" (or similar) rather than "basename(getUrl())" making it partially impossible to run zabbix frontend behind a proxy, despite the fact that there are patches available since 1.8.xx
Ok, that was it. I did not want to be offensive, but rather want to give a feedback.
All in all, 2.0.6 ran fine when apache's error and access logs were redirected to /dev/null (as mentionend we run it behind another web server via mod_proxy and do the logging there).
I want to say thank you for your work and hope you get my remarks not as an offense.
today I gave the latest available appliance a try.
We are running ESXi and vCenter 5.1 (soon: 5.5).
We had 2.0.6 running in a separate VM but wanted to upgrade to a 64bit OS.
While deployment and basic startup was fine, the configuration was way more tricky than before.
I copied the "old" MySQL DB to the new system and for now everything is running fine.
But now the "rants":
- why the heck you zabbix guys have removed almost all of the available Yast2 modules? That makes configuration a lot more complicated.
- for what reason zabbix database is NOT using the "innodb_file_per_table" setting?
- why is there no rule for Suse's firewall which allows incoming zabbix trapper connections? Or at least a file in /etc/sysconfig/SuSEfirewall2.d/services to enable the selection of "zabbix" as an allowed service?
Code:
## Name: Zabbix Server ## Description: Open ports for Zabbix Server # space separated list of allowed TCP ports TCP="zabbix-trapper"
- no swap configured. Ok, that was consistent to the 2.0.6 appliance and I can live w/o it
- frontend. Some php files still use "getUrl()" (or similar) rather than "basename(getUrl())" making it partially impossible to run zabbix frontend behind a proxy, despite the fact that there are patches available since 1.8.xx
Ok, that was it. I did not want to be offensive, but rather want to give a feedback.
All in all, 2.0.6 ran fine when apache's error and access logs were redirected to /dev/null (as mentionend we run it behind another web server via mod_proxy and do the logging there).
I want to say thank you for your work and hope you get my remarks not as an offense.