Thanks for the help. It looks like it was a configuration problem in the WHM interface for configuring Apache. (There isn't a lot of good documentation for this thing). For those who stumble upon this string and have a similar problem, in WHM use Apache Configuration >> Include Editor >> Pre Main Include >> All Versions (if you select a single Apache version like I did, even though it IS the current version, it does not seem to work) ... and then include your 'LoadModule' statement in the text box.
Thanks Graham -- for the original work AND the continued support. On Thursday, December 7, 2017 at 7:43:30 AM UTC-5, Jeff Robertson wrote: > > I used the output of 'mod_wsgi-express module-config' to determine what > to put into the httpd.conf; is that the same as 'mod_wsgi-module-config'? > > I did use the interface to restart Apache, not the command line restart. > You could definitely be right that they are two different processes. > > This "Include Editor" in WHM seems unusual -- I haven't seen a lot written > about it elsewhere in my searching. Based on reading the documentation, it > seems to dynamically generate the Apache code to ensure users don't mess up > the configuration; but I'm not clear if it is "nice to have" vs. "required" > in my server. I'll do some more research on this with my hosting service. > > Thanks > > On Wednesday, December 6, 2017 at 5:34:52 PM UTC-5, Graham Dumpleton wrote: >> >> Just to clarify, when you said: >> >> """ >> Apache configuration statement (I'm using WHM and it is making me use >> Include Editor to configure httpd.conf -- this statement goes into the "Pre >> Main Include" interface.) >> """ >> >> you used that to edit the Apache configuration and inserted into the >> httpd.conf file the output of running 'mod_wsgi-module-config'? >> >> Running that command is not enough, it doesn't edit the 'httpd.conf' file >> for you. >> >> If you are having to edit the config files through an interface, it is >> possible that if you were to run 'httpd' on the command line that it isn't >> using the same files. The WHM my be starting up httpd in a way that it is >> using different configuration files. Are you also restarting Apache on the >> command line, or does WHM provide a web interface for that as well? >> >> Graham >> >> On 6 Dec 2017, at 10:30 PM, Jeff Robertson <[email protected]> wrote: >> >> Trying to work through the installation of mod_wsgi ... >> >> It seems that I'm having trouble getting Apache to load the module. >> >> Some background details: >> >> # httpd -V >> Server version: Apache/2.4.29 (cPanel) >> Server built: Nov 28 2017 15:27:38 >> Server's Module Magic Number: 20120211:68 >> Server loaded: APR 1.5.2, APR-UTIL 1.5.2 >> Compiled using: APR 1.5.2, APR-UTIL 1.5.2 >> Architecture: 64-bit >> Server MPM: >> Server compiled with.... >> -D APR_HAS_SENDFILE >> -D APR_HAS_MMAP >> -D APR_HAVE_IPV6 (IPv4-mapped addresses disabled) >> -D APR_USE_SYSVSEM_SERIALIZE >> -D APR_USE_PTHREAD_SERIALIZE >> -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT >> -D APR_HAS_OTHER_CHILD >> -D AP_HAVE_RELIABLE_PIPED_LOGS >> -D DYNAMIC_MODULE_LIMIT=256 >> -D HTTPD_ROOT="/etc/apache2" >> -D SUEXEC_BIN="/usr/sbin/suexec" >> -D DEFAULT_PIDLOG="/var/run/apache2/httpd.pid" >> -D DEFAULT_SCOREBOARD="logs/apache_runtime_status" >> -D DEFAULT_ERRORLOG="logs/error_log" >> -D AP_TYPES_CONFIG_FILE="conf/mime.types" >> -D SERVER_CONFIG_FILE="conf/httpd.conf" >> >> >> >> >> # httpd -l >> Compiled in modules: >> core.c >> mod_so.c >> http_core.c >> >> >> >> # httpd -M >> Loaded Modules: >> core_module (static) >> so_module (static) >> http_module (static) >> mpm_worker_module (shared) >> cgid_module (shared) >> access_compat_module (shared) >> actions_module (shared) >> alias_module (shared) >> asis_module (shared) >> auth_basic_module (shared) >> authn_core_module (shared) >> authn_file_module (shared) >> authz_core_module (shared) >> authz_groupfile_module (shared) >> authz_host_module (shared) >> authz_user_module (shared) >> autoindex_module (shared) >> cache_module (shared) >> dav_module (shared) >> dav_fs_module (shared) >> dbd_module (shared) >> deflate_module (shared) >> dir_module (shared) >> env_module (shared) >> expires_module (shared) >> filter_module (shared) >> headers_module (shared) >> include_module (shared) >> log_config_module (shared) >> logio_module (shared) >> mime_module (shared) >> negotiation_module (shared) >> proxy_module (shared) >> proxy_fcgi_module (shared) >> proxy_http_module (shared) >> proxy_wstunnel_module (shared) >> reqtimeout_module (shared) >> rewrite_module (shared) >> setenvif_module (shared) >> slotmem_shm_module (shared) >> socache_dbm_module (shared) >> socache_shmcb_module (shared) >> speling_module (shared) >> status_module (shared) >> suexec_module (shared) >> unique_id_module (shared) >> unixd_module (shared) >> userdir_module (shared) >> version_module (shared) >> ssl_module (shared) >> bwlimited_module (shared) >> security2_module (shared) >> suphp_module (shared) >> >> >> >> # mod_wsgi-express module-config >> LoadModule wsgi_module >> "/home/varilead/mydjango/lib/python3.6/site-packages/mod_wsgi-4.5.22-py3.6-linux-x86_64.egg/mod_wsgi/server/ >> mod_wsgi-py36.cpython-36m-x86_64-linux-gnu.so" >> WSGIPythonHome "/home/varilead/mydjango" >> >> >> >> Apache configuration statement (I'm using WHM and it is making me use >> Include Editor to configure httpd.conf -- this statement goes into the "Pre >> Main Include" interface.) >> >> LoadModule wsgi_module >> "/home/varilead/mydjango/lib/python3.6/site-packages/mod_wsgi-4.5.22-py3.6-linux-x86_64.egg/mod_wsgi/server/ >> mod_wsgi-py36.cpython-36m-x86_64-linux-gnu.so" >> WSGIPythonHome "/home/varilead/mydjango" >> >> I have saved the configuration above and restarted Apache; I don't get >> any Apache errors at the restart. >> >> **Another background datapoint: I have python 2.7 loaded by default on my >> server; but I have python 3.6 loaded as well, and will be wanting to use >> that as a virtualenv when I run my project. Is there potentially come >> conflict with that scenaio? Are there other datapoints I can share that >> will help diagnose? >> >> # ldd mod_wsgi-py36.cpython-36m-x86_64-linux-gnu.so >> linux-vdso.so.1 => (0x00007ffe20e00000) >> libpython3.6m.so.1.0 => /usr/local/lib/libpython3.6m.so.1.0 ( >> 0x00007f21236d8000) >> libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f21234b8000) >> libc.so.6 => /lib64/libc.so.6 (0x00007f2123120000) >> libdl.so.2 => /lib64/libdl.so.2 (0x00007f2122f18000) >> libutil.so.1 => /lib64/libutil.so.1 (0x00007f2122d10000) >> librt.so.1 => /lib64/librt.so.1 (0x00007f2122b08000) >> libm.so.6 => /lib64/libm.so.6 (0x00007f2122880000) >> /lib64/ld-linux-x86-64.so.2 (0x00007f2123e28000) >> >> >> When I re-run "httpd - m", I don't see wsgi_module in the list. What >> other indications should I be looking for to know if mod_wsgi was >> successfully loaded? >> >> Any help? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "modwsgi" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/modwsgi. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
