1

Topic: Issue after upgrading to iRedAdmin-Pro-MySQL 1.9.1

==== Required information ====
- iRedMail version: 1.9.1
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Linux/BSD distribution name and version: CentOS 6.6
- Related log if you're reporting an issue:
====

After upgrading to iRedAdmin Pro to 1.9.1 i get an "Internal server error" trying to access iredadmin/system/throttling and a "not found" message trying to reach the /iredadmin/system/greylisting.

Regards.

----

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

2

Re: Issue after upgrading to iRedAdmin-Pro-MySQL 1.9.1

Sorry about this trouble. Any related error in Apache/Nginx log file?

3 (edited by matteo.frakka 2015-01-29 18:45:45)

Re: Issue after upgrading to iRedAdmin-Pro-MySQL 1.9.1

That's all:

[root@postfix httpd]# tail ssl_access_log
[...]
192.168.10.89 - - [29/Jan/2015:11:32:58 +0100] "GET /iredadmin/system/greylisting HTTP/1.1" 404 9
192.168.10.89 - - [29/Jan/2015:11:33:02 +0100] "GET /iredadmin/system/throttling HTTP/1.1" 500 21
[...]

[root@postfix httpd]# tail ssl_error_log
[...]
[Thu Jan 29 11:44:13 2015] [error] [client 192.168.10.89] Traceback (most recent call last):
[Thu Jan 29 11:44:13 2015] [error] [client 192.168.10.89]   File "/usr/lib/python2.6/site-packages/web/application.py", line 239, in process
[Thu Jan 29 11:44:13 2015] [error] [client 192.168.10.89]     return self.handle()
[Thu Jan 29 11:44:13 2015] [error] [client 192.168.10.89]   File "/usr/lib/python2.6/site-packages/web/application.py", line 230, in handle
[Thu Jan 29 11:44:13 2015] [error] [client 192.168.10.89]     return self._delegate(fn, self.fvars, args)
[Thu Jan 29 11:44:13 2015] [error] [client 192.168.10.89]   File "/usr/lib/python2.6/site-packages/web/application.py", line 416, in _delegate
[Thu Jan 29 11:44:13 2015] [error] [client 192.168.10.89]     mod = __import__(mod, None, None, [''])
[Thu Jan 29 11:44:13 2015] [error] [client 192.168.10.89] ImportError: No module named throttle
[Thu Jan 29 11:44:13 2015] [error] [client 192.168.10.89]

4

Re: Issue after upgrading to iRedAdmin-Pro-MySQL 1.9.1

Do you use Policyd or Cluebringer? Have correct SQL username/password in iRedAdmin-Pro config file?

5 (edited by matteo.frakka 2015-02-02 18:18:01)

Re: Issue after upgrading to iRedAdmin-Pro-MySQL 1.9.1

I've just done a check and we have both policyd and cluebringer installed but only policyd should be in use. Maybe cluebringer been installed with recent server update?

Username and password should be correct.

6

Re: Issue after upgrading to iRedAdmin-Pro-MySQL 1.9.1

Could you please double check which one is running? Policyd, or Cluebringer? And verify the SQL username/password with SQL command line tool please.

7

Re: Issue after upgrading to iRedAdmin-Pro-MySQL 1.9.1

I checked the credential stored in setting.py:

Credentials for user iredadmin on db iredadmin => Ok.
Credentials for user vmailadmin on db vmail => Ok.
Credentials for user policyd on db policyd => Ok.
Credentials for user amavisd on db amavisd => Ok.

$ service policyd status
policyd (pid  2750) is running...
$ service cbpolicyd status
cbpolicyd is stopped
$ chkconfig | grep cbpolicyd
cbpolicyd       0:off   1:off   2:off   3:off   4:off   5:off   6:off

So we are using policyd.

8

Re: Issue after upgrading to iRedAdmin-Pro-MySQL 1.9.1

Is it possible to let me login to your server for further debug?

9

Re: Issue after upgrading to iRedAdmin-Pro-MySQL 1.9.1

Ok.
I'm sending you an email with credentials to log in.

10

Re: Issue after upgrading to iRedAdmin-Pro-MySQL 1.9.1

Fixed.

I checked source code commit logs, the 2 urls (/system/greylisting, /system/throttling) don't exist (for Policyd) at all, but in an old commit log, I restructured file templates/default/layout.html, and made this mistake.

Simply removed these two links in layout.html. It should be fine now.

Thanks very much for your feedback and help. smile