1

Topic: Upgraded to iRedAdmin-Pro-SQL-4.3 and website is now down

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.2.1
- Deployed with iRedMail Easy or the downloadable installer? download installer
- Linux/BSD distribution name and version: Centos 7.8
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
When going to https://mail2.secureto.us/iredadmin/login I am now getting a 502 Bad Gateway nginx error.
Restart and different browsers are not fixing the issue.
NGINX is running:
[root@mail etc]# service nginx status
Redirecting to /bin/systemctl status nginx.service
● nginx.service - The nginx HTTP and reverse proxy server
   Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2020-05-05 11:15:41 EDT; 13min ago
  Process: 1027 ExecStart=/usr/sbin/nginx (code=exited, status=0/SUCCESS)
  Process: 991 ExecStartPre=/usr/sbin/nginx -t (code=exited, status=0/SUCCESS)
  Process: 969 ExecStartPre=/usr/bin/rm -f /run/nginx.pid (code=exited, status=0/SUCCESS)
Main PID: 1055 (nginx)
   CGroup: /system.slice/nginx.service
           â”œâ”€1055 nginx: master process /usr/sbin/nginx
           â””─1063 nginx: worker process

May 05 11:15:41 mail.sipmadeeasy.com systemd[1]: Starting The nginx HTTP and reverse proxy server...
May 05 11:15:41 mail.sipmadeeasy.com nginx[991]: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
May 05 11:15:41 mail.sipmadeeasy.com nginx[991]: nginx: configuration file /etc/nginx/nginx.conf test is successful
May 05 11:15:41 mail.sipmadeeasy.com systemd[1]: Failed to parse PID from file /run/nginx.pid: Invalid argument
May 05 11:15:41 mail.sipmadeeasy.com systemd[1]: Started The nginx HTTP and reverse proxy server.


And as I think is expected, Apache is not running.

Apache is not running:
Redirecting to /bin/systemctl status httpd.service
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2020-05-05 11:30:12 EDT; 5s ago
     Docs: man:httpd(8)
           man:apachectl(8)
  Process: 2595 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 2595 (code=exited, status=1/FAILURE)

May 05 11:30:11 mail.sipmadeeasy.com systemd[1]: Starting The Apache HTTP Server...
May 05 11:30:12 mail.sipmadeeasy.com httpd[2595]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
May 05 11:30:12 mail.sipmadeeasy.com httpd[2595]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
May 05 11:30:12 mail.sipmadeeasy.com httpd[2595]: no listening sockets available, shutting down
May 05 11:30:12 mail.sipmadeeasy.com httpd[2595]: AH00015: Unable to open logs
May 05 11:30:12 mail.sipmadeeasy.com systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
May 05 11:30:12 mail.sipmadeeasy.com systemd[1]: Failed to start The Apache HTTP Server.
May 05 11:30:12 mail.sipmadeeasy.com systemd[1]: Unit httpd.service entered failed state.
May 05 11:30:12 mail.sipmadeeasy.com systemd[1]: httpd.service failed.

Any help would be very much appreciated!!
Ray

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Upgraded to iRedAdmin-Pro-SQL-4.3 and website is now down

Did you try to restart "iredadmin" service?

3 (edited by rhowe 2020-05-05 23:45:04)

Re: Upgraded to iRedAdmin-Pro-SQL-4.3 and website is now down

ZhangHuangbin wrote:

Did you try to restart "iredadmin" service?

[root@mail etc]# service iredadmin restart
Redirecting to /bin/systemctl restart iredadmin.service
[root@mail etc]# service iredadmin status
Redirecting to /bin/systemctl status iredadmin.service
● iredadmin.service - iRedAdmin daemon service
   Loaded: loaded (/usr/lib/systemd/system/iredadmin.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2020-05-05 11:43:14 EDT; 3s ago
  Process: 2896 ExecStopPost=/usr/bin/rm -rf /var/run/iredadmin (code=exited, status=0/SUCCESS)
  Process: 2892 ExecStart=/usr/bin/uwsgi --ini /opt/www/iredadmin/rc_scripts/uwsgi/rhel8.ini --pidfile /var/run/iredadmin/iredadmin.pid (code=exited, status=203/EXEC)
  Process: 2889 ExecStartPre=/usr/bin/chmod 0755 /var/run/iredadmin (code=exited, status=0/SUCCESS)
  Process: 2886 ExecStartPre=/usr/bin/chown iredadmin:iredadmin /var/run/iredadmin (code=exited, status=0/SUCCESS)
  Process: 2884 ExecStartPre=/usr/bin/mkdir /var/run/iredadmin (code=exited, status=0/SUCCESS)
Main PID: 2892 (code=exited, status=203/EXEC)

May 05 11:43:14 mail.sipmadeeasy.com systemd[1]: Starting iRedAdmin daemon service...
May 05 11:43:14 mail.sipmadeeasy.com systemd[1]: Started iRedAdmin daemon service.
May 05 11:43:14 mail.sipmadeeasy.com systemd[2892]: Failed at step EXEC spawning /usr/bin/uwsgi: No such file or directory
May 05 11:43:14 mail.sipmadeeasy.com systemd[1]: iredadmin.service: main process exited, code=exited, status=203/EXEC
May 05 11:43:14 mail.sipmadeeasy.com systemd[1]: Unit iredadmin.service entered failed state.
May 05 11:43:14 mail.sipmadeeasy.com systemd[1]: iredadmin.service failed.


Looks like we found the problem...but now what?  smile

4

Re: Upgraded to iRedAdmin-Pro-SQL-4.3 and website is now down

Looking through the server, Failed at step EXEC spawning /usr/bin/uwsgi: No such file or directory
[root@mail /]# find / -name uwsgi
/run/uwsgi
/root/iRedAdmin-Pro-SQL-4.2/rc_scripts/uwsgi
/root/netdata-v1.21.1/collectors/python.d.plugin/uwsgi
/root/iRedAdmin-Pro-SQL-4.3/rc_scripts/uwsgi
/var/lib/nginx/tmp/uwsgi
/usr/sbin/uwsgi
/usr/lib64/uwsgi
/opt/www/iRedAdmin-1.0/rc_scripts/uwsgi
/opt/www/iRedAdmin-Pro-SQL-4.2/rc_scripts/uwsgi
/opt/www/iRedAdmin-Pro-SQL-4.3/rc_scripts/uwsgi
/opt/mlmmjadmin-2.1/rc_scripts/uwsgi

5

Re: Upgraded to iRedAdmin-Pro-SQL-4.3 and website is now down

rhowe wrote:

/usr/sbin/uwsgi

Please update file /etc/systemd/system/multi-user.target.wants/iredadmin.service, replace incorrect uwsgi path (/usr/bin/uwsgi) by the correct one (/usr/sbin/uwsgi), then restart iredadmin service:

systemctl daemon-reload
service iredadmin restart

Upgrading iRedAdmin-Pro doesn't change uwsgi path, so the question for you: Why did the uwsgi path change? I assume it was changed before upgrading iRedAdmin-Pro.