Code: Select all
sudo su - zimbra
zmproxyctl stop
Stopping proxy...failed.
Code: Select all
ps aux | grep nginx
root 22633 0.0 0.0 47272 1792 ? Ss 10:16 0:00 nginx: master process /opt/zimbra/common/sbin/nginx -c /opt/zimbra/conf/nginx.conf
zimbra 22635 0.0 0.0 56268 12092 ? S 10:16 0:00 nginx: worker process
zimbra 22636 0.0 0.0 56048 11896 ? S 10:16 0:00 nginx: worker process
zimbra 22637 0.0 0.0 55820 8508 ? S 10:16 0:00 nginx: worker process
zimbra 22638 0.0 0.0 56384 12808 ? S 10:16 0:00 nginx: worker process
Code: Select all
sudo su - zimbra
kill -0 22633
-su: kill: (22633) - Operation not permitted
I have killed nginx AS root (using sudo) and then as the zimbra user started the proxy with
Code: Select all
sudo su - zimbra
zmproxyctl start
Starting proxy...nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /opt/zimbra/conf/nginx/includes/nginx.conf.mail.imaps.default:13
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /opt/zimbra/conf/nginx/includes/nginx.conf.mail.pop3s.default:13
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /opt/zimbra/conf/nginx/includes/nginx.conf.web.https.default:40
done.
My question is: What is the correct way to repair this? I am using LetsEncrypt scripts that need to restart the proxy automatically and this is now failing most of the time.