Community Forums

1. 

   eskargot
   Member
   Posted 9 years ago

   I'm trying to run mediadrop in a apache server with mod_wsgi and I have this error sentence:
   
[Mon Jun 02 17:56:39 2014] [notice] Apache/2.2.15 (Unix) DAV/2 mod_fcgid/2.3.9 mod_python/3.3.1 Python/2.6.6 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips mod_wsgi/3.2 configured -- resuming normal operations
[Mon Jun 02 17:56:54 2014] [error] [client 85.56.143.147] mod_wsgi (pid=6502): Target WSGI script '/xxx/mediadrop.wsgi' cannot be loaded as Python module.
[Mon Jun 02 17:56:54 2014] [error] [client 85.56.143.147] mod_wsgi (pid=6502): Exception occurred processing WSGI script '/xxx/mediadrop.wsgi'.
[Mon Jun 02 17:56:54 2014] [error] [client 85.56.143.147] Traceback (most recent call last):
[Mon Jun 02 17:56:54 2014] [error] [client 85.56.143.147] File "/xxx/mediadrop.wsgi", line 15, in <module>
[Mon Jun 02 17:56:54 2014] [error] [client 85.56.143.147] from paste.script.util.logging_config import fileConfig
[Mon Jun 02 17:56:54 2014] [error] [client 85.56.143.147] ImportError: No module named script.util.logging_config
[Mon Jun 02 17:57:38 2014] [notice] caught SIGTERM, shutting down


   Someone can help me?
2. 

   infernose@gmail.com
   Member
   Posted 9 years ago

   I'm having the similar error with WSGI deployment in centOS5.

   my error as caught by httpd logs :
   [Fri Jun 13 02:53:20 2014] [notice] SELinux policy enabled; httpd running as context root:system_r:httpd_t:s0
   [Fri Jun 13 02:53:20 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
   [Fri Jun 13 02:53:20 2014] [notice] Digest: generating secret for digest authentication ...
   [Fri Jun 13 02:53:20 2014] [notice] Digest: done
   [Fri Jun 13 02:53:20 2014] [notice] Apache/2.2.3 (CentOS) configured -- resuming normal operations
   [Fri Jun 13 02:53:23 2014] [error] [client 175.156.116.27] mod_wsgi (pid=24952): Target WSGI script '/var/www/mediadrop.wsgi' cannot be loaded as Python module.
   [Fri Jun 13 02:53:23 2014] [error] [client 175.156.116.27] mod_wsgi (pid=24952): Exception occurred processing WSGI script '/var/www/mediadrop.wsgi'.
   [Fri Jun 13 02:53:23 2014] [error] [client 175.156.116.27] Traceback (most recent call last):
   [Fri Jun 13 02:53:23 2014] [error] [client 175.156.116.27] File "/var/www/mediadrop.wsgi", line 12, in ?
   [Fri Jun 13 02:53:23 2014] [error] [client 175.156.116.27] from paste.script.util.logging_config import fileConfig
   [Fri Jun 13 02:53:23 2014] [error] [client 175.156.116.27] ImportError: No module named paste.script.util.logging_config

   I have already tried the suggestion from http://mediadrop.net/community/topic/proble-to-work-with-apache-mod_wsgi#post-202409 but still no joy.

   running in development mode by "paster serve --reload deployment.ini" works fine though.

   on a side note, 1 thing I have noticed, the rename of mediacore to mediadrop seems to be a botched effort, there are conflicting mentions of either name both in installation files and guide, leading to unnecessary confusion during installation.
3. 

   Todd_H
   Member
   Posted 9 years ago

   Has anyone figured this out yet? I'm facing the exact same issue

RSS feed for this topic

Reply

You must log in to post.