Can you set LogLevel to debug and also add:
WSGIVerboseDebugging On
Capture log output from before request, until after failed request.
Graham
> On 14 Aug 2018, at 10:42 pm, Hemant Chaudhary
> <[email protected]> wrote:
>
> Hi,
> By mistake I pasted the old logs. New error log is like this :
> [Tue Aug 14 12:30:06.016383 2018] [wsgi:info] [pid 654311463:tid
> 577193508084252676] mod_wsgi (pid=654311463): Create interpreter
> 'www.example.com:8079|/wsgi/first.py'.
> [Tue Aug 14 12:30:06.024527 2018] [wsgi:info] [pid 654311463:tid
> 577193508084252676] [remote 15.213.82.149:61543
> <http://15.213.82.149:61543/>] mod_wsgi (pid=654311463, process='example.com
> <http://example.com/>', application='www.example.com:8079|/wsgi/first.py'):
> Loading WSGI script
> '/home/hemant_super/practi/web4/apache-2.4.29/wsgi/first.py'.
> [Tue Aug 14 12:30:16.471707 2018] [wsgi:error] [pid 1325400115:tid
> 577187392050757636] (4022)Invalid function argument: [client
> 15.213.82.149:61550 <http://15.213.82.149:61550/>] mod_wsgi (pid=1325400115):
> Unable to send request details to WSGI daemon process 'example.com
> <http://example.com/>' on '/tmp/wsgi.1879048236.0.1.sock'.
>
> This is an NonStop HPE Operating System and PID for processes are like this
> only. So no issues with PID.
>
> One more interesting outcome is that, now when I am browsing first.py for the
> first time then able to get the page. But after that it is giving the error
> invalid function.
> Please share your though.
> Hemant
>
>
>
> On Tue, Aug 14, 2018 at 4:54 PM, Graham Dumpleton <[email protected]
> <mailto:[email protected]>> wrote:
> Still more inclined to think is just where socket is, being on NFS server.
> The process ID size I can't see that would cause an issue when looking at
> code. UNIX sockets though, don't sometimes work in NFS mounted file systems
> from memory.
>
>
>> On 14 Aug 2018, at 9:12 pm, Graham Dumpleton <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> I would say the issue may be related to the size of the pids.
>>
>> A process ID would normally be less than 2^22. Your system has larger values
>> for some reason. The value 1912602637 is greater than 2^31 and so would be
>> regarded as negative value in 32 bit integer. This may screw up some stuff.
>>
>> So definitely want to know why you have such large process IDs.
>>
>> Graham
>>
>>> On 14 Aug 2018, at 9:03 pm, Graham Dumpleton <[email protected]
>>> <mailto:[email protected]>> wrote:
>>>
>>> BTW, what operating system is this?
>>>
>>> It is very strange to see such large process ID numbers such as 1325400071
>>> and 1912602637.
>>>
>>> From:
>>>
>>> *
>>> https://unix.stackexchange.com/questions/16883/what-is-the-maximum-value-of-the-process-id
>>>
>>> <https://unix.stackexchange.com/questions/16883/what-is-the-maximum-value-of-the-process-id>
>>>
>>> /proc/sys/kernel/pid_max
>>> This file (new in Linux 2.5) specifies the value at which PIDs wrap around
>>> (i.e., the value in this file is one greater than the maximum PID). The
>>> default value for this file, 32768, results in the same range of PIDs as
>>> on earlier kernels. On 32-bit platfroms, 32768 is the maximum value for
>>> pid_max. On 64-bit systems, pid_max can be set to any value up to 2^22
>>> (PID_MAX_LIMIT, approximately 4 million).
>>>
>>> Those process IDs are way above 4 million value even of a 64 bit system.
>>>
>>> Graham
>>>
>>>> On 14 Aug 2018, at 8:52 pm, Graham Dumpleton <[email protected]
>>>> <mailto:[email protected]>> wrote:
>>>>
>>>> If you have set WSGISocketPrefix and properly re-started Apache, it should
>>>> not be showing the path:
>>>>
>>>>
>>>> /home/hemant_super/practi/web4/apache-2.4.29/logs/wsgi.2030043146.0.1.sock
>>>>
>>>> but should be showing:
>>>>
>>>> /tmp/wsgi.2030043146.0.1.sock
>>>>
>>>> Ensure you have stopped and started Apache after making the change.
>>>>
>>>> Graham
>>>>
>>>>> On 14 Aug 2018, at 8:50 pm, Hemant Chaudhary
>>>>> <[email protected] <mailto:[email protected]>>
>>>>> wrote:
>>>>>
>>>>> No Still no working :
>>>>> Error_log :
>>>>> [Tue Aug 14 09:21:13.966947 2018] [wsgi:info] [pid 1325400071:tid
>>>>> 577203541127856132] [remote 15.213.82.149:58102
>>>>> <http://15.213.82.149:58102/>] mod_wsgi (pid=1325400071,
>>>>> process='example.com <http://example.com/>',
>>>>> application='www.example.com:8079
>>>>> <http://www.example.com:8079/>|/wsgi/first.py'): Loading WSGI script
>>>>> '/home/hemant_super/practi/web4/apache-2.4.29/wsgi/first.py'.
>>>>> [Tue Aug 14 09:23:06.846906 2018] [wsgi:error] [pid 1912602637:tid
>>>>> 577197012777500676] (4022)Invalid function argument: [client
>>>>> 15.213.82.149:58117 <http://15.213.82.149:58117/>] mod_wsgi
>>>>> (pid=1912602637): Unable to send request details to WSGI daemon process
>>>>> 'example.com <http://example.com/>' on
>>>>> '/home/hemant_super/practi/web4/apache-2.4.29/logs/wsgi.2030043146.0.1.sock'.
>>>>>
>>>>> This is my configuration :
>>>>> LoadModule wsgi_module modules/mod_wsgi.so
>>>>> Listen 8079
>>>>> WSGISocketPrefix /tmp/wsgi
>>>>> <VirtualHost 15.213.91.33:8079 <http://15.213.91.33:8079/>>
>>>>>
>>>>> ServerName www.example.com <http://www.example.com/>
>>>>> ServerAlias example.com <http://example.com/>
>>>>> ServerAdmin [email protected] <mailto:[email protected]>
>>>>> LogLevel info
>>>>> ErrorLog "logs/error_wsgi_log"
>>>>> LogFormat "%P %p %h %l %u %t \"%r\" %>s %b" common
>>>>> CustomLog "logs/access_wsgi_log" common
>>>>>
>>>>> WSGIScriptAlias /wsgi
>>>>> "/home/hemant_super/practi/web4/apache-2.4.29/wsgi/"
>>>>>
>>>>> # WSGISocketPrefix /tmp/wsgi
>>>>> WSGIDaemonProcess example.com <http://example.com/> processes=1
>>>>> threads=15 display-name="wsgi_hem"
>>>>> WSGIProcessGroup example.com <http://example.com/>
>>>>>
>>>>>
>>>>> <Directory '/home/hemant_super/practi/web4/apache-2.4.29/wsgi/'>
>>>>> AddHandler wsgi-script .wsgi .py .pl
>>>>> AllowOverride All
>>>>> Options +Indexes +FollowSymLinks +ExecCGI
>>>>> Require all granted
>>>>> </Directory>
>>>>>
>>>>> </VirtualHost>
>>>>>
>>>>> Do I need to change anything in conf. But the same script and conf works
>>>>> fine with embeded wsgi in apache.
>>>>>
>>>>> Thanks
>>>>> Hemant
>>>>>
>>>>> On Tue, Aug 14, 2018 at 3:25 PM, Graham Dumpleton
>>>>> <[email protected] <mailto:[email protected]>> wrote:
>>>>> Try setting:
>>>>>
>>>>> WSGISocketPrefix /tmp/wsgi
>>>>>
>>>>> as a test to see if moving the socket out of the NFS partition helps.
>>>>>
>>>>> Graham
>>>>>
>>>>>
>>>>>> On 14 Aug 2018, at 7:53 pm, Hemant Chaudhary
>>>>>> <[email protected] <mailto:[email protected]>>
>>>>>> wrote:
>>>>>>
>>>>>> Yes it is on NFS server
>>>>>>
>>>>>> On Aug 14, 2018 3:11 PM, "Graham Dumpleton" <[email protected]
>>>>>> <mailto:[email protected]>> wrote:
>>>>>> Quick question. Is your home directory on an NFS server?
>>>>>>
>>>>>> Will respond properly later with things to try.
>>>>>>
>>>>>> Graham
>>>>>>
>>>>>>> On 14 Aug 2018, at 7:30 pm, Hemant Chaudhary
>>>>>>> <[email protected]
>>>>>>> <mailto:[email protected]>> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have setup where embeded wsgi is working while daemon is not working
>>>>>>> and giving the following error
>>>>>>> "
>>>>>>> [Tue Aug 14 09:20:55.990713 2018] [wsgi:info] [pid 1325400071:tid
>>>>>>> 7857357344764657668] mod_wsgi (pid=1325400071): Attach interpreter ''.
>>>>>>> [Tue Aug 14 09:21:13.956064 2018] [wsgi:info] [pid 1325400071:tid
>>>>>>> 577203541127856132] mod_wsgi (pid=1325400071): Create interpreter
>>>>>>> 'www.example.com:8079 <http://www.example.com:8079/>|/wsgi/first.py'.
>>>>>>> [Tue Aug 14 09:21:13.966947 2018] [wsgi:info] [pid 1325400071:tid
>>>>>>> 577203541127856132] [remote 15.213.82.149:58102
>>>>>>> <http://15.213.82.149:58102/>] mod_wsgi (pid=1325400071,
>>>>>>> process='example.com <http://example.com/>',
>>>>>>> application='www.example.com:8079
>>>>>>> <http://www.example.com:8079/>|/wsgi/first.py'): Loading WSGI script
>>>>>>> '/home/hemant_super/practi/web4/apache-2.4.29/wsgi/first.py'.
>>>>>>> [Tue Aug 14 09:23:06.846906 2018] [wsgi:error] [pid 1912602637:tid
>>>>>>> 577197012777500676] (4022)Invalid function argument: [client
>>>>>>> 15.213.82.149:58117 <http://15.213.82.149:58117/>] mod_wsgi
>>>>>>> (pid=1912602637): Unable to send request details to WSGI daemon process
>>>>>>> 'example.com <http://example.com/>' on
>>>>>>> '/home/hemant_super/practi/web4/apache-2.4.29/logs/wsgi.2030043146.0.1.sock'."
>>>>>>>
>>>>>>> "
>>>>>>> For daemon I have added following lines in configuration :
>>>>>>> WSGIDaemonProcess example.com <http://example.com/> processes=1
>>>>>>> threads=15 display-name="wsgi_hem"
>>>>>>> WSGIProcessGroup example.com <http://example.com/>
>>>>>>>
>>>>>>> Log for working embeded wsgi is :
>>>>>>> " [Tue Aug 14 06:18:52.707764 2018] [wsgi:info] [pid 503316532:tid
>>>>>>> 577196600460640260] [client 15.213.82.149:57719
>>>>>>> <http://15.213.82.149:57719/>] mod_wsgi (pid=503316532, process='',
>>>>>>> application='www.example.com:8079
>>>>>>> <http://www.example.com:8079/>|/wsgi/first.py'): Loading WSGI script
>>>>>>> '/home/hemant_super/practi/web4/apache-2.4.29/wsgi/first.py'. "
>>>>>>>
>>>>>>> Please help to know where am I going wrong ?
>>>>>>>
>>>>>>> Thanks
>>>>>>> Hemant
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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]
>>>>>>> <mailto:[email protected]>.
>>>>>>> To post to this group, send email to [email protected]
>>>>>>> <mailto:[email protected]>.
>>>>>>> Visit this group at https://groups.google.com/group/modwsgi
>>>>>>> <https://groups.google.com/group/modwsgi>.
>>>>>>> For more options, visit https://groups.google.com/d/optout
>>>>>>> <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]
>>>>>> <mailto:[email protected]>.
>>>>>> To post to this group, send email to [email protected]
>>>>>> <mailto:[email protected]>.
>>>>>> Visit this group at https://groups.google.com/group/modwsgi
>>>>>> <https://groups.google.com/group/modwsgi>.
>>>>>> For more options, visit https://groups.google.com/d/optout
>>>>>> <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]
>>>>>> <mailto:[email protected]>.
>>>>>> To post to this group, send email to [email protected]
>>>>>> <mailto:[email protected]>.
>>>>>> Visit this group at https://groups.google.com/group/modwsgi
>>>>>> <https://groups.google.com/group/modwsgi>.
>>>>>> For more options, visit https://groups.google.com/d/optout
>>>>>> <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]
>>>>> <mailto:[email protected]>.
>>>>> To post to this group, send email to [email protected]
>>>>> <mailto:[email protected]>.
>>>>> Visit this group at https://groups.google.com/group/modwsgi
>>>>> <https://groups.google.com/group/modwsgi>.
>>>>> For more options, visit https://groups.google.com/d/optout
>>>>> <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]
>>>>> <mailto:[email protected]>.
>>>>> To post to this group, send email to [email protected]
>>>>> <mailto:[email protected]>.
>>>>> Visit this group at https://groups.google.com/group/modwsgi
>>>>> <https://groups.google.com/group/modwsgi>.
>>>>> For more options, visit https://groups.google.com/d/optout
>>>>> <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]
> <mailto:[email protected]>.
> To post to this group, send email to [email protected]
> <mailto:[email protected]>.
> Visit this group at https://groups.google.com/group/modwsgi
> <https://groups.google.com/group/modwsgi>.
> For more options, visit https://groups.google.com/d/optout
> <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]
> <mailto:[email protected]>.
> To post to this group, send email to [email protected]
> <mailto:[email protected]>.
> Visit this group at https://groups.google.com/group/modwsgi
> <https://groups.google.com/group/modwsgi>.
> For more options, visit https://groups.google.com/d/optout
> <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.
