1

Topic: ImportError: No module named settings

======== Required information ====
- iRedMail version: iRedMail-0.8.7
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): PGSQL (9.3.5)
- Linux/BSD distribution name and version: Ubuntu 14.04.1 LTS
- Related log if you're reporting an issue: See text below
====

Some time ago I installed iRedMail without any issues and now I wanted to add an email, only to discover iredadmin no longer works.

I have spent the last hours trying to figure it out but seem to be stuck. I'm sure settings must be in the python path but it seems not to be for some reason.

It would be great if someone could help me out with this, thank you very much in advance.

Apache error log:

# cat var/log/apache2/error.log
[Sun Nov 02 18:22:55.263006 2014] [:error] mod_wsgi (pid=26832): Target WSGI script '/usr/share/apache2/iredadmin/iredadmin.py' cannot be loaded as Python module.
[Sun Nov 02 18:22:55.263041 2014] [:error] mod_wsgi (pid=26832): Exception occurred processing WSGI script '/usr/share/apache2/iredadmin/iredadmin.py'.
[Sun Nov 02 18:22:55.263059 2014] [:error] Traceback (most recent call last):
[Sun Nov 02 18:22:55.263075 2014] [:error]   File "/usr/share/apache2/iredadmin/iredadmin.py", line 9, in <module>
[Sun Nov 02 18:22:55.263132 2014] [:error]     from libs import iredbase
[Sun Nov 02 18:22:55.263143 2014] [:error]   File "/usr/share/apache2/iredadmin/libs/iredbase.py", line 18, in <module>
[Sun Nov 02 18:22:55.263206 2014] [:error]     import iredutils
[Sun Nov 02 18:22:55.263217 2014] [:error]   File "/usr/share/apache2/iredadmin/libs/iredutils.py", line 13, in <module>
[Sun Nov 02 18:22:55.263317 2014] [:error]     import settings
[Sun Nov 02 18:22:55.263340 2014] [:error] ImportError: No module named settings

iredadmin folder:

# ls -lah /usr/share/apache2/iredadmin/
total 96K
dr-xr-xr-x  9 iredadmin iredadmin 4.0K Nov  2 18:32 .
drwxr-xr-x  8 root      root      4.0K Sep 17 20:10 ..
-r-xr-xr-x  1 iredadmin iredadmin   49 May 17 04:04 AUTHORS
-r-xr-xr-x  1 iredadmin iredadmin 4.6K May 17 04:04 ChangeLog
dr-xr-xr-x  6 iredadmin iredadmin 4.0K Nov  2 18:15 controllers
dr-xr-xr-x  3 iredadmin iredadmin 4.0K Jun 18 14:41 docs
dr-xr-xr-x 18 iredadmin iredadmin 4.0K Jun 18 14:41 i18n
-r-xr-xr-x  1 iredadmin iredadmin  402 Nov  2 18:15 iredadmin.py
dr-xr-xr-x  6 iredadmin iredadmin 4.0K Nov  2 18:26 libs
-r-xr-xr-x  1 iredadmin iredadmin  18K May 17 04:04 LICENSE
-r-xr-xr-x  1 iredadmin iredadmin  439 May 17 04:04 README
-rwx------  1 iredadmin iredadmin 3.9K Jun 18 14:41 settings.py
-r-xr-xr-x  1 iredadmin iredadmin 4.4K May 17 04:04 settings.py.ldap.sample
-r-xr-xr-x  1 iredadmin iredadmin 3.8K May 17 04:04 settings.py.mysql.sample
-r-xr-xr-x  1 iredadmin iredadmin 3.8K May 17 04:04 settings.py.pgsql.sample
dr-xr-xr-x  4 iredadmin iredadmin 4.0K Jun 18 14:41 static
dr-xr-xr-x  3 iredadmin iredadmin 4.0K Jun 18 14:41 templates
dr-xr-xr-x  2 iredadmin iredadmin 4.0K May 17 04:04 tools

Apache virtual host config:

# cat /etc/apache2/sites-enabled/iRedMail 
<IfModule mod_ssl.c>
  <VirtualHost _default_:443>

    ServerAdmin fabian.barkhau@gmail.com
    ServerName  live01

    DocumentRoot /var/www/html

    # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
    # error, crit, alert, emerg.
    # It is also possible to configure the loglevel for particular
    # modules, e.g.
    #LogLevel info ssl:warn
    LogLevel warn

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    # For most configuration files from conf-available/, which are
    # enabled or disabled at a global level, it is possible to
    # include a line for only one particular virtual host. For example the
    # following line enables the CGI configuration for this host only
    # after it has been globally disabled with "a2disconf".
    #Include conf-available/serve-cgi-bin.conf

    #   SSL Engine Switch:
    #   Enable/Disable SSL for this virtual host.
    SSLEngine on

    #   A self-signed (snakeoil) certificate can be created by installing
    #   the ssl-cert package. See
    #   /usr/share/doc/apache2/README.Debian.gz for more info.
    #   If both key and certificate are stored in the same file, only the
    #   SSLCertificateFile directive is needed.
    #SSLCertificateFile /etc/ssl/certs/iRedMail_CA.pem
    #SSLCertificateKeyFile /etc/ssl/private/iRedMail.key
    SSLCertificateFile /etc/ssl/certs/bitcoin-bounties.com.crt
    SSLCertificateKeyFile /etc/ssl/private/bitcoin-bounties.com.key

    #   Server Certificate Chain:
    #   Point SSLCertificateChainFile at a file containing the
    #   concatenation of PEM encoded CA certificates which form the
    #   certificate chain for the server certificate. Alternatively
    #   the referenced file can be the same as SSLCertificateFile
    #   when the CA certificates are directly appended to the server
    #   certificate for convinience.
    #SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt

    #   Certificate Authority (CA):
    #   Set the CA certificate verification path where to find CA
    #   certificates for client authentication or alternatively one
    #   huge file containing all of them (file must be PEM encoded)
    #   Note: Inside SSLCACertificatePath you need hash symlinks
    #         to point to the certificate files. Use the provided
    #         Makefile to update the hash symlinks after changes.
    #SSLCACertificatePath /etc/ssl/certs/
    #SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt

    #   Certificate Revocation Lists (CRL):
    #   Set the CA revocation path where to find CA CRLs for client
    #   authentication or alternatively one huge file containing all
    #   of them (file must be PEM encoded)
    #   Note: Inside SSLCARevocationPath you need hash symlinks
    #         to point to the certificate files. Use the provided
    #         Makefile to update the hash symlinks after changes.
    #SSLCARevocationPath /etc/apache2/ssl.crl/
    #SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl

    #   Client Authentication (Type):
    #   Client certificate verification type and depth.  Types are
    #   none, optional, require and optional_no_ca.  Depth is a
    #   number which specifies how deeply to verify the certificate
    #   issuer chain before deciding the certificate is not valid.
    #SSLVerifyClient require
    #SSLVerifyDepth  10

    #   SSL Engine Options:
    #   Set various options for the SSL engine.
    #   o FakeBasicAuth:
    #     Translate the client X.509 into a Basic Authorisation.  This means that
    #     the standard Auth/DBMAuth methods can be used for access control.  The
    #     user name is the `one line' version of the client's X.509 certificate.
    #     Note that no password is obtained from the user. Every entry in the user
    #     file needs this password: `xxj31ZMTZzkVA'.
    #   o ExportCertData:
    #     This exports two additional environment variables: SSL_CLIENT_CERT and
    #     SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
    #     server (always existing) and the client (only existing when client
    #     authentication is used). This can be used to import the certificates
    #     into CGI scripts.
    #   o StdEnvVars:
    #     This exports the standard SSL/TLS related `SSL_*' environment variables.
    #     Per default this exportation is switched off for performance reasons,
    #     because the extraction step is an expensive operation and is usually
    #     useless for serving static content. So one usually enables the
    #     exportation for CGI and SSI requests only.
    #   o OptRenegotiate:
    #     This enables optimized SSL connection renegotiation handling when SSL
    #     directives are used in per-directory context.
    #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
    <FilesMatch "\.(cgi|shtml|phtml|php)$">
            SSLOptions +StdEnvVars
    </FilesMatch>
    <Directory /usr/lib/cgi-bin>
            SSLOptions +StdEnvVars
    </Directory>

    #   SSL Protocol Adjustments:
    #   The safe and default but still SSL/TLS standard compliant shutdown
    #   approach is that mod_ssl sends the close notify alert but doesn't wait for
    #   the close notify alert from client. When you need a different shutdown
    #   approach you can use one of the following variables:
    #   o ssl-unclean-shutdown:
    #     This forces an unclean shutdown when the connection is closed, i.e. no
    #     SSL close notify alert is send or allowed to received.  This violates
    #     the SSL/TLS standard but is needed for some brain-dead browsers. Use
    #     this when you receive I/O errors because of the standard approach where
    #     mod_ssl sends the close notify alert.
    #   o ssl-accurate-shutdown:
    #     This forces an accurate shutdown when the connection is closed, i.e. a
    #     SSL close notify alert is send and mod_ssl waits for the close notify
    #     alert of the client. This is 100% SSL/TLS standard compliant, but in
    #     practice often causes hanging connections with brain-dead browsers. Use
    #     this only for browsers where you know that their SSL implementation
    #     works correctly.
    #   Notice: Most problems of broken clients are also related to the HTTP
    #   keep-alive facility, so you usually additionally want to disable
    #   keep-alive for those clients, too. Use variable "nokeepalive" for this.
    #   Similarly, one has to force some clients to use HTTP/1.0 to workaround
    #   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
    #   "force-response-1.0" for this.
    BrowserMatch "MSIE [2-6]" \
            nokeepalive ssl-unclean-shutdown \
            downgrade-1.0 force-response-1.0
    # MSIE 7 and newer should be able to use keepalive
    BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown

    <Directory />
      Options FollowSymLinks
      AllowOverride None
      Require all denied
    </Directory>

    <Directory /usr/share>
      AllowOverride None
      Require all granted
    </Directory>

    <Directory /var/www/>
      Options Indexes FollowSymLinks
      AllowOverride None
      Require all granted
    </Directory>

    # Alias /cluebringer "/usr/share/postfix-cluebringer-webui/webui/"
    Alias /iredadmin/static "/usr/share/apache2/iredadmin/static/"
    WSGIScriptAlias /iredadmin "/usr/share/apache2/iredadmin/iredadmin.py/"
    # Alias /awstats/icon "/usr/share/awstats/icon/"
    # Alias /awstatsicon "/usr/share/awstats/icon/"
    # ScriptAlias /awstats "/usr/lib/cgi-bin/"
    Alias /mail "/usr/share/apache2/roundcubemail/"
    # Alias /phppgadmin "/usr/share/phppgadmin/"

  </VirtualHost>
</IfModule>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

----

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

2

Re: ImportError: No module named settings

Does executing "a2enconf iredadmin" fix it?

3

Re: ImportError: No module named settings

No, I already ran across that and it doesn't help.

# a2enconf iredadmin
Conf iredadmin already enabled

4

Re: ImportError: No module named settings

Does it work without this virtual host (/etc/apache2/sites-enabled/iRedMail)?

5

Re: ImportError: No module named settings

No /etc/apache2/sites-enabled/iRedMail is just the renamed default-ssl.conf that iRedMail generated. Without it nothing works.

6

Re: ImportError: No module named settings

Everything looks just fine, no idea yet.

Is it possible to let me login to your server to debug this?

7

Re: ImportError: No module named settings

I'm afraid not as I do have sensitive information on the server, but I will gladly give you almost any log or information you need.

8

Re: ImportError: No module named settings

Sorry, no clue at all, i don't know what log file i should request. sad

9

Re: ImportError: No module named settings

I will see if I can get you access because this is becoming a problem now, I can't even send/receive emails any more sad

Maybe we can arrange an appointment and can give you access for limited time while I monitor what you do via a shared screen session?

10

Re: ImportError: No module named settings

fbarkhau wrote:

I can't even send/receive emails any more

You must check Postfix log file to see what the problem is.

fbarkhau wrote:

Maybe we can arrange an appointment and can give you access for limited time while I monitor what you do via a shared screen session?

Limited time is ok, i will help fix the iRedAdmin issue.