EPrints Technical Mailing List Archive

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

Message: #08602

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

Re: [EP-tech] Upgrading to 3.4.3 - an experience

Hi Ravi,

I have looked into this and determined that if there is no structural changes to the database between versions, then additional fields are not added to user, eprint, etc. data objects through "epadmin upgrade <ARCHIVE_NAME>" and you would also need run "epadmin update <ARCHIVE_NAME>" to do this.  Therefore, I have modified the upgrade call to add fields to data objects when no structural changes need to made to upgrade to the new database version, which would normally do this field adding whilst making the structural changes.

Here is the GitHub issue that relates to this bug (and fix):

https://github.com/eprints/eprints3.4/issues/148

Obviously, this will not help until 3.4.4 is released, so upgrades to 3.4.3 will still need "epadmin update ..." to be run.  I will see if there is somewhere appropriate on the wiki to make it clear that this is required as part of the upgrade process.

Regards

David Newman

On 10/05/2021 11:59, David R Newman wrote:

Hi Ravi,

I will look into why the upgrade did not do an update as well.  The reason why you won't have been able to login is that various new fields have been added to the user data object / record.  These are mainly to provide better security to temporarily lock accounts when there have been too many failed password attempts in a set period of time.

I would generally say that EPrints from APT or YUM/DNF package management is generally not advised for production repositories.  Packages are more intended for installing EPrints for testing and evaluation purposes.  If you have a fairly vanilla repository updates are unlikely to cause any significant problems but the more bespoke your repository the more likely upgrading through the package manager is to cause you repository to fail.  This is especially the case if parts of the core codebase have been modified on your installation.  Although the package manager should warn you, if you choose not to use the latest version of a file being installed, it is likely this will leave you with an inconsistent version of EPrints that cannot be run.

Regards

David Newman

On 10/05/2021 11:41, Ravi M via Eprints-tech wrote:
CAUTION: This e-mail originated outside the University of Southampton.
Hello,

Just wanted to share my experience upgrading from version 3.4.2 to 3.4.3, in case it's useful to anyone.

I run EPrints on an Ubuntu server, and http://deb.eprints-hosting.org/3.4/stable/ is in my PPA. Over the weekend I did the usual update/upgrade tasks via the command line, and I noticed that there was a new version of EPrints. I installed it and ran '/bin/epadmin upgrade <repository>' as advised at the end of the install. Everything seemed okay on the command line (unless I overlooked some piece of advice), but I couldn't sign into the EPrints site with any of my accounts -- I got 'Incorrect username or password' every time. Thankfully '/bin/epadmin update <repository>' sorted things out.

Best wishes,
Ravi

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/

Virus-free. www.avg.com