andrey.ivanov wrote:The exception is in the com.zimbra.common.httpclient.HttpClientUtil class. It could be a new Zimbra bug related to the major change of version of HttpCLient ("Upgraded 3rd Party HttpClient to version 4.5.5." from https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.15).
There is already a known issue with the same reason, with a workaround "WebMail Login Failure - when zimbraCsrfTokenCheckEnabled is set to FALSE Apache HttpClient Connection pool shuts down and login to webmail fails.". So maybe it's a second side effect of HttpClient upgrade in 8.8.15...
Interesting ...
zimbraCsrfTokenCheckEnabled is set to TRUE though
andrey.ivanov wrote:The exception is in the com.zimbra.common.httpclient.HttpClientUtil class. It could be a new Zimbra bug related to the major change of version of HttpCLient ("Upgraded 3rd Party HttpClient to version 4.5.5." from https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.15).
There is already a known issue with the same reason, with a workaround "WebMail Login Failure - when zimbraCsrfTokenCheckEnabled is set to FALSE Apache HttpClient Connection pool shuts down and login to webmail fails.". So maybe it's a second side effect of HttpClient upgrade in 8.8.15...
Interesting ...
zimbraCsrfTokenCheckEnabled is set to TRUE though
How can we send that to developers to analyze. do i need zimbra network edition for that?
Yes, you need a supported Network Edition. I do have support but unfortunately i still have not tested 8.8.15 to reproduce your problem and make a ticket. As Mark says, maybe the 8.8.15_P1 will fix this problem.
On CentOS 7.6, 8.8.15p1 is not solving the problem with either FOSS or NE editions. I could not see either this problem described in the "known issues".
same issue here - Zimbra 8.8.15 NE and FOSS too. I opened a support ticket on 23. august. Zimbra support was able to reproduce it on their test servers and allegedly the update to 8.8.15_P1 solved the problem on their side. But not in my case. Tried updating both the NE and FOSS and I'm still experiencing the issue.
Maybe the next patch will cover this, but it would be nice to see some workaround before..
Exception in thread "main" java.lang.NullPointerException
at com.zimbra.common.httpclient.HttpClientUtil.executeMethod(HttpClientUtil.java:53)
at com.zimbra.common.httpclient.HttpClientUtil.executeMethod(HttpClientUtil.java:49)
at com.zimbra.cs.util.SpamExtract.extractMessages(SpamExtract.java:367)
at com.zimbra.cs.util.SpamExtract.extract(SpamExtract.java:291)
at com.zimbra.cs.util.SpamExtract.main(SpamExtract.java:220)
Exception in thread "main" java.lang.NullPointerException
at com.zimbra.common.httpclient.HttpClientUtil.executeMethod(HttpClientUtil.java:53)
at com.zimbra.common.httpclient.HttpClientUtil.executeMethod(HttpClientUtil.java:49)
at com.zimbra.cs.util.SpamExtract.extractMessages(SpamExtract.java:367)
at com.zimbra.cs.util.SpamExtract.extract(SpamExtract.java:291)
at com.zimbra.cs.util.SpamExtract.main(SpamExtract.java:220)
I just updated Zimbra to the latest version 8.8.15 P1 and I have the same error, they haven't updated it.
Same here too. I just decided to re-install rather than upgrade so it's a clean install - ZCS 8.8.15 open source (patch 1, provided that "apt upgrade" is all you have to do nowadays to patch) on Ubuntu 18.04.3 server.
It looks as if "spamtrain.log" contains nothing but these errors, and the Bayes filter has not started, so I suspect no training at all is happening.