Upgrade from v2.08 to 2.2 - How to step by step

[leadout_kv]

Hello

Let me start by saying I'm a Linux newb.

I have a fully functioning v2.08 Zabbix server running "openSUSE 12.3 (Dartmouth) (x86_64)". I implemented the Zabbix server using an Appliance VM so not much configuration was needed other than to change IP info and other minor tweaks. I would like to upgrade this Zabbix server at some point to Zabbix v2.2.

update - this is a Zabbix v2.08 server that is operating in an isolated environment with no access to the internet.

I've read the upgrade documentation but the steps are very high level and not having actual "step by step" instructions. I'm stuck where the step says "# 4 Install new server binaries - You may use pre-compiled binaries or compile your own."

How do I install (step by step) the new server binaries?

Thanks

[leadout_kv]

anyone? Help with step by step would be appreciated.

Thanks

[Dave_sutfene]

upgrade

i'll wil start tomorrow updating my 2.0.9 installation on ubuntu to version 2.2.0

i'll come back to you later.
but any help from others would be great

FYI i made a clean installation of ubuntu (with X) and installed apache/mysql/php and zabbix from the source code. i already had a 2.0.8 (suse) server with historical data which i want to preserve so i had to make a new server in 2.0.9 and upgrade it to 2.2.0

[Dave_sutfene]

upgraded

i did this to upgrade:

1. Download the source fies
2. tar -zxvf zabbix-2.2.0.tar.gz
3. cd zabbix
4. sudo apt-get install libxml2-dev
5. ./configure --enable-server --enable-agent --with-mysql --with-net-snmp --with-libcurl --with-libxml2
6. Sudo Make install
7. cd frontends/php
8. cp -a . /var/www/zabbix

if there was an error upgrading the database you can see it in the server log
some say it can take a moment maybe i was to quick

but i did this and now it works:
mysql -u root -p
use zabbix;
ALTER TABLE items ADD lastvalue VARCHAR(60);
service zabbix-server restart

[leadout_kv]

i did this to upgrade:

1. Download the source fies
2. tar -zxvf zabbix-2.2.0.tar.gz
3. cd zabbix
4. sudo apt-get install libxml2-dev
5. ./configure --enable-server --enable-agent --with-mysql --with-net-snmp --with-libcurl --with-libxml2
6. Sudo Make install
7. cd frontends/php
8. cp -a . /var/www/zabbix

if there was an error upgrading the database you can see it in the server log
some say it can take a moment maybe i was to quick

but i did this and now it works:
mysql -u root -p
use zabbix;
ALTER TABLE items ADD lastvalue VARCHAR(60);
service zabbix-server restart

Dave - thank you very much for posting these instructions. Its appreciated. I will use them to upgrade my v2.08 server and report back on how it went.

[ceinmart]

I've updated

Hi,

Just sharing.
I'm use zabbix at opensuse 12.3 too.
My, isn't appliance, I've installed it manually. But I'm using 100% RPMs packages.

To admin my packages I use the zypper command, configured to official Opensuse repositories.

Just last week (february/2014) the relase of Zabbix 2.2 was availabe at official opensuse repositories.

To update, is very very very simple.
I just execute :

# refresh the repository information
zypper ref 
# download all pending packages to update
zypper up -d 
# execute the update by self.
zypper up

My zabbix was updated to version 2.2.1-3.1 (opensuse repository)

After the update, I get only one issue.
The systemctl service initialization wasn't create, so the service of the server and the agent at this server wasn't started.

If I execute a "systemctl" and check the list of services, all zabbix services was gone.

Then I was started the services manually first :

cd /etc/init.d
./zabbix-server start
./zabbix-agentd start

Here take few minutes to zabbix-server become available , I think was because of the automatically database structure update what they should execute.
When I try access the front-end they give me a message saying my database still at version 2.0.9 ... the after few minutes, it back to work.


To fix the service is quite simple :

chkconfig zabbix-server on
chkconfig zabbix-agentd on

If you execute the systemctl after that, it wasn't updated immediately and I don't remember if I solve with "systemctl daemon-reload" or was after I restarted the host.