I posted something similar here, but have since run this again for the 1.5.2 to 1.5.3 upgrade and wanted to add more details to the procedures:
1. Download and unpack the 1.5.x source
2. Though I have a backup of the entire VM ( I have Zabbix running virtualized ), I made a backup of the zabbix database:
-> #mysqldump -u<user> -p<pass> zabbix > zabbixbackup.sql
3. Compiled/built the new zabbix server. I personally used the following:
-> ./configure --enable-server --with-mysql --with-net-snmp –with-libcurl # for MySQL + WEB monitoring.
4. Ran mysql upgrade scripts - instead of trying to cat patches.sql from the command line, I launched mysql shell and ran the scripts from within mysql
-> mysql -u<username> -p<password> database
-> mysql>source <patch.sql>
5. Made backup of existing frontend and then recursively copied the new frontend to the web directory
- cp -R /var/www/zabbix /var/www/zabbix_<ver>
- changed to the frontends/php directory in the install folder
- cp -R * /var/www/zabbix
1. Download and unpack the 1.5.x source
2. Though I have a backup of the entire VM ( I have Zabbix running virtualized ), I made a backup of the zabbix database:
-> #mysqldump -u<user> -p<pass> zabbix > zabbixbackup.sql
3. Compiled/built the new zabbix server. I personally used the following:
-> ./configure --enable-server --with-mysql --with-net-snmp –with-libcurl # for MySQL + WEB monitoring.
4. Ran mysql upgrade scripts - instead of trying to cat patches.sql from the command line, I launched mysql shell and ran the scripts from within mysql
-> mysql -u<username> -p<password> database
-> mysql>source <patch.sql>
5. Made backup of existing frontend and then recursively copied the new frontend to the web directory
- cp -R /var/www/zabbix /var/www/zabbix_<ver>
- changed to the frontends/php directory in the install folder
- cp -R * /var/www/zabbix