EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #07879

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] Apache crashes with a segmentation fault

We experienced this issue running EPrints on Ubuntu 18.04 and we "resolved" it by switching to mpm_prefork, but I'd prefer to understand the cause of the crashes (which do happen sometimes still) and the option to run EPrints under mpm_event.  I don't think that expat is the issue, since we're not running any python scripts on that server.  LibXML is a different story though, as EPrints does use that.   

We have the following:
ldconfig -p | grep -i libxml

        libxml2.so.2 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libxml2.so.2
        libxml2.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libxml2.so
        libxmlsec1.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libxmlsec1.so.1
        libxmlsec1-openssl.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libxmlsec1-openssl.so.1

But EPrints is reporting that it is using this:
	XML::LibXML 2.0128 /usr/lib/x86_64-linux-gnu/perl5/5.26/XML/LibXML.pm

Does that mean that the LibXML being used by EPrints on our server is a local installation component rather than a system one?   I suppose the broader question is: what is the best practice; which LibXML library should be used by EPrints on Ubuntu 18.04?  

Tomasz





-----Original Message-----
From: eprints-tech-bounces@ecs.soton.ac.uk <eprints-tech-bounces@ecs.soton.ac.uk> On Behalf Of Yuri via Eprints-tech
Sent: May 17, 2019 6:55 AM
To: eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] Apache crashes with a segmentation fault

This mayne means you've two expat or libxml, one from the system and another from a local installation? If you use only the system version, you shouldn't have this problem.

This can have some info:

https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmodwsgi.readthedocs.io%2Fen%2Fdevelop%2Fuser-guides%2Fissues-with-expat-library.html&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Ce15d06e522664ce30ee508d6edec98e4%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=c8Xbg4FvODdRtR0uI8SRTG2ZY01sSdk3bNF2mEpsmbQ%3D&amp;reserved=0

but basically remove any self compiled component and use system one, or recompile them again.

Il 17/05/19 11:51, Janusz S. Bień via Eprints-tech ha scritto:
> In its 10th year of being in use, our digital library (harvested in 
> particular by Europeana) was hit by the problem causes by the 
> automatic upgrade of Debian stable. It may be the very problem 
> described at
>
>           
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.
> eprints.org%2Fw%2FTroubleshooting&amp;data=01%7C01%7Ceprints-tech%40ec
> s.soton.ac.uk%7C117a337937934fd9619008d6dab612c6%7C4a5378f929f44d3ebe8
> 9669d03ada9d8%7C0&amp;sdata=HdlXs8ZKVDvutuKvBpPFLdmDE14JTKm%2FttB%2FPK
> op%2FHA%3D&amp;reserved=0

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Ce15d06e522664ce30ee508d6edec98e4%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=Y50h5CNxrgJAMQAJGrz2%2B%2FhcvnW5RL0%2FQRoaTG4FRe8%3D&amp;reserved=0
*** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.eprints.org%2F&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Ce15d06e522664ce30ee508d6edec98e4%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=0VSkWhxgPwmkl%2BgFo86YoLZ8FlRh84n2974%2FF9UyipA%3D&amp;reserved=0
*** EPrints developers Forum: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fforum.eprints.org%2F&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Ce15d06e522664ce30ee508d6edec98e4%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=9m6j9TCEV6a0ovtYa654STNsPv4vhoUIYr5BvQVaSG4%3D&amp;reserved=0