You have a server in the lookup pool list that shouldn't be there or you should remove the trouble server from the pool to avoid any more customer issues to deescalate the situation.The server/s are too busy to serve the request.Following step one, you also have to confirm there is port level access between proxy servers and the server it's trying to reach.This oversight might when you've deployed a new ZCS server in your environment. If the resolution to the host from the proxy servers is correct and working.If your getting "No route to host" errors in /opt/zimbra/log/nginx.log files on the proxy servers, you should check: Zmprov gcf zimbraReverseProxyLookupTarget Zmprov ms `zmhostname` zimbraReverseProxyLookupTarget FALSEĪdditionally, zimbraReverseProxyLookupTarget is a server inherited attribute from the global configuration, so check if zimbraReverseProxyLookupTarget has been incorrectly designated in global config. If a non-mailbox server is listed, set the zimbraReverseProxyLookupTarget server configuration attribute to FALSE for that server. ![]() Grep zm_lookup_handlers /opt/zimbra/conf/nginx/includes/ ![]() To view the zmlookup lookup handlers, review the zm_lookup_handlers parameter in /opt/zimbra/conf/nginx/includes/ ![]() Only mailbox servers can perform route handler functions. Slow Proxy Logins - Route Lookup Handles (garpu)Ī common nginx misconfiguration is to have incorrectly designated non-mailbox servers as routing/zmlookup handlers. Proxy related errors can be found in the following logs on each proxy server: Zimbra Proxy Manual:Adding Additional Reverse Proxy To Zimbra Proxy Installing, Configuring, Disabling the Zimbra ProxyĬonfiguration And Template Files And Proxy Related VariablesĪdvanced Proxy Configuration Examples via CLI
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |