Z-Push Zimbra Backend (Push Email, Contacts, Appointments & Tasks)

[gunvier]

Hello:
I'm in a similar situation than sangamc.
I'm running zimbra 8 and z-push 2 with zimbrabackend release 54.
yesterday I was so happy because I get all contacts and calendar synced, that still working.

but today, I found that mail is not working fine... it's strange, because the only folder that i can't se populated is the inbox. if I go to any other folder (even sent items who has more than 6000 mails on it) I can click on "update" and I get my e-mails from there. on Imbox, it stills empty (even, I can't see the sub-folders of inbox)

on z-push.log I found this every time I try to sync:

16/11/2012 13:34:39 [32218] [INFO] [gunther] Version='2.0.5-1541' method='POST' from='190.100.22.35' cmd='Sync' getUser='gunther' devId='SAMSUNG1359548049068153' devType='SAMSUNGGTN'
16/11/2012 13:34:39 [32218] [WARN] [gunther] /var/www/z-push/lib/core/zpush.php:445 Use of undefined constant ZIMBRA_USER_DIR - assumed 'ZIMBRA_USER_DIR' (8)
16/11/2012 13:34:39 [32218] [ERROR] [gunther] LoopDetection->ProcessLoopDetectionPreviousConnectionFailed(): Command 'Sync' at 16/11/2012 13:29:24 with pid '32218' terminated unexpectedly or is still running.
16/11/2012 13:34:39 [32218] [ERROR] [gunther] Please check your logs for this PID and errors like PHP-Fatals or Apache segmentation faults and report your results to the Z-Push dev team.
16/11/2012 13:34:39 [32218] [INFO] [gunther] SyncCollections->CheckForChanges(): Waiting for store changes... (lifetime 470 seconds)
16/11/2012 13:34:39 [32218] [INFO] [gunther] ExportChangesDiff->InitializeExporter(): Found '0' changes
16/11/2012 13:34:39 [32218] [INFO] [gunther] ExportChangesDiff->InitializeExporter(): Found '0' changes
16/11/2012 13:34:39 [32218] [INFO] [gunther] ExportChangesDiff->InitializeExporter(): Found '0' changes

Apache has permissions to write on state folder, as it creates subfolders and files when I configure the account on my phone.

Any ideas what can I do to get it work?

Thanks!

[sangamc]

Hi Gunvier,

Are you able to find the logs that have the following error.

Please check your logs for this PID and errors like PHP-Fatals or Apache segmentation faults

I think there is more on the error by following this directive, but my apache logs dont have anything relevant, and even though i have enabled PHP logging in php.ini I am having no luck finding more info.

Thanks

[gunvier]

Hi Sangamc.

nothing found on apach2 logs.

it's crazy, because I moved all sub-folders from inbox to another folder, and I can browse them on the phone like a charm.
it just don't want to do anything with the inbox.

I have into there around 20.000 e-mails... don't know if that is a problem.
i'm going to try moving old ones to another folder....

[gunvier]

So... I moved around 14000 e-mails from inbox to a "old-" folder...
now inbox gets populted and everything works fine

maybe I have to clean a bit from time to time...
but ¿why is that? if the phone is just getting the last 100 messages?

[liverpoolfcfan]

I was just going to ask you guys how large your Inbox is. I have seen some problems with large in boxes.

Try limiting the sync from the config.php file. The default setting is SYNC_FILTERTYPE_ALL - try setting it down to 2 weeks as below.

// SYNC_FILTERTYPE_ALL (default, no limitation)
// SYNC_FILTERTYPE_1DAY, SYNC_FILTERTYPE_3DAYS, SYNC_FILTERTYPE_1WEEK, SYNC_FILTERTYPE_2WEEKS,
// SYNC_FILTERTYPE_1MONTH, SYNC_FILTERTYPE_3MONTHS, SYNC_FILTERTYPE_6MONTHS
define('SYNC_FILTERTIME_MAX', SYNC_FILTERTYPE_2WEEKS);

The search function should still allow you to search back further if needed.

[liverpoolfcfan]

So... I moved around 14000 e-mails from inbox to a "old-" folder...
now inbox gets populted and everything works fine

maybe I have to clean a bit from time to time...
but ¿why is that? if the phone is just getting the last 100 messages?

There is a change in z-push-2 that for some reason counts how many emails are in the Inbox before it has been told by the device what FILTERTYPE setting to use (which comes on the first sync request) - Without a provided filter type Z-push will use the configured default - which is ALL.

This results in the item count taking so long (500 items at a time processed) that the response is not provided back to z-push in a timely manner. The LoopDetection appears to decide the previous command died or hung, so it kicks off another.

I have asked the developers why this was changed and have not gotten any good answer as yet.

The way I have dealt with it is the method I posted above - to set the SYNC_FILTERTYPE_MAX to 2 weeks.

[sangamc]

My inbox is on a test account. less than 20 messsages with a mix of html and non html. A few calendar entries for the month of Nov and less than 10 entries in the contacts list.

In @Gunvier situation, do you by any chance have another folder named 'Inbox' I've had a similar situation when On an old z-push server

[gunvier]

My inbox is on a test account. less than 20 messsages with a mix of html and non html. A few calendar entries for the month of Nov and less than 10 entries in the contacts list.

In @Gunvier situation, do you by any chance have another folder named 'Inbox' I've had a similar situation when On an old z-push server

Hello.
no, I don't have another folder called "inbox" on my account... I have tested all day, everything is working fine for me.

[fviero]

Hi all

After another successfull Zimbra Z-push deployment, the only thing that remains is this:

InterProcessData::InitSharedMem(): PHP libraries for the use shared memory are not available. Functionalities like z-push-top or loop detection are not available. Check your php packages.

I´m using z-push 2 with backend release 54 on a RHEL 6.3, Zimbra 6.0.6

Everyhting appears to be working fine (well, still under test, but it´s indeed working), except i have that error in my logs.

Something to worry about? Easy to fix?

Thanks!!

[lytledd]

InterProcessData::InitSharedMem(): PHP libraries for the use shared memory are not available. Functionalities like z-push-top or loop detection are not available. Check your php packages.

I ran into this yesterday on a new install under CentOs, the fix was:

yum install php-process

Doug