Zimbra 8.8.15 RC1 Released (IMHO)

Ask questions about your setup or get help installing ZCS server (ZD section below).
User avatar
L. Mark Stone
Elite member
Elite member
Posts: 1993
Joined: Wed Oct 09, 2013 11:35 am
Location: Portland, Maine
ZCS/ZD Version: 8.8.12 Network Edition
Contact:

Zimbra 8.8.15 RC1 Released (IMHO)

Postby L. Mark Stone » Mon Apr 01, 2019 9:56 pm

Zimbra released 8.8.12 today. The Release Notes are here: https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.12

IMHO, 8.8.12 is effectively 8.8.15 LTS Release Candidate 1. There are three very nice surprises with this release as well. Here's why:

First, conspicuously absent from the Release Notes, but right there on the Downloads page, are binaries for Ubuntu 18.04. NOTE: The Release Notes have been updated from yesterday to indicate that Ubuntu 18.04 binaries are BETA.

Second, the Product Lifecycle wiki shows that 8.8.15's General Support now ends on 31 December 2022. It used to end in March 2021, before Ubuntu 16.04 reached end of life in April 2021 (which is why I never expected to see Zimbra binaries for Ubuntu 18.04; there was no need...) Nice! More than a year of General Support added to a Zimbra Long-Term Release! Lifecycle wiki is here: https://www.zimbra.com/support/support- ... lifecycle/

Third, all features in 8.8.12, according to the Release Notes, are either now deemed Stable or Deprecated. And if you looked at the Lifecycle wiki, you'll note there is no 8.8.13 nor 8.8.14; the versioning goes straight from 8.8.12 Standard Release to 8.8.15 LTS.

So IMHO it looks like 8.8.12 is really 8.8.15 RC1. If Zimbra continues its monthly Patch Release cycle, we should see RC2 (8.8.12 Patch 1) on or about May 1, then RC3 (8.8.12 Patch 2) around June 1, followed by 8.8.15 LTS on July 1 -- hopefully with Stable binaries for Ubuntu 18.04.

Hope that helps,
Mark


___________________________________
L. Mark Stone
Mission Critical Email - Zimbra VAR/BSP/Training Partner https://www.missioncriticalemail.com/
Zeta Alliance http://www.zetalliance.org/
User avatar
DavidMerrill
Advanced member
Advanced member
Posts: 92
Joined: Thu Jul 30, 2015 2:44 pm
Location: Portland, ME
ZCS/ZD Version: 8.8.11 P3
Contact:

Re: Zimbra 8.8.15 RC1 Released (IMHO)

Postby DavidMerrill » Mon Apr 01, 2019 10:56 pm

Thanks for sharing this intel Mark, appreciate it!
___________________________________
David Merrill - Zimbra Practice Lead
OTELCO Zimbra Hosting, Licensing and Professional Services
Zeta Alliance
User avatar
maxxer
Advanced member
Advanced member
Posts: 136
Joined: Fri Oct 04, 2013 2:12 am
Contact:

Re: Zimbra 8.8.15 RC1 Released (IMHO)

Postby maxxer » Tue Apr 02, 2019 3:23 am

good catch! thanks Mark
User avatar
pup_seba
Outstanding Member
Outstanding Member
Posts: 684
Joined: Sat Sep 13, 2014 2:43 am
Location: Tarragona - Spain
Contact:

Re: Zimbra 8.8.15 RC1 Released (IMHO)

Postby pup_seba » Tue Apr 02, 2019 7:22 am

Hi,

As usual, thanks for sharing Mark! :)

Yersterday at 8pm CEST I started migrating an 8 server (3 store + 2 mta + 2 ldap mmr + 1 docs) from version 8.8.9p6 to this version. Just some notes I found during the migration.

- Documentation on this link, is still providing a wrong path for ldif files. https://zimbra.github.io/installguides/ ... grade.html
Proposed path in documentation is /opt/zimbra/openldap/etc/openldap/schema/zimbra.ldif, which does not exists. Instead, i used this /opt/zimbra/common/etc/openldap/zimbra/schema/zimbra.ldif

- Even when when zimbra talk was previously installed in server and migration method was an in-place update, instead of asking to "update" zimbra talk, it asks for "install zimbra talk".

- Done on a RHEL7.x, I got the warning about not having "libreoffice-headless".
Checking required packages for zimbra-store
FOUND: libreoffice-5.3.6.1-19
MISSING: libreoffice-headless

###WARNING###

yum install libreoffice-headless
Loaded plugins: product-id, search-disabled-repos, subscription-manager
zimbra | 2.9 kB 00:00:00
zimbra-8812-oss | 2.9 kB 00:00:00
Package 1:libreoffice-headless-4.3.7.2-5.el7_2.1.x86_64 is obsoleted by 1:libreoffice-core-5.3.6.1-19.el7.x86_64 which is already installed
Nothing to do

- After update was done on mailstores, even when services were up and running, in /opt/zimbra/log/mailbox.log I was able to see these errors. Really big stack, this is just a portion:
2019-04-02 00:09:24,104 INFO [main] [] misc - System property sun.os.patch.level=unknown
2019-04-02 00:09:24,138 INFO [main] [] system - Setting mysql connector property: maxActive=100
2019-04-02 00:09:24,138 INFO [main] [] system - Setting mysql connector property: maxActive=100
2019-04-02 00:09:24,224 FATAL [main] [] soap - Unable to start servlet
java.lang.NoClassDefFoundError: java/sql/Connection
at com.compuware.apm.agent.introspection.jdbc.ConnectionPoolIntrospection.updateConnectionClass(ConnectionPoolIntrospection.java:214)
at org.mariadb.jdbc.MySQLConnection.createStatement(MySQLConnection.java)
at org.mariadb.jdbc.MySQLConnection.newConnection(MySQLConnection.java:128)
at org.mariadb.jdbc.Driver.connect(Driver.java:113)
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:677)
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:189)
at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:78)
at com.zimbra.cs.db.ZimbraConnectionFactory.createConnection(ZimbraConnectionFactory.java:67)

Visible problem was not the log itself, but having a "blank page" in admiUI and having a "network encountered error" when trying to access webUI via proxies...in other woards, mail system down as per user perspective.

Thanks to zimbra support (lucky me Rick King managed the case, and I'm always feel lucky and happy when working with him), everything seemed to be alright, and just adjusting a dumb non-best practice I had in /etc/hosts, give the impression to fix the problem. Later on, after closing the ticket, the problem came up again. But it seems that restarting the whole server, not only the zimbra services, made it dissapear...we'll see. I'll upload logs to zimbra support just in case they actually find something not going well.

- I was not able to find any documentation about how to upgrade zimbra docs. I understand that this should be easy and I feel is almost intuitive, but I would like to see some docs about it instead of again, having to write a piece of doc by try and error in my lab.

- Latetly, a new "localhost" is showing under supervision in adminUI. I'll fix that today tho...easy thing to fix, although I don't understand why is there.

I'll update this in case new info shows up. Today and tomorrow I'll have to update to this release from two other different versions, alghough these are smaller deployments and I hope they go smoother. Like this weekend, that I updated to 8.8.11p3 from 8.6 versions...everything went a lot smoother than this one.
User avatar
L. Mark Stone
Elite member
Elite member
Posts: 1993
Joined: Wed Oct 09, 2013 11:35 am
Location: Portland, Maine
ZCS/ZD Version: 8.8.12 Network Edition
Contact:

Re: Zimbra 8.8.15 RC1 Released (IMHO)

Postby L. Mark Stone » Tue Apr 02, 2019 12:02 pm

Sebastian,

Thanks for posting your upgrade experience.

On the documentation discrepancies, I would ask Rick (his nickname is "The King" because, well... he is!) if he needs you to make a separate support ticket to get those addressed.

Regarding the libreoffice-headless "missing" package in RHEL/CentOS7, this is a known bug in the installer. So long as you install the libreoffice meta-package, high-fidelity document preview (a Network Edition-only feature) will work OK as reported by others -- even though the installer complains.

Zimbra is very sensitive to having accurate and comprehensive /etc/hosts and DNS resolution, and I have seen issues with Zimbra services not starting in a multi-server environment when /etc/hosts was not correct. This is possibly also what is causing the spurious "localhost" entry in the Admin Console monitoring section. That will disappear after a few days of log rotation if /etc/hosts is corrected everywhere. As I know you know, the green check marks and red X's in the Admin Console are very dependent on syslogging being configured correctly, which in turn requires correct/comprehensive /etc/hosts and accurate DNS. That's a long way of saying I have seen many systems that had stale green check marks in the Admin Console, but some Zimbra services (like stats or zmconfigd) were not running. I've also seen where syslogging was not working so lots of red X's but Zimbra itself was actually running just fine.

As re Zimbra Docs in-place upgrade, I wonder now if this is even possible. The new 8.8.12 version of Zimbra Docs is built on Collabora, whereas previous versions used a custom build of LibreOffice. It may be you will need to deploy new Docs servers and remove the existing ones. That's a good question for Rick (or a separate Support ticket) so we can all get clarification - and get the documentation updated accordingly. I don't know if 8.8.12 will work with 8.8.11 and earlier Docs servers or not.

Please keep us posted!

All the best,
Mark
___________________________________
L. Mark Stone
Mission Critical Email - Zimbra VAR/BSP/Training Partner https://www.missioncriticalemail.com/
Zeta Alliance http://www.zetalliance.org/
User avatar
pup_seba
Outstanding Member
Outstanding Member
Posts: 684
Joined: Sat Sep 13, 2014 2:43 am
Location: Tarragona - Spain
Contact:

Re: Zimbra 8.8.15 RC1 Released (IMHO)

Postby pup_seba » Wed Apr 03, 2019 9:48 am

Hi,

New things after upgrades. Things written in "italic" are added. Somethings other things are removed, like the /etc/hosts as problem persists even when that file adjustedNot all of these happen in the same platform, these are things happening on different customers.

- Documentation on this link, is still providing a wrong path for ldif files. https://zimbra.github.io/installguides/ ... grade.html
Proposed path in documentation is /opt/zimbra/openldap/etc/openldap/schema/zimbra.ldif, which does not exists. Instead, i used this /opt/zimbra/common/etc/openldap/zimbra/schema/zimbra.ldif

Before updating, I asked zimbra support about it and the answer is "yes, that ldap part still applies". Yet, Now I have another answer from another zimbra technician were he says "nope, that part does not apply to new installations and I'll open an RFE to be removed".

- Even when when zimbra talk was previously installed in server and migration method was an in-place update, instead of asking to "update" zimbra talk, it asks for "install zimbra talk".

- Done on a RHEL7.x, I got the warning about not having "libreoffice-headless".
Checking required packages for zimbra-store
FOUND: libreoffice-5.3.6.1-19
MISSING: libreoffice-headless

###WARNING###

yum install libreoffice-headless
Loaded plugins: product-id, search-disabled-repos, subscription-manager
zimbra | 2.9 kB 00:00:00
zimbra-8812-oss | 2.9 kB 00:00:00
Package 1:libreoffice-headless-4.3.7.2-5.el7_2.1.x86_64 is obsoleted by 1:libreoffice-core-5.3.6.1-19.el7.x86_64 which is already installed
Nothing to do

- After update was done on mailstores, even when services were up and running, in /opt/zimbra/log/mailbox.log I was able to see these errors. Really big stack, this is just a portion:
2019-04-02 00:09:24,104 INFO [main] [] misc - System property sun.os.patch.level=unknown
2019-04-02 00:09:24,138 INFO [main] [] system - Setting mysql connector property: maxActive=100
2019-04-02 00:09:24,138 INFO [main] [] system - Setting mysql connector property: maxActive=100
2019-04-02 00:09:24,224 FATAL [main] [] soap - Unable to start servlet
java.lang.NoClassDefFoundError: java/sql/Connection
at com.compuware.apm.agent.introspection.jdbc.ConnectionPoolIntrospection.updateConnectionClass(ConnectionPoolIntrospection.java:214)
at org.mariadb.jdbc.MySQLConnection.createStatement(MySQLConnection.java)
at org.mariadb.jdbc.MySQLConnection.newConnection(MySQLConnection.java:128)
at org.mariadb.jdbc.Driver.connect(Driver.java:113)
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:677)
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:189)
at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:78)
at com.zimbra.cs.db.ZimbraConnectionFactory.createConnection(ZimbraConnectionFactory.java:67)

Visible problem was not the log itself, but having a "blank page" in admiUI and having a "network encountered error" when trying to access webUI via proxies...in other woards, mail system down as per user perspective.

A support ticket is opened (actually 2 support tickets are opened) about this issue. We are nos suspecting that the database takes too long to start and that's may be the reason why the servlet fails to start when connecting to the database. I'll keep you posted

- I was not able to find any documentation about how to upgrade zimbra docs. I understand that this should be easy and I feel is almost intuitive, but I would like to see some docs about it instead of again, having to write a piece of doc by try and error in my lab.

You are completly right Mark! I completle ignored that Collabora thing :) Again, I opened a support ticket for the info on how to upgrade/replace this should be done. I'll keep you posted

- Latetly, a new "localhost" is showing under supervision in adminUI. I'll fix that today tho...easy thing to fix, although I don't understand why is there.

I did not know it could dissapear by itself when the conditions you mention are met! In any case, following this wiki fixed the problem right away https://wiki.zimbra.com/wiki/Server_sta ... rossed_out

- IMAP clients can't show/sync non-english characters like "ñ" or "á"
We are able to see them in the webUI, but nor Outlooks, thunderbirds or others (like the mac client) can properly see or even create such folders anymore. All of these custemers sync via IMAP...which I suspect has something to do with this "imap deserialze" bug being fix". I'll open a support ticket (once the others are solved) to ask about this


- zextras was not enabled even when it was enabled during install
In this case, if we "zmprov gacf zimbraNetworkModulesNGEnabled", the value was set to TRUE, yet, at a server level (zmprov gs), the value was set to "FALSE". The sympthom was the lack of the zimlet in the adminUI, and an error saying no server available when doing a "zxsuite core getservices". The fix was to simply modify the value to TRUE at a server level and restart.


- Legacy backups schedule is restored to default, regardless it was dissabled before it. I remember some old posts talking about this (Mark posts more precisly), I guess it is still not fixed.

Today I have to do another update, and then another one on monday...let's see what other surprises come up :)
User avatar
comradeTJH
Posts: 16
Joined: Tue Jul 04, 2017 12:39 pm

Re: Zimbra 8.8.15 RC1 Released (IMHO)

Postby comradeTJH » Thu Apr 04, 2019 8:36 am

Did you already open a ticket for the IMAP non english character folder name problem?
This is kind of a huge deal here. Nearly all our accounts have folders with Umlauts (ä,ö and ü) in them and Outlook doesn't see them anymore. Furthermore, if users delete mails, Outlook moves them into the "Gelöschte Elemente" folder, which isn't there anymore and thus creates a new new one that's now shown on the web-client as "Gel-&APY-schte Elemente". This starts to get very messy :-/

Is there any way to roll back 8.8.12 to 8.8.11 in the meantime?

Thanks a lot!
User avatar
pup_seba
Outstanding Member
Outstanding Member
Posts: 684
Joined: Sat Sep 13, 2014 2:43 am
Location: Tarragona - Spain
Contact:

Re: Zimbra 8.8.15 RC1 Released (IMHO)

Postby pup_seba » Thu Apr 04, 2019 10:05 am

Hi mate!

Nope, not yet I didn't. But I will open it now, as I think we have fixed the servlet problem I described before. I'll keep this updated so if any one else updating find some more problems, maybe they can find the solution in here. I may be hijacking this post and what's the original purpose of it? if so, sorry, just tell me and I'll just create a new one! :)
User avatar
L. Mark Stone
Elite member
Elite member
Posts: 1993
Joined: Wed Oct 09, 2013 11:35 am
Location: Portland, Maine
ZCS/ZD Version: 8.8.12 Network Edition
Contact:

Re: Zimbra 8.8.15 RC1 Released (IMHO)

Postby L. Mark Stone » Thu Apr 04, 2019 10:16 am

Sebastian,

You are NOT hijacking the post at all.

It’s good to have one or more threads for new releases where early adopters can post there successes and challenges, so that others can adopt their workarounds or upgrade with better confidence.

Thanks for the detailed posts!

Mark
___________________________________
L. Mark Stone
Mission Critical Email - Zimbra VAR/BSP/Training Partner https://www.missioncriticalemail.com/
Zeta Alliance http://www.zetalliance.org/
User avatar
pup_seba
Outstanding Member
Outstanding Member
Posts: 684
Joined: Sat Sep 13, 2014 2:43 am
Location: Tarragona - Spain
Contact:

Re: Zimbra 8.8.15 RC1 Released (IMHO)

Postby pup_seba » Thu Apr 04, 2019 7:33 pm

Hi,

A little update on issues I faced in several upgrades to 8.8.12 in some different installations. It's been a looong week, somedays working from 7:30am until 4:00am. So here it goes, I hope it helps someone...next week I must face new migrations so who knows, maybe we can make this list a little bit longer I'm afraid:

- Issue 1
Documentation on this link, is still providing a wrong path for ldif files. https://zimbra.github.io/installguides/ ... grade.html
--> As it turned out, this step as most of that guide is completly outdated and absolutly not necessary. Sadly, even some of the zimbra support staff did not know this. Lucky me, Teodor was there to save the day and clarify things. So, here are other things for which I have confirmation that are not necessary in that guide:
- Upgrading LDAP Replica Servers or Multi-Master Server.
- Disable SSLv3 Support.
- After all MTA nodes are upgraded to Zimbra Collaboration 8.8.12, the following commands may be run to fix the default globalconfig values, if necessary.
- You should run zmldapupgrade -b 66387 after upgrading.

- Issue 2
Even when when zimbra talk was previously installed in server and migration method was an in-place update, instead of asking to "update" zimbra talk, it asks for "install zimbra talk".
--> This is "normal" behaviour. As per Zimbra support "zimlets are reinstalled, together with the talk zimlet. The installer reinstalls them." Yet...zimbra is the only one zimlet asking to "be installed". No prob...say "Y" and keep moving with the install wizard :)

- Issue 3
Done on a RHEL7.x, I got the warning about not having "libreoffice-headless".
Checking required packages for zimbra-store
FOUND: libreoffice-5.3.6.1-19
MISSING: libreoffice-headless

###WARNING###

yum install libreoffice-headless
Loaded plugins: product-id, search-disabled-repos, subscription-manager
zimbra | 2.9 kB 00:00:00
zimbra-8812-oss | 2.9 kB 00:00:00
Package 1:libreoffice-headless-4.3.7.2-5.el7_2.1.x86_64 is obsoleted by 1:libreoffice-core-5.3.6.1-19.el7.x86_64 which is already installed
Nothing to do

--> According to the technician from Zimbra support, he thinks it may be only a problelm with the installer not realizing the package is already installed in a newer version. He is trying to confirm this information internally.

- Issue 4
After update was done on mailstores, even when services were up and running, in /opt/zimbra/log/mailbox.log I was able to see these errors. Really big stack, this is just a portion:
2019-04-02 00:09:24,104 INFO [main] [] misc - System property sun.os.patch.level=unknown
2019-04-02 00:09:24,138 INFO [main] [] system - Setting mysql connector property: maxActive=100
2019-04-02 00:09:24,138 INFO [main] [] system - Setting mysql connector property: maxActive=100
2019-04-02 00:09:24,224 FATAL [main] [] soap - Unable to start servlet
java.lang.NoClassDefFoundError: java/sql/Connection
at com.compuware.apm.agent.introspection.jdbc.ConnectionPoolIntrospection.updateConnectionClass(ConnectionPoolIntrospection.java:214)
at org.mariadb.jdbc.MySQLConnection.createStatement(MySQLConnection.java)
at org.mariadb.jdbc.MySQLConnection.newConnection(MySQLConnection.java:128)
at org.mariadb.jdbc.Driver.connect(Driver.java:113)
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:677)
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:189)
at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:78)
at com.zimbra.cs.db.ZimbraConnectionFactory.createConnection(ZimbraConnectionFactory.java:67)

Visible problem was not the log itself, but having a "blank page" in admiUI and having a "network encountered error" when trying to access webUI via proxies...in other woards, mail system down as per user perspective.

A support ticket is opened (actually 2 support tickets are opened) about this issue. We are nos suspecting that the database takes too long to start and that's may be the reason why the servlet fails to start when connecting to the database. I'll keep you posted

--> This was caused by something very specific to one of my customers. The problem in this case was with "dynatrace" agent, which was slowing down the db start, thus 'causing the servlet to fail the connection to it during strat time. So even when all services were showing as running, functionality was broken. Once disabled this agent from dynatrace, problem was solved.

- Issue 5
I was not able to find any documentation about how to upgrade zimbra docs. I understand that this should be easy and I feel is almost intuitive, but I would like to see some docs about it instead of again, having to write a piece of doc by try and error in my lab.
--> You can' find documentation if there is no documentation (insert roll safe think about it meme here). So there, there is no documentation on how the upgrade process should be. Mark guessing is absolutly right and as per Zimbra support, we should: 1. Install the new zDocs server in a new machine. 2. Remove the previous version (zdocs remove-local-server). The instructions for point 1. are as follow:
Prerequisites for zimbra Docs

In case of multi-server, all server should be resolvable with each other.
Mailbox servers should be reachable to the Docs server & vice versa.
Proxy servers should be reachable to the Docs server & vice versa.
Check host files of each server.
The zimbraPublicServiceHostname, zimbraPublicServiceProtocol, zimbraPublicServicePort should be configured on a domain so that it can proxy all request to the corresponding mailbox server.
All mailbox servers will need to be able to directly communicate with the Docs Server over port 8443 (HTTPS Backend), which must be open on both ends.
The Supported OS (Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, Red Hat Enterprise Linux 7, CentOS 7) for the Docs server as of now.

Installation steps for the Docs server

At this stage, we assume that all above prerequisites are done.

Login into the Docs server.
Download the zimbra-docs-OSv.tgz standalone installer, extract it and as the root user execute the install.sh script contained in the package.
https://www.zimbra.com/downloads/zimbra-collaboration/

We need to provide the ldap url, zimbra DN and zimbra ldap password.
e.g:
LDAP url (ldap://proxy.abc.com:389): ldap://proxy.abc.com:389
LDAP dn (uid=zimbra,cn=admins,cn=zimbra): uid=zimbra,cn=admins,cn=zimbra
LDAP password (fadpXcun5): fadpXcun5
Trying to connect to LDAP...OK
Configuration written
................++\+
..............................................................................................++\+
Generated key in /opt/zimbra/conf/docs/key.pem
Updating server 590fae5c-2cf3-4e1f-8537-df7989216945 with hostname 'docs.abc.com' in LDAP
Changes applied
No changed in the configuration
systemctl restart zimbra-docs-server
Setup successfully completed.

If we get the above message, then docs is installed successfully.

To check if the installation was successful,

We'll verify the ldap connectivity from the docs server
[]# zdocs ldap-test
Trying to connect to LDAP...OK

To restart a docs server if needed:
zdocs zdocs restart

Regenerate the config and restart the server if config changed.
zdocs --auto-restart generate-config

Then we continue the installation

Run the following on all proxy servers

We need to re-generate to proxy server configuration - just restart the services.
su - zimbra
zmproxyctl restart

To verify: Run the following command:
grep -i server /opt/zimbra/conf/nginx/includes/nginx.conf.docs.upstream

The expected output is:
[]$ grep -i server /opt/zimbra/conf/nginx/includes/nginx.conf.docs.upstream
server docs.abc.com:9980;

Run the following on the all mailbox servers
Now the com_zextras_docs Zimlet needs to be deployed on the server and enable on all users and COS that need to have access to the Zimbra Docs features.

RHEL/CentOS
yum install zimbra-docs

Ubuntu
apt-get install zimbra-docs
su - zimbra
zmmailboxdctl restart

Troubleshooting

Check the zimlet (com_zextras_docs) is installed and enabled on all mailbox nodes.
Check the docs server status from Docs server and from mailbox server as well.
zdocs status # From Docs Server
zxsuite docs status # From mailbox nodes

Check the network connection between the servers.
You can check the error by browser debugging (?dev=1)
We see below logs which indicate that docs server is working fine.



- Issue 6
Latetly, a new "localhost" is showing under supervision in adminUI. I'll fix that today tho...easy thing to fix, although I don't understand why is there.

I did not know it could dissapear by itself when the conditions you mention are met! In any case, following this wiki fixed the problem right away https://wiki.zimbra.com/wiki/Server_sta ... rossed_out

- Issue 7
IMAP clients can't show/sync non-english characters like "ñ" or "á"
We are able to see them in the webUI, but nor Outlooks, thunderbirds or others (like the mac client) can properly see or even create such folders anymore. All of these custemers sync via IMAP...which I suspect has something to do with this "imap deserialze" bug being fix". I'll open a support ticket (once the others are solved) to ask about this
--> Bug. This is Zimbra support response...no comments from my side on their answer (of course there is no way for us to follow the bug state as bug tracking tool is now private):
Thank you for contacting Zimbra Support.
After a close investigation, we have identified that your case has resulted into a bug and we have reported the bug to Development using our new bug process.
For more information about this process, please see the [ https://blog.zimbra.com/2018/05/zimbras ... g-process/ | Zimbra New Bug Fix / Reporting Process ] wiki. We will be keeping this case open and the support team will be sending you updates on the status of the bug.
If you have any questions, please let us know by replying to the case and support will followup with you.
We appreciate your commitment to Zimbra.

- Issue 8
- zextras was not enabled even when it was enabled during install
In this case, if we "zmprov gacf zimbraNetworkModulesNGEnabled", the value was set to TRUE, yet, at a server level (zmprov gs), the value was set to "FALSE". The sympthom was the lack of the zimlet in the adminUI, and an error saying no server available when doing a "zxsuite core getservices".
--> The fix was to simply modify the value to TRUE at a server level and restart.

- Issue 9
- Legacy backups schedule is restored to default, regardless it was dissabled before it.
--> This is a long time error, that I must assume that provoked more than one problem to unaware admins. viewtopic.php?t=65096
Fix is "easy", basically you need to fulsh the leagacy backups (zmschedulebackup -F) and also set the deleteonrollover for redologs to "TRUE" as there is not going to be more legacy backups to remove them for you. ("zmprov mcf zimbraRedoLogDeleteOnRollover TRUE" for the global config and then double check it at a server level or just do it one server by one with "zmprov ms `zmhostname` zimbraRedoLogDeleteOnRollover TRUE")

- Issue 10
- Zextras (backup_ng) backups fail when trying to backup ldap files.
--> I remember phoenix recenlty explaining someone in this forum how to fix it but sorry, I can't find the post and I'll go nuts if I keep waiting for this forum pages to load. So basicall, permissions on those files need to be fixed. This is done by executing this as root user:
chmod 0644 /opt/zimbra/common/etc/openldap/slpad.*

- Issue 11
- The stats service was not able to start.
--> Fixed by removing the .pid file which had wrong permissions/owner. In this particular case was what I did was to move away this file "/opt/zimbra/zmstat/pid/zmstat-fd-real.pid" and restart the service via "zmstatsctl restart"

- Issue 12
- Some specific android devices, see the mails with date of 1/1/1970. I did not see this one by myself, but I know my customer opened a support ticket about it. I'll try to find out the details about which exact android model is having the problem also.

Return to “Installation and Upgrade”

Who is online

Users browsing this forum: No registered users and 5 guests