Issue
Following the update of ea-nginx to version ea-nginx-1.26.3-4.el*.cloudlinux.1.1, servers with Imunify360 installed may encounter instances of the Nginx service becoming unavailable due to this or a related error:
# systemctl status nginx.service
● nginx.service - nginx - high performance web server
Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2025-05-20 01:11:00 +01; 32s ago
Docs: http://nginx.org/en/docs/
Process: 46772 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=1/FAILURE)
May 20 09:14:47 example.com nginx[35476]: nginx: [emerg] bind() to 0.0.0.0:52229 failed (98: Address already in use)
May 20 09:14:47 example.com nginx[35476]: nginx: [emerg] bind() to [::]:52229 failed (98: Address already in use)
May 20 09:14:47 example.com nginx[35476]: nginx: [emerg] bind() to 0.0.0.0:52231 failed (98: Address already in use)
May 20 09:14:47 example.com nginx[35476]: nginx: [emerg] bind() to [::]:52231 failed (98: Address already in use)
tcp 0 0 0.0.0.0:52227 0.0.0.0:* LISTEN 0 2017792709 36644/im360: master
tcp 0 0 0.0.0.0:52229 0.0.0.0:* LISTEN 0 2017792710 36644/im360: master
tcp 0 0 0.0.0.0:52231 0.0.0.0:* LISTEN 0 2017792711 36644/im360: master
Environment
- Imunify360
- Webshield
- ea-nginx-1.26.3-4
Solution
Update the package to the most recent version:
yum update ea-nginx --enablerepo=cloudlinux-ea4-rollout-11-bypass
Cause
Product issue DEF-34054.
Useful links
Comments
0 comments
Please sign in to leave a comment.