Zimbra Forums

I'm observing the same problem after upgrading from 8.7.4_GA_1730 to 8.7.7_GA_1787.

Thank you mefistoteles,

I confirm too, after executing the given commands sequence, I no longer see those errors in my /opt/zimbra/log/mysql_error.log.

After refreshing /opt/zimbra/jetty/zimbraAdmin , I can login to admin UI without a problem. Do you have to manipulate dst-nat every time? How do I "Refresh" jetty? I had installed new Zimbra on another VM, and then had copied /opt/zimbra/jetty/zimbraAdmin from newly installed Zimbra to a ...

Did you try to execute zmprov -l as per https://wiki.zimbra.com/wiki/Fix_zclien ... on_refused?

I would not install Zimbra on a server with an active web server. Please note, that Zimbra uses HTTP port 80 and HTTPS port 443.

In fact, I'd dedicate a virtual server just to Zimbra. It would simplify Zimbra upgrades, maintenance, etc...

Congrats:-) -- Thank you for sharing!

Anything eye-catching in /opt/zimbra/log/mailbox.log or in /opt/zimbra/log/zmmailboxd.out?

Hello, The ./install.sh script had referenced /sbin/ifconfig and netstat tools during upgrade. These tools are part of package net-tools , which was replaced in CentOS 7 with iproute2 instead. My upgrade went fine, i.e. no visible problems. Should I expect any problem? How essential these two tools ...

After refreshing /opt/zimbra/jetty/zimbraAdmin, I can login to admin UI without a problem.

Do you have to manipulate dst-nat every time?

DualBoot wrote:Maybe you could have put verbose mode on the mailboxd process.
You can check the options with this command :

Code: Select all

zmprov help log

Thank you!