Ad Widget

**Anil** · 24-02-2005, 15:10

Hi

I affraid I can't answer your question....as i still haven't upgraded our zabbix server to 1.1alpha5.

However could you please tell me how you did your upgrade? - did you just run the "make" commands as you did for V1.0 and as a result did this just copy the new files over the old ones? Also was your old config (in relation to items monitored on a host) saved once you did the upgrade?

I have tried looking through old posts on this site and also the docs...but still not clear on how to do the upgrade...

**Alexei** · 24-02-2005, 15:13

Have you seen http://www.zabbix.com/manual_config_upgrading.php ?

**Anil** · 24-02-2005, 15:21

Yup,

I have downloaded V1.1alpha5 and also untared the files to a seperate directory. Where are the installation instructions?? - sorry for asking such a silly question...but am i just missing an obvious file? What command/s do i need to run next?

I run "less README", "less INSTALL" etc...but they just point to the .pdf doc

**rickardp** · 24-02-2005, 15:28

I downloaded the tar package, configured if with the compile options i needed.
and so on......

Problems encountered:
zabbix-1.1alpha5/upgrades/dbpatches/1.0_to_1.1alpha1/mysql/patch.sql
must be manually edited where the load_file insert is found
(load_file("/tmp/zabbix_upgrade/Notebook_small.png"))

Since I ran the patch.sql file and got errors I had to snip the inserts into a separate file......

On top of that I had to run the patch as root (don't ask me why)

A startscript for the server was not supplied so I copied the script zabbix-1.1alpha5/misc/init.d/redhat/zabbix_suckerd_ctl and replaced "suckerd"
with "server" and voilla!!!

Config file for zabbix_server.conf was copied to /etc/zabbix and edited with user/pass

PHP pages replaced the old ones, db.inc.php was edited, supplying user/pass

Still stuck with the errors in db.inc.php (it has something to do with "return mysql_num_rows($result);" ) More research in this is in progress

**rickardp** · 24-02-2005, 17:15

It seems that you get this kind of error if a SQL statement goes wrong.

In my case it was a database patch that wasn't applied (forgot one).

Apply the upgrade patches one after the other and be sure to really
'cd' down into the patch dir before running the patch.

Graphs still don't work, i'll try to search the forums as I recall seeing
threads about this....

Good luck with your upgrades (from what I can see now it's well worth doing it
for the GUI design alone)

**Alexei** · 24-02-2005, 17:16

Originally posted by rickardp

Still stuck with the errors in db.inc.php (it has something to do with "return mysql_num_rows($result);" ) More research in this is in progress

In most cases it indicates that your frontend (PHP files) is not in sync with current database schema. You may uncomment 'echo ...' in function DBSelect(), file db.inc.php, to see what SQL statement fails.

**rickardp** · 28-02-2005, 14:46

Graph problem
The graphs did not work with the previous versions of php and gd:

RH7.2 versions verified to run v1.0beta10
Running on a RH7.2 box with apache 1.3.x

PHP 4.1.12
GD 1.8.3

New versions verified to run V1.1alfa5
Running on a RH7.2 box with apache 1.3.x

PHP 4.3.10
GD 2.0.28

New problems:

The script that I used to get cpu usage from, now return negative values(??) when executed in the agent.
It will return the proper values when run from the prompt, very strange
indeed

UserParameter=cpu[usage],mpstat 1 1| awk '{ x++; if (x == 4) printf "%s\n", 100 - $7}'

Had to conjure up a new cpu[usage] i.e (100-cpu[idle]). I'm not very happy with 1 minute average cpu measurements since I miss the tops (I poll every 10s)
grep 'cpu\[idle1\]' /tmp/zabbix_agentd.tmp | cut -d ' ' -f 2 | awk '{printf "%s\n", 100 - $1}'
Is there a way to get a 100-idle item? I know that I can do the arithmetics in the trigger, but the graphs won't reflect the actual usage will it? Guess some people are hard to please

Ad Widget

V1.0Beta10 Upgrade to V1.1alfa5

V1.0Beta10 Upgrade to V1.1alfa5

Comment

Comment

Comment

Comment

Comment

Comment

Comment