1

Topic: internal server error after upgrade to 3.7 or 3.8

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 9.9
- Deployed with iRedMail Easy or the downloadable installer? Download
- Linux/BSD distribution name and version: FreeBSD 10.x Jail
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Apache 2.4.x
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Hi,
yesterday i finally got the time to upgrade my iRedAdmin-Pro from 2.9 to the latest.
Got a problem (i was getting a internal server error). While looking to debug the issue today I noticed teh new 3.8 version, so I tried that one, but i get the same error, here are the relevant logs from apache.

[Thu Aug 01 16:32:58.404478 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898] Traceback (most recent call last):
[Thu Aug 01 16:32:58.404517 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]   File "/usr/local/lib/python2.7/site-packages/web/application.py", line 239, in process
[Thu Aug 01 16:32:58.404542 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]     return self.handle()
[Thu Aug 01 16:32:58.404555 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]   File "/usr/local/lib/python2.7/site-packages/web/application.py", line 230, in handle
[Thu Aug 01 16:32:58.404567 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]     return self._delegate(fn, self.fvars, args)
[Thu Aug 01 16:32:58.404579 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]   File "/usr/local/lib/python2.7/site-packages/web/application.py", line 458, in _delegate
[Thu Aug 01 16:32:58.404596 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]     mod = __import__(mod, None, None, [''])
[Thu Aug 01 16:32:58.404609 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]   File "/usr/local/www/iredadmin/controllers/sql/basic.py", line 9, in <module>
[Thu Aug 01 16:32:58.404622 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]     from libs import iredutils, sysinfo, form_utils
[Thu Aug 01 16:32:58.404638 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]   File "/usr/local/www/iredadmin/libs/sysinfo.py", line 13, in <module>
[Thu Aug 01 16:32:58.404651 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]     from libs.logger import log_traceback
[Thu Aug 01 16:32:58.404663 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]   File "/usr/local/www/iredadmin/libs/logger.py", line 30, in <module>
[Thu Aug 01 16:32:58.404681 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]     _handler = SysLogHandler(address=_server, facility=settings.SYSLOG_FACILITY)
[Thu Aug 01 16:32:58.404694 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]   File "/usr/local/lib/python2.7/logging/handlers.py", line 761, in __init__
[Thu Aug 01 16:32:58.404706 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]     self._connect_unixsocket(address)
[Thu Aug 01 16:32:58.404718 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]   File "/usr/local/lib/python2.7/logging/handlers.py", line 804, in _connect_unixsocket
[Thu Aug 01 16:32:58.404737 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]     self.socket.connect(address)
[Thu Aug 01 16:32:58.404749 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]   File "/usr/local/lib/python2.7/socket.py", line 228, in meth
[Thu Aug 01 16:32:58.404761 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]     return getattr(self._sock,name)(*args)
[Thu Aug 01 16:32:58.404778 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898] error: [Errno 2] No such file or directory
[Thu Aug 01 16:32:58.404799 2019] [wsgi:error] [pid 69147] [remote [REMOTE_IP]:57898]


Any suggestion on how i could further debug it?
Is it possible that the issue is caused by jumping from 2.9?
Thank you.

----

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 after upgrade to 3.7 or 3.8

Does your server has /dev/log for syslog?

3

Re: internal server error after upgrade to 3.7 or 3.8

ZhangHuangbin wrote:

Does your server has /dev/log for syslog?

no /dev/log
syslog has pretty much the default configurations in my system, the only difference is an entry for mlmmjadmin:

!mlmmjadmin
local5.*            /var/log/mlmmjadmin/mlmmjadmin.log

4

Re: internal server error after upgrade to 3.7 or 3.8

On FreeBSD, please add one setting in iRedAdmin-Pro config file:

SYSLOG_SERVER = '/var/run/log'

Then restart "iredadmin" service.

This issue has been fixed in iRedAdmin-Pro (development edition) upgrade script.