Here is the output. 
Note: I have removed the 'Permission denied' lines

/usr/lib64/python2.7/site-packages/libxml2mod.so
/usr/lib64/libxml2.so.2
/usr/lib64/libxml2.so.2.9.1

Thanks & regards,
Sujaikumar

On Monday, April 9, 2018 at 8:56:58 AM UTC+5:30, Graham Dumpleton wrote:
>
> Sorry, one more thing.
>
> Can you run:
>
>     find / -name 'libxml2*so*'
>
> Graham
>
> On 9 Apr 2018, at 1:21 pm, Graham Dumpleton <graham.d...@gmail.com 
> <javascript:>> wrote:
>
> And on CentOS the package is likely called libxml2-devel.
>
> Graham
>
> On 9 Apr 2018, at 1:19 pm, Graham Dumpleton <graham.d...@gmail.com 
> <javascript:>> wrote:
>
>
> Today, I'm planning to get libxml2.so.2.9.8 into /usr/lib64 location 
> (after removing existing libxml2.so.2.9.1).
>
> I'm still wondering how the standalone django server picks 2.9.8 version 
> whereas the apache/mod_wsgi picks 2.9.1.
>
>
> I would strongly recommend against fiddling around with shared libraries 
> in /usr/lib64. You could break a lot more than just this.
>
> Where are you intending to get libxml2.so.2.9.8 from?
>
> Graham
>
> Thanks & regards,
> Sujaikumar
>
>
> On Monday, April 9, 2018 at 8:06:57 AM UTC+5:30, Graham Dumpleton wrote:
>>
>> Are you sure the libxm2-dev package on your system is up to date?
>>
>> Can you find the lxml .so file in the Python installation/virtual 
>> environment and run 'ldd' on it to see where it is finding the XML shared 
>> library?
>>
>> Graham
>>
>> On 9 Apr 2018, at 12:23 pm, Sujai Kumar <sujai....@gmail.com> wrote:
>>
>> I have compiled Python 3.6.3 from sources.
>>
>> Thanks & regards,
>> Sujaikumar
>>
>> On Mon 9 Apr, 2018, 5:44 AM Graham Dumpleton, <graham.d...@gmail.com> 
>> wrote:
>>
>>> Are you using system Python package, or have you installed a separate 
>>> Python package, eg., Anaconda Python, or self compiled from source code?
>>>
>>> Graham
>>>
>>> On 8 Apr 2018, at 10:14 pm, Sujai Kumar <sujai....@gmail.com> wrote:
>>>
>>> Hello Sir,
>>>
>>> I'm facing a problem with mod_wsgi/lxml configuration. I looked up into 
>>> some of the stackoverflow posts and understood that the issue could be with 
>>> Library versions.
>>>
>>> etree.tostring() removes characters between '<' and '>' on 
>>> Apache/mod_wsgi where as the plain Django server works just fine.
>>>
>>> *Running standalone Django server (Works Fine)*
>>> {"LXML_VERSION": [4, 2, 1, 0], "*LIBXML_VERSION": [2, 9, 8]*, 
>>> "LIBXML_COMPILED_VERSION": [2, 9, 8], "LIBXSLT_VERSION": [1, 1, 32], 
>>> "LIBXSLT_COMPILED_VERSION": [1, 1, 32]}
>>>
>>> *Running Django over mod_wsgi on Apache*
>>> {"LXML_VERSION": [4, 2, 1, 0], "*LIBXML_VERSION": [2, 9, 1]*, 
>>> "LIBXML_COMPILED_VERSION": [2, 9, 8], "LIBXSLT_VERSION": [1, 1, 32], 
>>> "LIBXSLT_COMPILED_VERSION": [1, 1, 32]}
>>>
>>> I confirmed that the version of LIBXML_VERSION are different between 
>>> standalone and mod_wsgi django server.
>>>
>>> sfmgr@lelnxweb5014:/data/sfdev/mod_wsgi-4.6.4> ls -lart 
>>> /usr/lib64/libxml2.so.2*
>>> -rwxr-xr-x 1 root root 1509408 Jun  6  2016 
>>> */usr/lib64/libxml2.so.2.9.1*
>>> lrwxrwxrwx 1 root root      16 Aug 15  2016 /usr/lib64/libxml2.so.2 -> 
>>> libxml2.so.2.9.1
>>>
>>>
>>> *Question?* 
>>> How do I get the LIBXML_VERSION updated to 2.9.8? Are you saying that 
>>> the system package should be updated? I'm wondering how the LXML_VERSION 
>>> for standalone server is picking up 2.9.8 even though the system only 
>>> contains 2.9.1 version.
>>>
>>> Kindly help in this regard. Thanks for your help in advance.
>>>
>>> Thanks & regards,
>>> Sujaikumar
>>>
>>> -- 
>>> 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 modwsgi+u...@googlegroups.com.
>>> To post to this group, send email to mod...@googlegroups.com.
>>> 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 modwsgi+u...@googlegroups.com.
>>> To post to this group, send email to mod...@googlegroups.com.
>>> 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 modwsgi+u...@googlegroups.com.
>> To post to this group, send email to mod...@googlegroups.com.
>> 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 modwsgi+u...@googlegroups.com <javascript:>.
> To post to this group, send email to mod...@googlegroups.com <javascript:>
> .
> 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 modwsgi+unsubscr...@googlegroups.com.
To post to this group, send email to modwsgi@googlegroups.com.
Visit this group at https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.

Reply via email to