We have a workaround for this, please enable zimbraCsrfTokenCheckEnabled by running below commands and restart mailbox service:
Code: Select all
su - zimbra
zmprov mcf zimbraCsrfTokenCheckEnabled TRUE
zmmailboxdctl restart
Code: Select all
su - zimbra
zmprov mcf zimbraCsrfTokenCheckEnabled TRUE
zmmailboxdctl restart
Code: Select all
2019-11-20 13:30:13,655 WARN [qtp1708169732-28478:https://xxxxxx/zimbra/m/zmain] [] webclient - system failure: Connection pool shut down
We and one of our customers had this issue. In our cases, the symptoms were that web client sessions generated a "Server Error 500" for the users, but that IMAP and other non web-ui access methods continued to function.benoit.georgelin wrote:Hello,
In our situation, this fix does not help at all.
We are still having a lot of :
After restarting Zimbra it does not even last 24hCode: Select all
2019-11-20 13:30:13,655 WARN [qtp1708169732-28478:https://xxxxxx/zimbra/m/zmain] [] webclient - system failure: Connection pool shut down
Is there any way to investigate this more ?
We are in multi-mode server with store-ui and proxy, maybe that's the difference ?
Thanks for your help,
Regards
Code: Select all
zmprov mds user@yourdomain.com "Gmail" zimbraDataSourcePollingInterval 4h
Code: Select all
zmprov mds user@yourdomain.com | grep " name "
You can indeed set the minimum polling interval via COS; I have not tested however how inheritance works for this variable. IOW, if a user has an external data source already configured, the minimum polling interval may already be set for that data source.benoit.georgelin wrote:Hi Mark.
I do appreciate a lot your answer.
It's exactly the issue that we are facing..
We run a lof of mailboxes and a lot of users uses external accounts I guess.
We will have to figure how to change the polling for all those external accounts. I think we can user the classes service to set the time globaly , is that right ?
Thanks