1

Topic: Internal server error when editing user following upgrade

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.9
- Deployed with iRedMail Easy or the downloadable installer? downloadable installer
- Linux/BSD distribution name and version:  Debian 8.3
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- 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.
====

Can't find much interesting in error logs, other than this in syslog

Any suggestions?

Feb  6 17:40:11 hostname uwsgi: Traceback (most recent call last):#012 
File "/usr/lib/python2.7/dist-packages/web/application.py", line 239, in process#012    return self.handle()#012 
File "/usr/lib/python2.7/dist-packages/web/application.py", line 230, in handle#012    return self._delegate(fn, self.fvars, args)#012 
File "/usr/lib/python2.7/dist-packages/web/application.py", line 420, in _delegate#012    return handle_class(cls)#012 
File "/usr/lib/python2.7/dist-packages/web/application.py", line 396, in handle_class#012    return tocall(*args)#012 
File "/opt/www/iRedAdmin-Pro-LDAP-3.3/controllers/ldap/user.py", line 293, in GET#012   
_qr = mlmmj.get_subscribed_lists(mail=mail, query_all_lists=False)#012
File "/opt/www/iRedAdmin-Pro-LDAP-3.3/libs/mlmmj/__init__.py", line 338, in get_subscribed_lists#012   
r = requests.get(url, params=params, headers=api_headers, verify=_verify_ssl)#012 
File "/usr/lib/python2.7/dist-packages/requests/api.py", line 70, in get#012   
return request('get', url, params=params, **kwargs)#012 
File "/usr/lib/python2.7/dist-packages/requests/api.py", line 56, in request#012   
return session.request(method=method, url=url, **kwargs)#012 
File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 475, in request#012    resp = self.send(prep, **send_kwargs)#012 
File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 596, in send#012   
r = adapter.send(request, **kwargs)#012 
File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line 487, in send#012   
raise ConnectionError(e, request=request)#012
ConnectionError: HTTPConnectionPool(host='127.0.0.1', port=7790): Max retries exceeded with url: /api/subscriber/bob@hope.com/subscribed?query_all_lists=no&email_only=no (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7f038fa24750>: Failed to establish a new connection: [Errno 111] Connection refused',))
Feb  6 17:40:11 hostname uwsgi:
Feb  6 17:40:11 hostname uwsgi: domain [pid: 30430|app: 1|req: 74/94] remote host ip () {50 vars in 1104 bytes} [Wed Feb  6 17:40:11 2019] GET /iredadmin/profile/user/general/bob@hope.com => generated 21 bytes in 52 msecs (HTTP/1.1 500) 2 headers in 164 bytes (2 switches on core 0)

----

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

2

Re: Internal server error when editing user following upgrade

Port 7790 is mlmmjadmin service, please try to restart it, then iRedAdmin-Pro should work fine.

3

Re: Internal server error when editing user following upgrade

ZhangHuangbin wrote:

Port 7790 is mlmmjadmin service, please try to restart it, then iRedAdmin-Pro should work fine.

Sorry for the delayed reply.
Just getting back to this now
Restarting the service didn't help
Only thing I notice that is odd, is that there are two identical entries in syslog....

Apr 20 23:18:34 stimail uwsgi: 127.0.0.1:7790 [pid: 29675|app: -1|req: -1/2] 127.0.0.1 () {32 vars in 564 bytes} [Sat Apr 20 23:18:34 2019] GET /api/subscriber/bob@hope.com/subscribed?query_all_lists=no&email_only=no => generated 21 bytes in 0 msecs (HTTP/1.1 500) 2 headers in 83 bytes (0 switches on core 0)
Apr 20 23:18:34 stimail uwsgi: 127.0.0.1:7790 [pid: 29675|app: -1|req: -1/2] 127.0.0.1 () {32 vars in 564 bytes} [Sat Apr 20 23:18:34 2019] GET /api/subscriber/bob@hope.com/subscribed?query_all_lists=no&email_only=no => generated 21 bytes in 0 msecs (HTTP/1.1 500) 2 headers in 83 bytes (0 switches on core 0)

Netstat shows that the service is running

tcp        0      0 127.0.0.1:7790          0.0.0.0:*               LISTEN

Any other suggestion as to what I should look for? (configs / logs?)

4

Re: Internal server error when editing user following upgrade

Which version of mlmmjadmin are you running? Try to upgrade to version 2.1 first, make sure it's running, then try again with iRedAdmin-Pro.

FYI: https://docs.iredmail.org/upgrade.mlmmjadmin.html

5

Re: Internal server error when editing user following upgrade

ZhangHuangbin wrote:

Which version of mlmmjadmin are you running? Try to upgrade to version 2.1 first, make sure it's running, then try again with iRedAdmin-Pro.

FYI: https://docs.iredmail.org/upgrade.mlmmjadmin.html

I am already running 2.1. The upgrade to 0.9.9 went OK.
I am pretty sure the issue started when upgrading to 0.9.8, but I may be recalling incorrectly??
And I have brought the Admin panel up to 3.5
So pretty much all up to date.

Netstat still shows
tcp        0      0 127.0.0.1:7790          0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:7791          0.0.0.0:*               LISTEN
So I am guessing something is running there

Any other logs or configs I should be checking for you?

Many thanks

6

Re: Internal server error when editing user following upgrade

1: please turn on debug mode in mlmmjadmin config file /opt/mlmmjadmin/settings.py, parameter "log_level", restart mlmmjadmin service.

log_level = "debug"

2: reproduce this issue again, check /var/log/syslog and /var/log/mlmmjadmin/mlmmjadmin.log.

7

Re: Internal server error when editing user following upgrade

I solved the issue.
What I found was an error (well a few actually) in my edits that had been done when doing the uprade at

https://docs.iredmail.org/integration.mlmmj.ldap.html

I restarted all the services (shutdown -r now  .....)
And a few errors came up.
The Postfix integration was not right.
So I went through and redid all the edits on that page, and it all seems to be better now.

I am pretty sure that mlmmjadmin was running, but not talking to Postfix.

Thanks for you help and patience.