SBC: Restarting nginx-data alarm, Remote worker endpoints unable to register and SSYNDI Crashed
SOLN326965 | Version: 10.0 | Published: 06/29/2018 | Updated: 12/06/2019
Available To: Customer, Internal
Categories: Avaya Session Border Controller for Enterprise, Break/Fix
Details

 

 

SBCE 7.2.1

nginx restarting

 

Problem Clarification

 

·       Restarting nginx-data alarm, Remote worker endpoints unable to register and SSYNDI Crashed.

·       SBCE 1 status DOWN and SBCE 2 UP

·       Both nginx-data.service failed to start

 

1.           Restarting Nginx-data

The below error was seen during  restart nginx-data.

It seemed stuck to initialize RW_PPM_1 with user nginx. I checked the files but I did not find anything wrong so I removed all Reverse Proxy configurations  

Jun 28 19:29:44 SBCE-PRI systemd[1]: Starting LSB: Manages the SBC instance of nginx...

-- Subject: Unit nginx-data.service has begun start-up

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit nginx-data.service has begun starting up.

Jun 28 19:29:44 SBCE-PRI sudo[6257]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/su - nginx -s /bin/bash -c . /etc/rc.d/init.d/functions; daemon --pidfile /var/run/nginx-data.pid /usr/local/nginx/bin/nginx -c /usr/local/ngi

Jun 28 19:29:44 SBCE-PRI su[6258]: (to nginx) root on none

Jun 28 19:29:44 SBCE-PRI systemd-logind[723]: Failed to create /run/user: File exists

Jun 28 19:29:44 SBCE-PRI su[6258]: pam_systemd(su-l:session): Failed to create session: File exists

Jun 28 19:29:44 SBCE-PRI su[6258]: pam_unix(su-l:session): session opened for user nginx by (uid=0)

Jun 28 19:29:44 SBCE-PRI nginx-data[6246]: Starting nginx: nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/nginx/conf/nginx.conf:2

Jun 28 19:29:44 SBCE-PRI nginx-data[6246]: nginx: [emerg] host not found in upstream "ustreamRW_PPM_1" in /usr/local/nginx/conf/RW_PPM_1/RW_PPM_1_url.conf:2

Jun 28 19:29:44 SBCE-PRI su[6258]: pam_unix(su-l:session): session closed for user nginx

Jun 28 19:29:44 SBCE-PRI nginx-data[6246]: [FAILED]

Jun 28 19:29:44 SBCE-PRI systemd[1]: nginx-data.service: control process exited, code=exited status=1

Jun 28 19:29:44 SBCE-PRI systemd[1]: Failed to start LSB: Manages the SBC instance of nginx.

 

[ipcs@SBCE-PRI ~]$ service  nginx-data status

/usr/local/nginx/bin/nginx must be a real file.

/usr/local/nginx/conf/nginx.conf must be a real file.

nginx-data.service - LSB: Manages the SBC instance of nginx

Loaded: loaded (/etc/rc.d/init.d/nginx-data; bad; vendor preset: disabled)

Active: failed (Result: exit-code) since Thu 2018-06-28 16:53:56 EDT; 1min 55s ago

Docs: man:systemd-sysv-generator(8)

Process: 9680 ExecStart=/etc/rc.d/init.d/nginx-data start (code=exited, status=1/FAILURE)

 

root@SBCE-SEC conf]# /usr/local/nginx/bin/nginx -s reload

nginx: [emerg] host not found in upstream "ustreamRW_PPM_1" in /usr/local/nginx/conf/RW_PPM_1/RW_PPM_1_url.conf:

 

Also identified by the below errors in the /archive/log/nginx/error.log ------

 

2018/06/28 12:47:57 [warn] 24501#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/nginx/conf/nginx.conf:2

2018/06/28 12:47:57 [emerg] 24501#0: host not found in upstream "ustreamRW_PPM_1" in /usr/local/nginx/conf/RW_PPM_1/RW_PPM_1_url.conf:2

2018/06/28 12:48:22 [warn] 24677#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/nginx/conf/nginx.conf:2

2018/06/28 12:48:22 [emerg] 24677#0: host not found in upstream "ustreamRW_PPM_1" in /usr/local/nginx/conf/RW_PPM_1/RW_PPM_1_url.conf:2

 

 2.          HA status: 10.1.2.3 was Primary and 10.4.5.6 was DOWN

Both 10.1.2.3 and 10.4.5.6 were not working properly. 10.1.2.3 was changed to DOWN when I tried to restart ‘ipcs-init’ to bring 10.4.5.6 back.  Also found found ‘Ssyndi’ was not up on both servers.     

 

3.           Re-configured Reverse Proxy flows

Re-configured Reverse Proxy flows: RW_PPM_1, RW_PPM_2 and settings but there were four items missing that could not see the complete names of url from the screenshot.  

 

Solution