Update from Zabbix 2.0.2 to 2.0.4

[ira]

Hello all,

I am using Debian Squeeze and build Zabbix from source.
At the moment I have 2.0.2 using mysql but there are some bug fixes which I need. That's why I want to update from 2.0.2 to 2.0.4

I know the procedure about 1.8.x -> 2.0.x but what is about updating inside of 2.0.x?

I found this guide here: https://www.zabbix.com/forum/showthr...ghlight=update

I already:
- configured and installed the sources from 2.0.4 (./configure + make install)
- updated /var/www/zabbix with the new frontend sources

Then I checked the sql-scripts and there were a lot of differences in data.sql
diff -by zabbix-2.0.2/database/mysql/data.sql zabbix-2.0.4/database/mysql/data.sql

I also found differences in
diff -by zabbix-2.0.2/upgrades/dbpatches/2.0/mysql/patch.sql zabbix-2.0.4/upgrades/dbpatches/2.0/mysql/patch.sql

That leads me to the conclusion that there ARE changes in the database between 2.0.2 and 2.0.4.

I found a page (https://www.zabbix.org/svn/zabbixorg...e_incremental/), which describes a possibility to make a patch between db versions, but it doesn't include version greater than 2.0.0

Is there a short and stable way to update the mysql db from 2.0.2 to 2.0.4?

Thanks
Ira

[tchjts1]

Not sure what to tell you. General rule of thumb is that there is no updates to the DB in minor release versions.

I have gone from 2.0.2 --> 2.0.3 --> 2.0.4 without doing any DB updates. Other than housekeeper being a resource hog when it runs, I haven't come across any issues that would point to needing to make changes at the DB level.

[ira]

Thanks for the reply.

I tried to analyze the diffs from yesterday and found out that the most changes are about changed item descriptions. That's really harmless.

The rest were changes of 5-digit numbers on some items, which I couldn't evaluate if they are important or not.

I backup up my old version and installed the new one and now I will wait some time to see if everything goes well. If there are some problems I'll report them here.

[ira]

Well, there is a problem. I have a great peak in the db size after the update.

Normally I have a very flat curve for the db size growing
- for 3 months it is grown from 6,89 to 7,01 GB.

Now, after the update, it went from 7,01 to 8,02 GB (!). It is about 1 GB for a single day.
That is a little bit scary if this trend remains.

There are not any additional items, templates or hosts added in this time, which could couse this.

I tried to free some space as I:

1. altered some tables in MySQL 5.1.49-3 /InnoDB
alerts;
events;
history_log;
history;

This didn't free any additional space

2. I set the MaxHousekeeperDelete in zabbix_server.conf from 5000 to 500000.

3. I changed the values in Administration, General, Housekeeper, Do not keep actions older than (in days)
Do not keep events older than (in days)

from 365 to 90

Till now there is no improvement.

Is there anything else what I could do to stop this growing db size trend?
Any help will be appreciated, I'm almost in despair

[heaje]

with mysql , imnodb does not clear disk space after it claims it. nothing you do in your database (short of recreating tables) will get your disk space back.

[ira]

Well, the matter is, that after the update of the binaries and the GUI, there is some definite change in the the way the db is filled.

It is not about directly discussing the Innodb but the behavior of Zabbix after the update.

[ira]

In the most guides I saw, it was enough to stop the zabbix server process and then start them again, when the update is done. I suppose that the mysql processes should be restarted too.

The problem were the "zabbix busy history syncer processes" which made a lot of mess (big spikes) every 10 minutes. This behavior matched exactly with the growing of the "values processed by zabbix server per second" which jumped every 10 Minutes from 50 to 170 (!) and then went down again.

It seems that there is one very simple solution to this problem: Just restart the zabbix server after update!

That helped me.