Problems with serve...
 
Notifications
Clear all

Problems with server rename

1 Posts
1 Users
0 Reactions
1,567 Views
(@tgxperience)
Posts: 7
Topic starter
 

As the official Zimbra forum is dying I thought I would post here.
I have a server that I upgraded from 8.8.12 to latest 8.8.15. I brought Zextras from 2.6.1 to the latest.

The upgrade went fine without any errors but the proxyservice came up as 'stopped'.
After shutting down all services and trying to restart I received the message:

Starting proxy...nginx: [emerg] host not found /opt/zimbra/conf/nginx/includes/nginx.conf.web:27 failed

Looking in that file I saw a lot of references to a servername that is no longer in use. The server was renamed
quite some time ago.

I added the old servername back into /etc/hosts and the proxy service was then able to achieve a running state.

A little more digging revealed the following:

[zimbra@servername libexec]$ zmprov gacf | grep oldservername.domain.com
zimbraReverseProxyAvailableLookupTargets: oldservername.domain.com
zimbraReverseProxyUpstreamLoginServers: oldservername.domain.com
zimbraVersionCheckNotificationEmail: user@oldservername.domain.com
zimbraVersionCheckNotificationEmailFrom: user@oldservername.domain.com

[zimbra@servername libexec]$ zmprov gacf | grep servername.domain.com
zimbraAmavisQuarantineAccount: virus-quarantine@servername.domain.com
zimbraDefaultDomainName: servername.domain.com
zimbraLogHostname: servername.domain.com
zimbraSpamIsNotSpamAccount: ham@servername.domain.com
zimbraSpamIsSpamAccount: spam@servername.domain.com

[zimbra@servername libexec]$ zmprov gs 'servername.domain.com' | grep oldservername.domain.com
zimbraReverseProxyAvailableLookupTargets: oldservername.domain.com
zimbraReverseProxyUpstreamLoginServers: oldservername.domain.com

Note two affected services are ReverseProxy and VersionCheckEmail.
Is anyone here familiar with correcting such issues?

Thanks.

 
Posted : 07/13/2020 17:42