Ignore the comment about processes crashing, I didn't pay enough attention to
the log output you gave me.
Can you do the following.
1. Create a fresh Python virtual environment and activate it so it is being
used.
2. Run:
APXS=/usr/local/apache2/bin/apxs pip install mod_wsgi
3. Run:
mod_wsgi-express start-server
4. Access:
http://localhost:8000
Tell me if this works and you see the splash page saying you are running
mod_wsgi.
If you have something already running on port 8000, use:
mod_wsgi-express start-server --port 8888
That is, use --port option to specify another port.
By installing mod_wsgi-express it will confirm whether that separately works
without upsetting your main Apache installation.
If it doesn't work, then I will describe how to use 'truss' to track down the
system call which is giving the invalid argument error. Am guessing it maybe
writev() calls or equivalent.
BTW, do you know if your Apache is using prefork, worker or event MPM. I don't
think Solaris supports events MPM, so am hoping it is worker MPM as that will
make debugging a little easier.
Graham
On 19/03/2015, at 2:33 PM, Graham Dumpleton <[email protected]> wrote:
> Does the main Apache error log, not the VirtualHost error log, contain any
> messages. In particular does it say anything about a segmentation fault?
>
> I can't see how this could occur unless the Apache child worker process
> proxying the request to the mod_wsgi daemon process had crashed.
>
> Did you build this Apache installation yourself from source code or it is a
> binary package from some where?
>
> Graham
>
> On 19/03/2015, at 2:22 PM, Jesus Cea <[email protected]> wrote:
>
>> I just tried to upgrade mod_wsgi from 3.5 to current 4.4.10. Apache
>> 2.4.12, under Solaris 10.
>>
>> Compilation is flawless. I didn't touch apache httpd.conf. Apache works
>> when making non-WSGI requests. But WSGI requests fail leaving this error
>> in the apache logs:
>>
>> """
>> [Thu Mar 19 04:00:58.428157 2015] [wsgi:error] [pid 25705:tid 4]
>> (22)Invalid argument: [client X.X.X.X:36924] mod_wsgi (pid=25705):
>> Unable to send request details to WSGI daemon process 'hs-XXX' on
>> '/usr/local/apache2/logs/wsgi.25691.0.3.sock'.
>> [Thu Mar 19 04:00:58.428382 2015] [wsgi:crit] [pid 25695:tid 13]
>> (70014)End of file found: mod_wsgi (pid=25695): Unable to read WSGI request.
>> """
>>
>> The file accessed is correct:
>>
>> """
>> srwx------ 1 apache root 0 Mar 19 03:14
>> /usr/local/apache2/logs/wsgi.25691.0.3.sock
>> """
>>
>> Checking every upgrade notes from 4.0 I see some very similar solved in
>> 4.1.2 release. I am trying to use 4.4.10.
>>
>> My configuration: (as is from wsgi 3.5)
>>
>> """
>> <VirtualHost *:28443>
>> ServerName hs-XXX.jcea.es
>>
>> SSLEngine on
>> SSLCertificateFile /home/jcea/.SSL/host.cert
>> SSLCertificateKeyFile /home/jcea/.SSL/host.key
>>
>> ErrorLog logs/hs-XXX_error.log
>> CustomLog logs/hs-XXX_access.log combinedSSL
>>
>> WSGIDaemonProcess hs-XXX threads=10 display-name=%{GROUP}
>> python-path=/home/XXX/
>> WSGIProcessGroup hs-XXX
>>
>> WSGIScriptAlias / /home/XXX/wsgi.py
>>
>> <Directory "/home/XXXX">
>> AllowOverride None
>>
>> AuthType Digest
>> AuthName "HS XXX"
>> AuthUserFile /home/XXXX/users
>> Require valid-user
>> </Directory>
>> </VirtualHost>
>> """
>>
>> I am back to 3.5 for now. Help!.
>>
>> --
>> Jesús Cea Avión _/_/ _/_/_/ _/_/_/
>> [email protected] - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/
>> Twitter: @jcea _/_/ _/_/ _/_/_/_/_/
>> jabber / xmpp:[email protected] _/_/ _/_/ _/_/ _/_/ _/_/
>> "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/
>> "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/
>> "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
>>
>> --
>> 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 http://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 http://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.
