Z-Push no longer works after switch from Zarafa to Kopano and local install to packaged version
-
More news. I’m not going to say that it’s fixed as I don’t want to be premature, but I made an interesting discovery. If I disable PHP’s opcache then things seem to start working again. Two devices now seem to be working for over an hour. I’m going to check again tomorrow and get the other users to test before I get too excited. My guess is that something device specific is getting cached, and that’s what’s causing things to break. My inital reports each time about devices working could be due to the first connection occurring when the cache is empty. I’ll update tomorrow about whether it’s still working this time.
@Merlin2104 Thanks, I appreciate the offer. Hopefully that won’t be necessary.
@fbartels Unfortunately we don’t have a subscription, otherwise I would have contacted support already! I’m 99% certain that our Apache vhosts are fine, as we didn’t change any of them, and only one of them is configured to access Z-Push.
-
Okay, I can pretty confidently say that the problem is with opcache. Both the locally installed and packaged versions of Z-Push work when opcache is disabled. For some reason I can’t get opcache.blacklist_filename to play ball, so I have to completely disable opcache to get Z-Push to work. As we’re hosting a number of other sites I’ve had to proxy Z-Push through to FPM, with opcache disabled on FPM, and leave everything else running on mod_php so that it can still use opcache. Any ideas what might be causing the problem? I see from the Z-Push documentation that opcache is supported, and I haven’t noticed it causing problems with any of our other sites or services. Here is our relevant config from php.ini:
[opcache] opcache.enable=1 ;opcache.enable_cli=0 opcache.memory_consumption=256 ;opcache.interned_strings_buffer=4 ;opcache.max_accelerated_files=2000 ;opcache.max_wasted_percentage=5 ;opcache.use_cwd=1 ;opcache.validate_timestamps=1 ;opcache.revalidate_freq=2 ;opcache.revalidate_path=0 ;opcache.save_comments=1 ;opcache.load_comments=1 ;opcache.fast_shutdown=0 ;opcache.enable_file_override=0 ;opcache.optimization_level=0xffffffff ;opcache.inherited_hack=1 ;opcache.dups_fix=0 ;opcache.blacklist_filename= ;opcache.max_file_size=0 ;opcache.consistency_checks=0 ;opcache.force_restart_timeout=180 ;opcache.error_log= ;opcache.log_verbosity_level=1 ;opcache.preferred_memory_model= ;opcache.protect_memory=0As you can see, everything is at the defaults except for the memory consumption.
PHP 5.6.30+dfsg-0+deb8u1
Apache 2.4.10-10+deb8u11 -
Hi kitserve,
now that you mentioned opcache I remember that there were some users who had similar issues with Z-Push and opcache. However I’ve seen other servers with opcache enabled and iOS devices syncing without issues.
What apache modules do you have enabled? Maybe one of them interferes with opcache and Z-Push?
Manfred
-
Maybe! I’ve no idea which might or might not conflict. Here are the modules:
user@host:~$ ls /etc/apache2/mods-enabled/ access_compat.load authn_core.load autoindex.conf dir.load headers.load negotiation.load proxy_fcgi.load reqtimeout.load ssl.load actions.conf authn_file.load autoindex.load env.load mime.conf pagespeed.conf proxy_html.conf rewrite.load status.conf actions.load authz_core.load cgi.load expires.load mime.load pagespeed.load proxy_html.load setenvif.conf status.load alias.conf authz_groupfile.load deflate.conf fastcgi.conf mpm_prefork.conf php5.conf proxy_http.load setenvif.load xml2enc.load alias.load authz_host.load deflate.load fastcgi.load mpm_prefork.load php5.load proxy.load socache_shmcb.load auth_basic.load authz_user.load dir.conf filter.load negotiation.conf proxy.conf reqtimeout.conf ssl.conf -
Hi kitserve,
in the past there was an issue with pagespeed: https://forums.zarafa.com/showthread.php?11592-devId-and-devType-allways-empty&highlight=pagespeed
Manfred
-
Interesting. That seems to have fixed it, thanks for the pointer. Strange that it only broke for us with the new version of Z-Push.
