EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #07976
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] Ubuntu and EPrints Version Upgrade
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>, "James Kerwin" <jkerwin2101@gmail.com>
- Subject: Re: [EP-tech] Ubuntu and EPrints Version Upgrade
- From: "Newman D.R." <drn@ecs.soton.ac.uk>
- Date: Tue, 24 Sep 2019 08:50:27 +0000
Hi James, I have installed (but not upgraded to) EPrints 3.4 on both Ubuntu 16.04 and 18.04 and they both install without major issue. Although 18.04 does have the database issue where you need to create a user that has privileges to allow the epadmin to create a new or recreate the existing database with a user that has permissions to manage it. One thing I noted with an install shortly after the release of 18.04 was that it installed the multi-threaded rather than single-threaded (prefork) module for Apache. This meant that Apache had a tendency to seg fault but I have done some installs more recently and this no longer seems to be an issue. However, the libxml-libxslt-perl package have been removed from the eprints DEB package list of dependencies, as this is what led to the seg faults when running Apache in MPM event mode. libxml-libxslt-perl is only needed if you have import/export modules that rely on XSLT to do transformations. I do not think EPrints 3.4 currently has any of these by default. Regarding EPrints 3.4, if you install the latest version (3.4.1) there are a couple of snags that have been fixed since April 5th (see [1]). The guide for upgrading from 3.3.12 to 3.4 is quite detailed [2]. This should be suitable for later versions of 3.3 as well. With any upgrade/migration I would advise doing the install (of the upgraded system on a new server) and an initial migration of data to allow users to test for a period before doing a freeze (disable login, logout out users (truncate loginticket table) and stop indexer) before dumping out the database, rsyncing across the archive's document directory and then reimporting the database on the new server, as a final migration before switching over DNS to point at this new server. I have done a number of upgrade of 3.3 to 3.4 although mostly if not exclusively on CentOS 7. However, I am also quite familiar with Ubuntu and translating things been the two OS. So if you have any issues, then let me know (direct email) and I will see if I can help. Regards David Newman [1] https://github.com/eprints/eprints3.4/commits/master [2]
https://wiki.eprints.org/w/Upgrading_3.3.12%2B_to_3.4 On 23/09/2019 12:25, James Kerwin via Eprints-tech wrote:
|
- References:
- [EP-tech] Ubuntu and EPrints Version Upgrade
- From: James Kerwin <jkerwin2101@gmail.com>
- [EP-tech] Ubuntu and EPrints Version Upgrade
- Prev by Date: Re: [EP-tech] Advanced Search: Appearance of boolean fields
- Next by Date: Re: [EP-tech] Advanced Search: Appearance of boolean fields
- Previous by thread: [EP-tech] EPrints/CRIS
- Next by thread: [EP-tech] DOI handling in orcid_support_advance
- Index(es):