PHP errors on screens.php after upgrade to 2.0

[James2k]

Hi,

I just updated by Zabbix install from 1.8 to 2.0. I'm running a CentOS 6.4 VPS server using the Zabbix packages in EPEL. For the upgrade I shutdown both the agent and server before hand, then removed the 1.8 packages, installed the 2.0 packages then ran the patch.sql for the upgrade of the MySQL database which completed without problems. Everything appeared to work OK until I saw the following PHP errors on the screens page

Not sure what to make of it, I couldn't find anything useful, I tried re-running the images.sql file on my DB but this hasn't changed anything.

Any help would be great, this was working on 1.8!

Thanks,

James

[trikke76]

can't see the errror but verify these php.ini settings

php_value max_execution_time 300
php_value memory_limit 128M
php_value post_max_size 16M
php_value upload_max_filesize 2M
php_value max_input_time 300
php_value date.timezone Europe/Brussels

those are the things that u need to adjust in 2.0

[James2k]

Hi,

Thanks for your reply. I wasn't able to actually post in the PHP code in the original thread (Got trapped in a false positive validation error, regarding multiple links which I assume it was because it referred .php pages), so I was waiting for the approval of my post.

The problem was specifically with the Local Network graph on the screen page. I got various PHP errors related to image functions for this graph like imagesx(), imagesy(), imagecreatefromstring(), mainly getting:

expects parameter 1 to be resource, boolean given

I don't have the original line numbers it was referencing

As I had just recently started using Zabbix 1.8, and found the EPEL repo have the 2.0 packages, I just dropped the tables in the database and reinstalled, which resolved the problem. Though I thought I carried out all the upgrade steps from 1.8.

I will check out my php.ini to confirm everything is in order, but I don't think any of my PHP settings were flagged in the front end install.

Not really a solution, but that's how I solved it.

Thanks,

James

[trikke76]

ok

so probably something went wrong with the upgrade

good it's working now