Just to report that I have installed 2.4.1 final and all works fine with the only modification needed for the /var/log that I had to change as follow:

drwxr-x—. 2 nginx z-push 4096 Apr 11 19:21 z-push

Hi emtie,

and the tasks didn’t re-recreate themselves since the deletion?

Manfred

Hi morfey,

perhaps this thread might be helpful: https://forum.kopano.io/topic/670/account-creation-with-current-outlook.

Manfred

@klausade , could you open a support ticket for this issue and send us the complete KOE-log when performing a GAB resync?

Normally Z-Push doesn’t require an apache restart and does also not enforce it. The new code is just used when it’s there.
Sounds very much like you have some php caching (like APC) installed that caches the old Z-Push code and is cleared on restart. Could that be?

replied in the other thread

no no… it isn’t 140 states, it’s a lot less.

anyway du -sh shows 14M

I have ran now:

z-push-admin -a fixstates

ran now and it took zero seconds…

Output is:

Checking flags of shared folders: Devices: 73 - Devices with additional folders: 0 - Fixed 0

@liverpoolfcfan yes, that would be all if you detect hierarchy changes in your backend. The code then checks again if the hierarchy changed by configuring a hierarchy exporter. If that’s the case it will throw StatusException with SyncCollections::HIERARCHY_CHANGED like it’s in the zimbra backend now. However in kopano we sometimes had/have not relevant hierarchy change notifications and adding the IBackend::HIERARCHYNOTIFICATION $notifications helped to solve those and spared some unnecessary requests.

Manfred

Hi wige,

yes, if you know a deviceid already, then you can filter connections. What I meant is that if you only know IMEI or MAC of the mobile, you won’t be able to determine deviceid.

You have to be aware though that Outlook over ActiveSync will generate a new deviceid every time you create a new profile, even if it’s the same user on the same computer.

Manfred

Hi liverpoolfcfan,

I updated to 2.4.0beta1 today and immediately started to experience issues. I quickly tracked them down to errors in the HTTPD error log file.

[Thu Jan 04 14:36:40.620521 2018] [:error] [pid 27643] [client 85.255.234.1:25065] PHP Fatal error: Declaration of BackendSearchZimbra::GetGALSearchResults() must be compatible with ISearchProvider::GetGALSearchResults($searchquery, $searchrange, $searchpicture) in /usr/share/z-push/backend/zimbra/zimbra.php on line 12846

If I am not in a position to pass back a picture at this time, can I assume that it is OK to just add a third parameter to the function definition in the zimbra backend and to set it with a default of “= false”?

Yes, adding a third parameter to the function definition will resolve it. You don’t have to do anything with $searchpicture in GetGALSearchResults.

Manfred

Hi,

I reinstalled Z-Push on Debian with:

apt-get install --reinstall z-push-autodiscover z-push-backend-kopano z-push-common z-push-config-apache z-push-ipc-sharedmemory z-push-kopano z-push-kopano-gabsync

But a newer version is a better solution.

Walter