EPrints Technical Mailing List Archive

Message: #09363

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

Re: [EP-tech] Change of EPrints machine name

CAUTION: This e-mail originated outside the University of Southampton.

David,

 

On my machine, I also needed to issue the following command as root, to enable the bin/generate_* commands to work…

                    cpan Unicode::String

Thanks for your spot on assistance.

 

Will attempt the 3.4.1 to 3.4.5 migration next week.

 

-Tom

 

From: David R Newman <drn@ecs.soton.ac.uk>
Sent: Friday, August 4, 2023 12:49 PM
To: eprints-tech@ecs.soton.ac.uk; Adams, Thomas <tadams@cshl.edu>
Subject: Re: [EP-tech] Change of EPrints machine name

 

Hi Tom,

The main place that the hostname (e.g. repository, newrepository, etc.) is set is in

EPRINTS_PATH/archives/ARCHIVE_ID/cfg/cfg.d/10_core.pl

However, once you have done this you should run the following commands to regenerate things and clear caches:

EPRINTS_PATH/bin/generate_apacheconf --system --replace
apachectl restart
EPRINTS_PATH/bin/generate_static ARCHIVE_ID
EPRINTS_PATH/bin/epadmin refresh_views ARCHIVE_ID
EPRINTS_PATH/bin/epadmin refresh_abstracts ARCHIVE_ID

 

The only other place I tend to find that the hostname might be hardcoded is if you archive has an ssl/securehost.conf file.  Where you will need to change the ServerName attribute and maybe generate a temporary Let's Encrypt certificate for the new hostname.  At that point you will need to update the SSLCertificate... attributes as well.

 

Beyond this, if you have an existing EPrints repository you have not always maintained your predecessor may have hardcoded the hostname in the code or configuration at an archive level.  Usually a grep for the hostname in the archives's cfg directory (EPRINTS_PATH/archives/ARCHIVE_ID/cfg/) will find these.  You are best trying to fix the fact that they are hardcoded, so this does not cause a problem in future.

 

Regards

 

David Newman

 

 

On 04/08/2023 17:34, Adams, Thomas via Eprints-tech wrote:

CAUTION: This e-mail originated outside the University of Southampton.

I would like to safely transition from EPrints 3.4.1 to 3.4.5, and upgrading the OS from CentOS 7.9.2 to Rocky 9.2

 

I now have the original machine called: repository and the new,  temporary machine  called: newrepository

 

The newrepository machine has:

                Rocky Linux 9.2

apache/2.4.53

mysqld 10.5.16-MariaDB

LetsEncrypt

 

The /opt/eprints directory has been copied over and the mysql has been dump and reloaded into the newrepository machine.

 

While I am able to view the home page of newrepository machine, all of the menus and links all point back to the original repository server.

 

Where are all of the places I need to change the “repository” machine name to “newrepository” in the configuration files?

Does the mysql database have the server name embedded within it as well?

 

There seems to be thousands of cached files, which have the old machine name within the URLs in the files. (e.g. /opt/eprints/archives/myrepo/html/en/index.html)

Not able to login as admin to rebuild them, since I end up back to the original machine.

 

Thanks

 

-Tom



*** 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/