Any chance you have a nginx running that is bound to ipv4 from a previous start/stop cycle? It seems weird that its only bound to the ipv4 socket (ie. tcp LISTEN) after your zmcontrol restart... but other services are shown as (tcp6 LISTEN). Almost like nginx isn't restarting, or has the correct listen statement in its nginx/includes files or was compiled without ipv6 support.
Did you check /opt/zimbra/log/nginx.log ... Mine shows both ipv4 and ipv6 addresses. It also show the starts as it is bounced.
Code: Select all
strings /opt/zimbra/common/sbin/nginx |grep with-ipv6
configure arguments: --prefix=/opt/zimbra/common --with-cc-opt='-g -I/opt/zimbra/common/include' --with-ld-opt='-Wl,-rpath,/opt/zimbra/common/lib -L/opt/zimbra/common/lib' --with-debug --with-ipv6 --with-http_ssl_module --with-http_stub_status_module --with-pcre --with-http_upstream_zmauth_module --with-http_zm_sso_module --with-http_spdy_module --with-mail --with-mail-sasl --with-mail_ssl_module --error-log-path=/opt/zimbra/log/nginx.log --http-log-path=/opt/zimbra/log/nginx.access.log --http-client-body-temp-path=/opt/zimbra/data/tmp/nginx/client --http-proxy-temp-path=/opt/zimbra/data/tmp/nginx/proxy --http-fastcgi-temp-path=/opt/zimbra/data/tmp/nginx/fastcgi --without-http_scgi_module --without-http_uwsgi_module --add-module=modules/nviennot-nginx-tcp-keepalive