EPrints Technical Mailing List Archive

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

Message: #10257


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

Re: [EP-tech] New site still inaccessible


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

Re: "already done the "generate_apacheconf" command, but I just fired
it up again to see whether that might help, and hey presto! It worked."

Hallelujah! =D

In the meantime, there seems great scope for improving the
installation process of an EPrints version,
and I'm looking forwards to the day installation is much simplified,
and would be happy to make contributions to any installation
simplification efforts.

Yours,
Andrew.


Quoting Will Hughes:

Andrew

Thank you very much indeed for putting a fresh pair of eyes on this.
I have been too close to the Eprints installation to realize what
was actually happening. I shall work through everything you mention:

It turns out that I had indeed correctly set up a Host-Only network
for my VM but incorrectly identified it in the Machine settings
(Adaptor 1) as NAT instead of Host-Only. These are now lined up.
But, on its own, that still causes the browser to throw a 500
Internal Server Error. But the host only DNS name resolved correctly
to http://arcomtest, and the request hit Apache. So, to probe further,

The Ubuntu Firewall is reported by ufw status as inactive

Apache is indeed running, as reported by systemctl status apache2.

The apache2/error.log reports this:
[Sat Sep 20 14:56:17.076223 2025] [perl:error] [pid 933:tid
123629776275136] [client 192.168.56.1:50568] Can't locate object
method "abort" via package "EPrints" at
/opt/eprints3/perl_lib/EPrints/Apache/Rewrite.pm line 74.\n
[Sat Sep 20 14:56:31.131835 2025] [perl:error] [pid 933:tid
123629677303488] [client 192.168.56.1:50576] Can't locate object
method "abort" via package "EPrints" at
/opt/eprints3/perl_lib/EPrints/Apache/Rewrite.pm line 74.\n

The config files are definitely confusing! I like the idea of
comparing them between the local dev and the production setup (if
only I'd done that before, dammit...)
/opt/eprints3/cfg/perl_module_isolation.conf exists the same in both

Yes, an apache.conf exists in the /opt/eprints3/cfg directory
Yes, /opt/eprints3/cfg/perl_module_isolation.conf is present

It looks like the apache2 stuff is all here:
libapache2-mod-perl2/noble,now 2.0.13-1build5 amd64 [installed]
  Integration of perl with the Apache2 web server
libapache2-mod-perl2-dev/noble 2.0.13-1build5 all
  Integration of perl with the Apache2 web server - development files
libapache2-mod-perl2-doc/noble 2.0.13-1build5 all
  Integration of perl with the Apache2 web server - documentation
liblinux-pid-perl/noble 0.04-2build4 amd64
  wrapper around the getpid() and getppid() C functions

I had already done the "generate_apacheconf" command, but I just
fired it up again to see whether that might help, and hey presto! It
worked.

So, thanks for taking the time to list out these steps. I was
running out of ideas.

Cheers!

Best wishes

Will