Updating from 2.0.6 to 2.2.9 (CentOS 6)

[shaun666]

Hi,

First off many thanks for making Zabbix freely available, it really is an excellent monitoring system that has saved our bacon on numerous occasions.

I want to upgrade from 2.0.6 to 2.2.9. I though it would be a good idea to build a new Zabbix server and a new Mysql Server to make fresh start so to speak.

In order to get a nice smooth upgrade I want to get our 2.0.6 system running on the new hosts and then execute the upgrade to 2.2.9 on the new hosts.



The original system is running CentOS 6 with Mysql v 5.1.68.

The new system is the same but with MySQL v 5.1.73

I made a dump of the mysql and zabbix databases and imported them into the new MySQL system without any errors

I then installed

zabbix-2.0.6-1.el6.x86_64.rpm
zabbix-java-gateway-2.0.6-1.el6.x86_64.rpm
zabbix-server-2.0.6-1.el6.x86_64.rpm
zabbix-web-2.0.6-1.el6.noarch.rpm
zabbix-agent-2.0.6-1.el6.x86_64.rpm
zabbix-sender-2.0.6-1.el6.x86_64.rpm
zabbix-server-mysql-2.0.6-1.el6.x86_64.rpm
zabbix-web-mysql-2.0.6-1.el6.noarch

on the new zabbix server along with Apache, PHP and php-ldap

Finally I copied over zabbix_server.conf and edited this to point at the new MySQL server.

The first time I started the new system up I got the initial configuration screen. Clicking through this showed the system was configured correctly. The database Test Connection was successful with the credentials I supplied.

Here is the php-ldap info:
# rpm -q php-ldap
php-ldap-5.3.3-46.el6_6.x86_64

The problem is when I try to login I get the "Probably php-ldap module is missing" error message

Looking in the zabbix server log I can see it is polling hosts and generally doing what it ought to.

I suspect I'm made a trivial mistake but I would be grateful for some pointers

Thanks

Shaun

[shaun666]

I thought it help others if I explained briefly how I fixed this.

Zabbix 2.0.6 supports 3 methods of authentication: Internal, LDAP and HTTP.

AFAIK only one method can be chosen so if LDAP is selected you cannot create valid internal users in order to get a backdoor in, so to speak.

Our system is configured to use LDAP so I edited the function ldapLogin in /usr/share/zabbix/api/classes/CUser.php so that it always returned true.

Once I had logged in with my usual Zabbix Super Admin account I could update the old LDAP config so that it used Secure LDAP on port 636 instead of plain text LDAP on port 3268.

I then restored CUser.php now it all works perfectly.

HTH

S