I didn't read the whole articles before and got misunderstanding on the
things about 'reload code in daemon mode'.
I thought the daemon would detect the changes on any code in the project,
but it ONLY detects the changes on the application script, silly am I. lol
sorry for wasting your time
> On 20 Feb 2019, at 11:23 am, 阿尼 wrote:
>
> Ooops.
> Since I did not install the mod_wsgi through pip, so I guess I can only use
> the second method.
Whether you use system package for mod_wsgi, configure/make/make install method
from source code, or pip install method should make no
Ooops.
Since I did not install the mod_wsgi through pip, so I guess I can only use
the second method.
And the result is still *EMBEDDED MODE*.
I did think of the chance that the code was wrong, but no matter the it is
wrong or not, I have to restart the server every time manually.
Graham
Obvious really. :-)
The code:
if not os.environ.get('mod_wsgi.process_group'):
output = 'EMBEDDED MODE'
else:
output = 'DAEMON MODE'
is wrong. It should be either:
import mod_wsgi
if not mod_wsgi.process_group:
output = 'EMBEDDED MODE'
else:
output = 'DAEMON MODE'
or:
def
Okay.
I did not get errors when I restart Apache after adding *WSGIRestrictEmbedded
On.*
Apache failed after I add an invalid line in the configuration.
I also changed the LogLevel to info but it seems to be normal, unless these
messages are related:
[Fri Feb 15 10:22:45.683121 2019]
When you added:
WSGIRestrictEmbedded On
and restarted Apache, did you then get errors?
If that directive is in the correct place, it cannot use embedded mode. If it
still is, it suggests the configuration isn't even been run.
Suggest added some invalid configuration at same place and
