Upgraded from 2.2.7 to 2.4.7 and cannot open host discovery rules

[Jason]

I've just upgraded zabbix server from 2.2.7 to 2.4.7

On all of my templates if I try and open some discovery rules (such as interface or file discovery on windows templates) they I just just a blank grey screen. Has anyone else seen this?

[Jason]

More information... It seems the rules I cannot open are the ones that had filters in them. All the ones that didn't use filters seem to open ok... Is it possible some of them didn't upgrade properly?

Edited : I've tried importing some 2.4.X templates such as the OS_AIX one and on that I cannot open the discovery rules there so it's not a problem with the templates themselves I think.

I've attached the screen I'm seeing. We're running on Centos 6 (2.6.32-573.12.1.el6.x86_64) with nginx as our web server.

If i remove the filter (by exporting template, removing filter and re-importing) then I can edit the discovery rule until i re-add the filter where it goes back to not working again.

[Jason]

I think it's due to acceleration... I've managed to find this in my nginx log..

[error] 14039#0: *807 FastCGI sent in stderr: "PHP message: PHP Fatal error: Invalid opcode 153/1/8. in /var/www/html/zabbix/include/classes/helpers/CConditionHelper.php on line 172" while reading upstream, client: XX.XX.XX.XX, server: zabbix.mycompany.com, request: "GET /zabbix/host_discovery.php?form=update&itemid=22907&sid=2c 58df944e5efab1 HTTP/1.1", upstream: "fastcgi://unix:/var/run/zabbix.socket:", host: "zabbix.mycompany.com", referrer: "https://zabbix.mycompany.com/zabbix/host_discovery.php?&hostid=10075&sid=2c58df944e5ef ab1"

[Jason]

If I switch back to apache then everything works as it should, but not in nginx...

nginx config below in case done something stupid...

server {
        listen 443 ssl default_server;
        server_name zabbix.mycompany.com;
        access_log  /var/log/nginx/zabbix.log;
        error_log  /var/log/nginx/zabbix.error;
        ssl on;
        ssl_protocols TLSv1.2;
        ssl_certificate /etc/pki/tls/certs/combined.crt;
        ssl_certificate_key /etc/pki/tls/private/cert.com.key;
        ssl_stapling on;
        ssl_stapling_verify on;
        ssl_trusted_certificate /etc/pki/tls/certs/full.pem;
        root /var/www/html;
        index index.php index.html;
        client_max_body_size 5m;
        client_body_buffer_size 128k;

        location ~ \.php$ {
                fastcgi_pass unix:/var/run/zabbix.socket;
                fastcgi_read_timeout 150;
                include fastcgi_params;
                fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
                fastcgi_param SCRIPT_NAME $fastcgi_script_name;
        }

        location ~*  \.(jpg|jpeg|png|gif|css|js|ico)$ {
                expires max;
                log_not_found off;
        }

        location ~ /\.ht {
        deny all;
        }

        location ~ /\. {
        deny all;
        }
}

[Firm]

What php version are on apache and nginx?

[Jason]

PHP 5.3.3 (cli) (built: Jul 9 2015 17:39:00)
Copyright (c) 1997-2010 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies

nginx version: nginx/1.8.1
built by gcc 4.4.7 20120313 (Red Hat 4.4.7-16) (GCC)
built with OpenSSL 1.0.1e-fips 11 Feb 2013
TLS SNI support enabled

Server version: Apache/2.2.15 (Unix)
Server built: Dec 15 2015 15:50:14
Server's Module Magic Number: 20051115:25
Server loaded: APR 1.3.9, APR-Util 1.3.9
Compiled using: APR 1.3.9, APR-Util 1.3.9
Architecture: 64-bit
Server MPM: Prefork
threaded: no
forked: yes (variable process count)

[Firm]

Check if you have eaccelerator module enabled in php-fpm.

[Jason]

It was enabled in nginx although I tried to disable it...It's definitely off in apache.

it's not configured as on in php-fqm

[Firm]

Try to set
always_populate_raw_post_data = -1 either in php.ini or php-fpm pool options.

[Jason]

Tried that. Doesn't seem to help.

For some reason I can't seem to disable eaccelerator when using nginx and fastcgi despite the eaccelerator config saying it shold be off.

[Firm]

Disable eaccelerator module loading completely. Find where

extension=eaccelerator.so

lives, probably /etc/php/mods-available, and comment it out.

[Jason]

I've done that...

I think fastcgi is loading eaccelerator as it's easily turned off in apache...

I'm missing something simple here...