I filed and obtained approval for an RFE for this feature: ZRFE-258. You are welcome to open a Support Case if you have a licensed version of Zimbra to add your voice to this request. Filed now (even tough I cannot see the open case :? ) I wonder if in the meantime it would be possible to add the w...

phoenix wrote:Well done, I'm glad you've fixed it.

Tanks to Zextras team. Yesterday my mind was fried up, I wasn't able to think. Messages that those files were picked by Jetty were present in mailbox.log, I just couldn't see them.

Anyway, I'm happy too

My bad!

Instead of moving zal.jar files outside I just renamed them in the same directory. So Jetty was picking them up anyway throwing the exception. After moving those file away everything is back to normal.

At least that's one step forward. You output seems to show a different patch level to mine, iIs there any reason you're not on the current ZCS patch level (Patch 8.8.15_P13)? I was on the latest packages but I wasn't able to have Zimbra accept zal.jar. So at least now Zimbra is back to work. Now I ...

Does this post help? https://forums.zimbra.org/viewtopic.php?t=67491&start=10 Indeed downgrading at least restored Zimbra functionalities yum downgrade zimbra-openjdk-11.0.2-1zimbra8.8b1.el7 zimbra-core-components-2.0.0-1zimbra8.8b1.el7 zimbra-patch-8.8.15.1576149483.p5-1.r7 zimbra-proxy-patch-...

phoenix wrote:Sorry, I guess that might be one of the 'old threads' you've tried? I'd guess this might be better asked on the Zextras forums.

I haven't tried Java downgrade yet, but all the other zal.jar options.

I filed a support ticket to Zextras, just tried different support channels

Hi. I've upgraded an old 8.6.0 CentOS7 to 8.8.15. It had ownCloud and Zextras installed, so after upgrade mailboxd is not starting with the exception above. I tried everything suggested in the old threads: * moved away zal.jar * for ownCloud downloaded zal.jar from github * extracted zal.jar from zi...

davidkillingsworth wrote:Removing and re-adding the shared mailboxes was the fix for those incidents as well.

Thanks for the suggestion, I'll take note.

Among all the tests we did for the issue we probably did the same, since now the mailbox works normally.

I'm getting the error above when doing incremental backups using zmbkpose. Full backup works, as it doesn't have a search query, incrementals are performed with a curl like this: curl -s -S -k -u admin@domain.it:password https://posta.domain.it:7071/home/admin@domain.it/?fmt=tgz\&query=after:-6m...

DanielEugenin wrote:I think this is solved cleaning /opt/zimbra/jetty/work directory.

viewtopic.php?t=67434

I confirm this works, thanks