proxy - unknown directive "zmauth_zx"

[yakuraku1]

After a reboot I always get the following error when starting the zmproxy:

zmproxyctl start
Starting proxy...nginx: [emerg] unknown directive "zmauth_zx" in /opt/zimbra/conf/nginx/includes/nginx.conf.web:66
failed.

How can I resolve this?

System Ubuntu 18.04LTS
Zimbra: 8.8.12_GA_3803.FOSS

Only Zimbra is on the system, no other server.

[phoenix]

You do realise the Ubuntu 18.04 is 'beta' as far as ZCS is concerned, don't you? What changes, if any, did you make to the server before the reboot? An internet search throws up these two articles, see if they help: https://www.startpage.com/do/dsearch?qu ... ge=english

[yakuraku1]

Thanks for your reply.

Yes, I'm aware, that Zimbra does consider Ubuntu 18.04 still beta. But that is not really the point isn't it? Even when it is a beta, it could be considered good that there are people are using it and find bugs to get them fixed. Even more since Ubuntu 18.04 was released a year ago. But that's going to much off topic.

The 2 sites were unfortunately not very useful.

What I did was an apt upgrade. From the apt history.log:

Code: Select all

Start-Date: 2019-04-21  08:52:39
Commandline: apt upgrade -y
Upgrade: zimbra-proxy-patch:amd64 (8.8.12.1552427139.p0-1.u18, 8.8.12.1554984827.p1-1.u18), update-manager-core:amd64 (1:18.04.11.9, 1:18.04.11.10), python3-zope.interface:amd64 (4.3.2-1build2, 4.3.2-1+ubuntu18.04.1+certbot+1), libsystemd0:amd64 (237-3ubuntu10.19, 237-3ubuntu10.20), snapd:amd64 (2.37.4+18.04.1, 2.38+18.04), ubuntu-standard:amd64 (1.417, 1.417.1), console-setup-linux:amd64 (1.178ubuntu2.7, 1.178ubuntu2.8), open-vm-tools:amd64 (2:10.3.0-0ubuntu1~18.04.3, 2:10.3.5-7~ubuntu0.18.04.1), libaio1:amd64 (0.3.110-5, 0.3.110-5ubuntu0.1), udev:amd64 (237-3ubuntu10.19, 237-3ubuntu10.20), console-setup:amd64 (1.178ubuntu2.7, 1.178ubuntu2.8), ubuntu-server:amd64 (1.417, 1.417.1), zimbra-patch:amd64 (8.8.12.1552477867.p0-1.u18, 8.8.12.1554985662.p1-1.u18), libudev1:amd64 (237-3ubuntu10.19, 237-3ubuntu10.20), ubuntu-minimal:amd64 (1.417, 1.417.1), python3-distupgrade:amd64 (1:18.04.30, 1:18.04.31), python3-update-manager:amd64 (1:18.04.11.9, 1:18.04.11.10), ubuntu-release-upgrader-core:amd64 (1:18.04.30, 1:18.04.31), systemd-sysv:amd64 (237-3ubuntu10.19, 237-3ubuntu10.20), python3-configobj:amd64 (5.0.6-2, 5.0.6-2+ubuntu18.04.1+certbot+1), libpam-systemd:amd64 (237-3ubuntu10.19, 237-3ubuntu10.20), distro-info-data:amd64 (0.37ubuntu0.3, 0.37ubuntu0.4), systemd:amd64 (237-3ubuntu10.19, 237-3ubuntu10.20), libnss-systemd:amd64 (237-3ubuntu10.19, 237-3ubuntu10.20), keyboard-configuration:amd64 (1.178ubuntu2.7, 1.178ubuntu2.8), zimbra-common-core-jar:amd64 (8.8.12.1553847719-1.u18, 8.8.12.1554873515-1.u18)
End-Date: 2019-04-21  08:53:33

[JDunphy]

If you change zmauth_zx to zmauth does it work any better. I believe this is an enhancement from Zextras. Root cause for you I am guessing is that nginx apparently was replaced with an incorrect version somewhere or the template files are wrong. I run 8.7.11P11 so I can't speak from any authority here on exactly what circumstances got you there. You could also do a little digging:

Code: Select all

% strings ~/common/sbin/nginx |grep zmauth

To see what is available for your nginx.

Ref: https://github.com/Zimbra/zm-nginx-conf/pull/11

[LinuxCuba]

After a reboot I always get the following error when starting the zmproxy:

zmproxyctl start
Starting proxy...nginx: [emerg] unknown directive "zmauth_zx" in /opt/zimbra/conf/nginx/includes/nginx.conf.web:66
failed.

How can I resolve this?

System Ubuntu 18.04LTS
Zimbra: 8.8.12_GA_3803.FOSS

Only Zimbra is on the system, no other server.

Same problem after applying zimbra patch 1 to zimbra 8.8.12 in ubuntu 18.04 LTS. Reported here https://github.com/Zimbra/zm-nginx-conf ... t-33224374 Solved by reversing the change.

[LinuxCuba]

You do realise the Ubuntu 18.04 is 'beta' as far as ZCS is concerned, don't you? What changes, if any, did you make to the server before the reboot? An internet search throws up these two articles, see if they help: https://www.startpage.com/do/dsearch?qu ... ge=english

It has nothing to do that is beta in ubuntu 18.04, this beta is for that very thing, try it and solve the problems and report the same, this patch was applied correctly on zimbra 8.8.12 in ubuntu 16.04, but it gave problem with 18.04, what Developers must resolve these and other errors or errors reported by users. Thank you that it is free software.

[LinuxCuba]

If you change zmauth_zx to zmauth does it work any better. I believe this is an enhancement from Zextras. Root cause for you I am guessing is that nginx apparently was replaced with an incorrect version somewhere or the template files are wrong. I run 8.7.11P11 so I can't speak from any authority here on exactly what circumstances got you there. You could also do a little digging:

Code: Select all

% strings ~/common/sbin/nginx |grep zmauth

To see what is available for your nginx.

Ref: https://github.com/Zimbra/zm-nginx-conf/pull/11

This is very old and the change in the code of the nginx proxy configuration template is not now, in zimbra 8.8.11 is the same, running in ubuntu 16.04 never gave problems, neither 8.8.12 in this version of ubuntu, Why does it affect ubuntu 18.04 now? Look here https://github.com/Zimbra/zm-nginx-conf ... t-33224374

[LinuxCuba]

This is output ubuntu 16.04 LTS:
zimbra@zimbra:~$ strings ~/common/sbin/nginx |grep zmauth
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
zero valid zmauth route handlers
zmauth
zmauth_admin
zmauth_zx

And this is output ubuntu 18.04 LTS


zimbra@zimbra-proxy:~$ strings ~/common/sbin/nginx |grep zmauth
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
zero valid zmauth route handlers
zmauth
zmauth_admin

Note that in ubuntu 18.04 the zmauth_zx module does not exist.

[Veera]

got exactly the same problem with a brand new installation on Ubuntu 18.04. LTS (pre-installed by provider can't change it)

I could fix the nginx problem by replaceing "zmauth_zx" with "zmauth" in the file: /opt/zimbra/conf/nginx/includes/nginx.conf.web

I got this from the following link: https://github.com/Zimbra/zm-nginx-conf ... efceef87e9

I guess this is something that has to be fixed by the Zimbra Team

thanks

Release 8.8.12.GA.3794.UBUNTU18.64 UBUNTU18_64 FOSS edition, Patch 8.8.12_P1