1 Topic by Jim O

  • Jim O
  • Member
  • Offline
  • Registered: 2017-05-06
  • Posts: 8

Topic: Unable to reach dashboard after upgrade (500 Internal Server Error)

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.8
- Linux/BSD distribution name and version: Ubuntu  16.0.4
- 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. xx.yy.zz.104 - - [10/Apr/2018:16:36:23 -0400] "GET /iredadmin/login HTTP/2.0" 500 21 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36"
====

After upgrading to iRedMail 0.9.8 and iReadAdminPro 2.9.0, I can't reach the dashboard. All I get is an internal server error (500).

Roundcube (1.3.5) and Sogo (4) are working so it doesn't seem to be an issue with nginx itself.

----

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

2 Reply by Jim O

  • Jim O
  • Member
  • Offline
  • Registered: 2017-05-06
  • Posts: 8

Re: Unable to reach dashboard after upgrade (500 Internal Server Error)

Nothing? Really?

3 Reply by ZhangHuangbin

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

Re: Unable to reach dashboard after upgrade (500 Internal Server Error)

Sorry i missed this post.

*) Any error in Nginx error log file? Or uwsgi log file?
*) Did you follow our tutorial to upgrade iRedMail to the latest iRedMail-0.9.8 before upgrading iRedAdmin-Pro?
*) Do you have mlmmj and mlmmjadmin integrated and working?

4 Reply by Jim O

  • Jim O
  • Member
  • Offline
  • Registered: 2017-05-06
  • Posts: 8

Re: Unable to reach dashboard after upgrade (500 Internal Server Error)

1) nginx log as above. uwsgi log:

# tail iredadmin.log
    from libs.sqllib import utils as sql_lib_utils
  File "/opt/www/iRedAdmin-Pro-SQL-2.9.0/libs/sqllib/utils.py", line 11, in <module>
    from libs.sqllib import user as sql_lib_user
  File "/opt/www/iRedAdmin-Pro-SQL-2.9.0/libs/sqllib/user.py", line 17, in <module>
    from libs import mlmmj
  File "/opt/www/iRedAdmin-Pro-SQL-2.9.0/libs/mlmmj/__init__.py", line 12, in <module>
    api_headers = {settings.MLMMJADMIN_API_AUTH_HEADER: settings.mlmmjadmin_api_auth_token}
AttributeError: 'module' object has no attribute 'mlmmjadmin_api_auth_token'

maurice.jlkmail.com [pid: 1262|app: 0|req: 16/24] 70.104.198.154 () {52 vars in 1018 bytes} [Thu Apr 26 09:07:59 2018] GET /iredadmin/login => generated 21 bytes in 163 msecs (HTTP/2.0 500) 2 headers in 165 bytes (2 switches on core 0)

2)yes

3) no

5 Reply by ZhangHuangbin

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

Re: Unable to reach dashboard after upgrade (500 Internal Server Error)

Jim O wrote:

2)yes
3) no

This is conflict.
We mention how to integrate mlmmj (and mlmmjadmin) in iRedMail upgrade tutorial:
https://docs.iredmail.org/upgrade.iredm … egration_1 (for MySQL/MariaDB backend)

Please follow the upgrade tutorial to integrate mlmmj and mlmmjadmin first, then re-run iRedAdmin-Pro upgrade script.

6 Reply by Jim O

  • Jim O
  • Member
  • Offline
  • Registered: 2017-05-06
  • Posts: 8

Re: Unable to reach dashboard after upgrade (500 Internal Server Error)

ZhangHuangbin wrote:
Jim O wrote:

2)yes
3) no

This is conflict.
We mention how to integrate mlmmj (and mlmmjadmin) in iRedMail upgrade tutorial:
https://docs.iredmail.org/upgrade.iredm … egration_1 (for MySQL/MariaDB backend)

Please follow the upgrade tutorial to integrate mlmmj and mlmmjadmin first, then re-run iRedAdmin-Pro upgrade script.

My mistake. I thought it was optional. Problem solved.