1 Topic by mikek (edited by mikek 2020-08-21 05:16:52)

  • mikek
  • Member
  • Offline
  • Registered: 2020-08-20
  • Posts: 18

Topic: Upgrade from community to iRedAdmin-PRO - bad gateway

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version: v1.3.1
- Deployed with iRedMail Easy or the downloadable installer? What is iRedmail Easy?
- Linux/BSD distribution name and version: Ubuntu 20.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MYSQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? Trying to upgrade
====

I installed the comunity version and have it running ok.
I bought the PRO and try to follow the instructions.
Now I get Bad Gateway on domain.com/iredadmin.

Q. How to fix the error Bad Gateway after a successful install?

----

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

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: Upgrade from community to iRedAdmin-PRO - bad gateway

Hi Mike,

Sorry about this trouble.
Please visit the iRedAdmin-Pro again, then run commands below immediately and show us the output:

service iredadmin status
tail -20 /var/log/syslog

3 Reply by mikek

  • mikek
  • Member
  • Offline
  • Registered: 2020-08-20
  • Posts: 18

Re: Upgrade from community to iRedAdmin-PRO - bad gateway

Thanks ZhangHuangbin, I sent you a coffee smile
What I see is "mail iredadmin: -- unavailable modifier requested: 0 --"

mike@mail:/root/iRedAdmin-Pro-SQL-4.4/tools$ service iredadmin status
● iredadmin.service - iRedAdmin daemon service
     Loaded: loaded (/lib/systemd/system/iredadmin.service; enabled; vendor preset: ena>
     Active: active (running) since Thu 2020-08-20 23:23:16 UTC; 15h ago
    Process: 936 ExecStartPre=/bin/mkdir -p /var/run/iredadmin (code=exited, status=0/S>
    Process: 982 ExecStartPre=/bin/chown iredadmin:iredadmin /var/run/iredadmin (code=e>
    Process: 991 ExecStartPre=/bin/chmod 0755 /var/run/iredadmin (code=exited, status=0>
   Main PID: 996 (uwsgi)
      Tasks: 6 (limit: 4601)
     Memory: 4.0M
     CGroup: /system.slice/iredadmin.service
             ├─ 996 /usr/bin/uwsgi --ini /opt/www/iredadmin/rc_scripts/uwsgi/debian.ini>
             ├─1005 /usr/bin/uwsgi --ini /opt/www/iredadmin/rc_scripts/uwsgi/debian.ini>
             ├─1006 /usr/bin/uwsgi --ini /opt/www/iredadmin/rc_scripts/uwsgi/debian.ini>
             ├─1007 /usr/bin/uwsgi --ini /opt/www/iredadmin/rc_scripts/uwsgi/debian.ini>
             ├─1008 /usr/bin/uwsgi --ini /opt/www/iredadmin/rc_scripts/uwsgi/debian.ini>
             └─1009 /usr/bin/uwsgi --ini /opt/www/iredadmin/rc_scripts/uwsgi/debian.ini>

Aug 20 23:23:16 mail.mydomain.com iredadmin[996]: spawned uWSGI master process (pid: 99>
Aug 20 23:23:16 mail.mydomain.com iredadmin[996]: spawned uWSGI worker 1 (pid: 1005, co>
Aug 20 23:23:16 mail.mydomain.com iredadmin[996]: spawned uWSGI worker 2 (pid: 1006, co>
Aug 20 23:23:16 mail.mydomain.com iredadmin[996]: spawned uWSGI worker 3 (pid: 1007, co>
Aug 20 23:23:16 mail.mydomain.com iredadmin[996]: spawned uWSGI worker 4 (pid: 1008, co>
Aug 20 23:23:16 mail.mydomain.com iredadmin[996]: spawned uWSGI worker 5 (pid: 1009, co>
Aug 20 23:23:28 mail.mydomain.com iredadmin[996]: -- unavailable modifier requested: 0 >
Aug 20 23:23:29 mail.mydomain.com iredadmin[996]: -- unavailable modifier requested: 0 >
Aug 20 23:23:33 mail.mydomain.com iredadmin[996]: -- unavailable modifier requested: 0 >
Aug 21 14:56:20 mail.mydomain.com iredadmin[996]: -- unavailable modifier requested: 0 >
*edited where mydomain is used to hide my real domain.


mike@mail:/root/iRedAdmin-Pro-SQL-4.4/tools$ tail -20 /var/log/syslog
Aug 21 15:03:01 mail CRON[53525]: (root) CMD (/bin/bash /usr/local/bin/fail2ban_banned_db unban_db)
Aug 21 15:03:45 mail PackageKit: refresh-cache transaction /2211_bbbccdac from uid 1000 finished with failed after 553ms
Aug 21 15:03:46 mail PackageKit: get-updates transaction /2212_bbdcdbeb from uid 1000 finished with success after 717ms
Aug 21 15:05:02 mail CRON[53629]: (sogo) CMD (/usr/sbin/sogo-tool expire-sessions 30 >/dev/null 2>&1; /usr/sbin/sogo-ealarms-notify >/dev/null 2>&1)
Aug 21 15:05:06 mail iredadmin: -- unavailable modifier requested: 0 --
Aug 21 15:05:12 mail postfix/anvil[53448]: statistics: max connection rate 1/60s for (smtpd:40.107.67.40) at Aug 21 15:01:49
Aug 21 15:05:12 mail postfix/anvil[53448]: statistics: max connection count 1 for (smtpd:40.107.67.40) at Aug 21 15:01:49
Aug 21 15:05:12 mail postfix/anvil[53448]: statistics: max cache size 1 at Aug 21 15:01:49
Aug 21 15:06:01 mail CRON[53679]: (sogo) CMD (/usr/sbin/sogo-tool expire-sessions 30 >/dev/null 2>&1; /usr/sbin/sogo-ealarms-notify >/dev/null 2>&1)
Aug 21 15:06:01 mail CRON[53680]: (root) CMD (/bin/bash /usr/local/bin/fail2ban_banned_db unban_db)
Aug 21 15:07:01 mail CRON[53724]: (sogo) CMD (/usr/sbin/sogo-tool expire-sessions 30 >/dev/null 2>&1; /usr/sbin/sogo-ealarms-notify >/dev/null 2>&1)
Aug 21 15:07:01 mail CRON[53725]: (root) CMD (/bin/bash /usr/local/bin/fail2ban_banned_db unban_db)
Aug 21 15:08:50 mail PackageKit: daemon quit
Aug 21 15:08:50 mail systemd[1]: packagekit.service: Succeeded.
Aug 21 15:09:00 mail systemd[1]: Starting Clean php session files...
Aug 21 15:09:01 mail CRON[53882]: (root) CMD (/bin/bash /usr/local/bin/fail2ban_banned_db unban_db)
Aug 21 15:09:01 mail CRON[53883]: (sogo) CMD (/usr/sbin/sogo-tool expire-sessions 30 >/dev/null 2>&1; /usr/sbin/sogo-ealarms-notify >/dev/null 2>&1)
Aug 21 15:09:01 mail CRON[53884]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Aug 21 15:09:01 mail systemd[1]: phpsessionclean.service: Succeeded.
Aug 21 15:09:01 mail systemd[1]: Finished Clean php session files.
Aug 21 15:10:01 mail CRON[53963]: (sogo) CMD (/usr/sbin/sogo-tool expire-sessions 30 >/dev/null 2>&1; /usr/sbin/sogo-ealarms-notify >/dev/null 2>&1)
Aug 21 15:12:01 mail CRON[54098]: (root) CMD (/bin/bash /usr/local/bin/fail2ban_banned_db unban_db)
Aug 21 15:17:34 mail iredadmin: -- unavailable modifier requested: 0 --

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: Upgrade from community to iRedAdmin-PRO - bad gateway

Update: it's a bug of iRedAdmin-Pro upgrade script. It's been fixed, let me know if you need a patched iRedAdmin-Pro version.

5 Reply by mikek

  • mikek
  • Member
  • Offline
  • Registered: 2020-08-20
  • Posts: 18

Re: Upgrade from community to iRedAdmin-PRO - bad gateway

The patch worked. Thank you!