@scottalanmiller said in Zimbra Services Fail to Start; Removing Stale PIDs:

@dbeato said in Zimbra Services Fail to Start; Removing Stale PIDs:

@dbeato said in Zimbra Services Fail to Start; Removing Stale PIDs:

@scottalanmiller said in Zimbra Services Fail to Start; Removing Stale PIDs:

@dbeato said in Zimbra Services Fail to Start; Removing Stale PIDs:

I have only had this happened on the upgrades between versions and OS upgrade.

This happened to us while simply up and running. Middle of the day. Very odd.

Weird

What version?

8.8.10_GA_3716

Hmmm I just upgraded from 8.8.9 to 8.8.11 last week or two weeks ago.

@dbeato said in Zimbra Update Fails with Validating LDAP Configuration, Cannot Create TLS Connection to LDAP Masters:

@scottalanmiller said in Zimbra Update Fails with Validating LDAP Configuration, Cannot Create TLS Connection to LDAP Masters:

So it worked by rebooting. WTF

Weird.

Very

@anthonyh said in Testing Zimbra Upgrade - 8.6.0 to 8.8.6:

I restored our production Zimbra server (CentOS 7) from backup to use as a testing environment for upgrading from Zimbra 8.6.0 to current (8.8.6 as of this writing).

Restore was fine. Gave the host an IP on a separate network. Followed a Zimbra wiki article on changing the server's hostname which worked no problem (from what I can tell). Fired up the services and Zimbra 8.6.0 came up hunky dory.

I do a yum update and install all pending updates (not many since I try to keep prod as current as possible), reboot the test server to verify Zimbra is still happy. Everything is good.

I download the 8.8.6 installer and current hotfix and stage them. I then snapshot the VM.

I run the 8.8.6 installer and it completes without complaint.

Where the problems begin. I cannot get to the Zimbra user interface. Management (7071) works fine. This points to a proxy issue.

I check and the proxy service is not running. I fire it up manually using zmproxyctl start and wait a minute. I eventually get the following error:

Starting proxy...nginx: [emerg] invalid URL prefix in /opt/zimbra/conf/nginx/includes/nginx.conf.zmlookup:3

I edit the file in question and, sure enough, the production IP is listed.

zm_lookup_handlers [PROD-IP]:7072/service/extension/nginx-lookup;

So I change it to the IP of the test VM (also tried 127.0.0.1 for the heck of it). However, this did not resolve the problem. Attempting to start the proxy service results in the same error.

So I test by telnetting to [TEST-IP]:7072 and it works. I try browsing to the path as shown in the config via a web browser and I get (from Chrome):

[TEST-IP] didn’t send any data. ERR_EMPTY_RESPONSE

Though I don't know if that indicates if there is an issue or not with whatever service is listening on 7072.

Any ideas?

@anthonyh said in Testing Zimbra Upgrade - 8.6.0 to 8.8.6:

In case anyone needs it, here is the solution. Looks like the instructions I followed to change the hostname did not include the proxy service. So to cover all bases, use the following commands after following the article here: https://wiki.zimbra.com/wiki/ZmSetServerName

zmprov ms `zmhostname` zimbraReverseProxyUpstreamLoginServers new.hostname.com zmprov ms `zmhostname` zimbraReverseProxyUpstreamEwsServers new.hostname.com zmprov mcf zimbraReverseProxyUpstreamLoginServers new.hostname.com zmprov mcf zimbraReverseProxyUpstreamEwsServers new.hostname.com /opt/zimbra/libexec/zmproxyconfgen zmproxyctl restart

To quote this further..

Edit file /opt/zimbra/conf/nginx/includes/nginx.conf.zmlookup

Modify URL to match the below (change hostname with yours):

zm_lookup_handlers https://mail.hostname.com:7072/service/extension/nginx-lookup;

Disable module chunkin because since 1.3.9 & above, Nginx core already has built-in support for the chunked request bodies, hence its no longer needed.

Verify Nginx version to see if it has been upgraded to 1.7.1

[zimbra@mail ~]$ nginx -v nginx version: nginx/1.7.1

Edit file /opt/zimbra/conf/nginx/includes/nginx.conf.web

Comment the following:

# chunkin on;

Edit file /opt/zimbra/conf/nginx/includes/nginx.conf.web.https.default

Comment these 4 lines & save the file:

# chunkin handler # location @chunkin_handler { # chunkin_resume; # }

Finally restart the proxy service:

zmproxyctl restart

Hope this helps 🙂

Kind regards,
Viraj

@dbeato said in Zimbra 8.8 in Beta:

@scottalanmiller said in Zimbra 8.8 in Beta:

@stuartjordan said in Zimbra 8.8 in Beta:

@scottalanmiller It is taking a while, when did you originally post this, about June time?

Yeah. I really want this update to come out!!

What will features will benefit the most for you?

It has the new interface. The old one is SO dated

I documented in another post so that we can find the actual answer files. I had to pull them out of the original script and check a bit to make sure that they do what we are looking for. Now to work on integrating them into Salt so that an install can be properly automated in that manner.

@black3dynamite said in Zimbra Community 8.0 Released (And Now Open Source):

@scottalanmiller said in Zimbra Community 8.0 Released (And Now Open Source):

Five years and we are still waiting on Zimbra 9 and/or the UI update 😞

What's up with the slow releases?

Not sure. They've done a lot of minor point releases since then, but no real features have updated and the UI is painfully old. They spent two years talking about, and then cancelling the bug UI update - really shot themselves in the foot there showing screenshots, overpromising, and then apparently just giving up. People really put a lot of hope in that and it just turned into vaporware.

Their acquisition by smaller and smaller companies has probably caused a lot of issues as they keep adjusting their focus and whatnot. But five years with no major updates has really showed that they just don't seem to be investing into it like they should. It was such an amazing market leader for so long. Now we worry if any major updates will ever come.