1 Topic by igor

  • igor
  • Member
  • Offline
  • Registered: 2013-12-17
  • Posts: 16

Topic: "internal server error" after upgrade to ver. pro-1.8.0 mysql

==== Required information ====
- iRedMail version: 0.8.5
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Linux/BSD distribution name and version: Debian 7
- Related log if you're reporting an issue: see below
====
I get "internal server error" when clicking on "Edit Account" of some profile within the List of Domains page.
The page returned is blank, with the only message "internal server error" on it. I am loged in as global admin. MySQL server is running. Other pages (under/iredadmin/base url) work normal.

[Dec 17 14:07:18 2013] [error] Traceback (most recent call last):
[Dec 17 14:07:18 2013] [error] File "/usr/lib/python2.7/dist-packages/web/application.py", line 239, in process
[Dec 17 14:07:18 2013] [error] return self.handle()
[Dec 17 14:07:18 2013] [error] File "/usr/lib/python2.7/dist-packages/web/application.py", line 230, in handle
[Dec 17 14:07:18 2013] [error] return self._delegate(fn, self.fvars, args)
[Dec 17 14:07:18 2013] [error] File "/usr/lib/python2.7/dist-packages/web/application.py", line 420, in _delegate
[Dec 17 14:07:18 2013] [error] return handle_class(cls)
[Dec 17 14:07:18 2013] [error] File "/usr/lib/python2.7/dist-packages/web/application.py", line 396, in handle_class
[Dec 17 14:07:18 2013] [error] return tocall(*args)
[Dec 17 14:07:18 2013] [error] File "/var/www/iredadmin/controllers/decorators.py", line 11, in proxyfunc
[Dec 17 14:07:18 2013] [error] return func(self, *args, **kw)
[Dec 17 14:07:18 2013] [error] File "/var/www/iredadmin/controllers/mysql/domain.py", line 133, in GET
[Dec 17 14:07:18 2013] [error] gl = greylist.Greylisting()
[Dec 17 14:07:18 2013] [error] NameError: global name 'greylist' is not defined

How can I define global name  'greylist'  ?
Thanks for your replay.

----

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: 30,768

Re: "internal server error" after upgrade to ver. pro-1.8.0 mysql

Please try below steps to fix it:

- Restart Apache web service.
- Delete all records in SQL table "iredadmin.sessions". It's just temporary session data, it's safe to delete them to force all admins to re-login.

3 Reply by igor

  • igor
  • Member
  • Offline
  • Registered: 2013-12-17
  • Posts: 16

Re: "internal server error" after upgrade to ver. pro-1.8.0 mysql

Thanks your, now it's fine! But i have once more problem : also stopped working link https://xxxx.yyy.zz/iredadmin/system/license with error message "... <urlopen error [Errno 111] Connection refused>". (Server used  setting http_proxy="http://123.456.789:3128/")

Thanks for your replay.

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,768

Re: "internal server error" after upgrade to ver. pro-1.8.0 mysql

Looks like you have http proxy defined in shell variable 'http_proxy', iRedAdmin-Pro uses it automatically.

5 Reply by igor (edited by igor 2013-12-18 15:33:41)

  • igor
  • Member
  • Offline
  • Registered: 2013-12-17
  • Posts: 16

Re: "internal server error" after upgrade to ver. pro-1.8.0 mysql

Yes, of course.
# export
...
declare -x http_proxy="http://XXX.XXX.XXX.XXX:3128/"

This problem decided by setting variable HTTP_PROXY in file  lib/default_settings.py .

Thank you.
This topic may be closed.