EPrints Technical Mailing List Archive

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

Message: #08394

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

Re: [EP-tech] Debian9 full-upgrade to Debian10 likes to remove eprints

  • To: <th.lauke@arcor.de>
  • Subject: Re: [EP-tech] Debian9 full-upgrade to Debian10 likes to remove eprints
  • From: David R Newman <drn@ecs.soton.ac.uk>
  • Date: Mon, 7 Dec 2020 15:56:54 +0000
Hi Thomas,
It is good to know that both installing on Debian 10 and upgrading from Debian 9 to Debian 10 seem to both work.  It would be useful for clarity if you could detail the exact steps that you had to take to keeping/upgrading MySQL between Debian 9 and Debian 10.  I assume this may involve adding MySQL's own APT repository so that it continue to exist according to your operating system and be upgraded to the appropriate version.
On the topic of the error message you are seeing when loading the login page.  Looking at that line of code, it looks like you assessment is fairly accurate.  Please could you answer a number of questions:
1. Does cfg/cfg.d/10_core.pl exist for you archive and is $c->{host} set to the hostname for you testing clone and the URL you are accessing /cgi/users/login on in your web browser?
2. Have you run "epadmin generate_apacheconf --system --replace" before reloading Apache?
3. Do you have HTTPS enabled on this test clone in 10_core.pl or another file in your archive's cfg/cfg.d/ directory (e.g. https.pl).  If so what is $c->{securehost} set to?
I think the first two are the critical questions.  The third might just complicate my advice if I assume you have HTTPS enabled and you don't or vice-versa. 

Regards

David Newman

On 07/12/2020 15:33, th.lauke@arcor.de wrote:

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

Hi David,


and see if there is an eprints dependency not available in Debian 10

yes, MariaDB is the new default ...

thus keeping/upgrading mysql keeps EPrints alive ...
BTW: a manual install of EPrints 3.4.2 accepts MariaDB!


I will be back when EPrints is up and running again ... on Debian 10 ... hopefully!

okay, upgrade seems to be done, login page is shown, but then I receive following error:
Can't locate object method "host" via package "URI::_generic" at /usr/share/eprints/cgi/users/login line 16.

I fear it's caused by a still misconfigured hostname of the testing clone ...
But currently I couldn't imagine any missed location :(

So, any helpful idea would be appreciated
Thomas


--
This email has been checked for viruses by AVG.
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.avg.com%2F&amp;data=04%7C01%7C%7Ccedd7d0e3cea4a793e2308d89ac8b85d%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637429534163072806%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=1g%2BklqEH2fu4a4KwyQm01EmuIJIp0Bpkfxc35p8ImsE%3D&amp;reserved=0