[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EP-tech] Not a valid repository identifier

The command I run first when something like this happens is:
[EPRINTS_ROOT]/bin/epadmin test

If you have multiple archives, you can also test just one:
[EPRINTS_ROOT]/bin/epadmin test ARCHIVE_ID

This will flag any issues with the EPrints config (such as a missing semi-colon as suggested below).


From: eprints-tech-bounces at ecs.soton.ac.uk [mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of Alan.Stiles
Sent: 27 February 2018 09:05
To: eprints-tech at ecs.soton.ac.uk
Subject: Re: [EP-tech] Not a valid repository identifier

A thought ? it might just be when you copied the code into the email, but does your 10_core.pl file have a semi-colon on the end of the last line in the broken repository?

$c->{http_root} = undef


From: eprints-tech-bounces at ecs.soton.ac.uk<mailto:eprints-tech-bounces at ecs.soton.ac.uk> [mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of Christer Enkvist
Sent: 26 February 2018 18:43
To: eprints-tech at ecs.soton.ac.uk<mailto:eprints-tech at ecs.soton.ac.uk>
Subject: [EP-tech] Not a valid repository identifier


Eprints 3.3.14/Ubuntu 12LTS.

I have made something stupid in my settings, probably in Apache.  I have two repositories on a server, pub5 and stud5.  Both worked excellently but suddenly one stopped working (yes, I did something in some Apache/SSL setting but can?t figure out what).

Now I cannot access and pages and the log explains why:

---------------- EPrints System Error ----------------------------
'pub5' is not a valid repository identifier:
PerlSetVar EPrints_ArchiveID pub5
EPrints System Error inducing stack dump
at /usr/share/eprints3/perl_lib/EPrints.pm line 147
        EPrints::abort('EPrints') called at /usr/share/eprints3/perl_lib/EPrints/Apache/Rewrite.pm line 62
        EPrints::Apache::Rewrite::handler('Apache2::RequestRec=SCALAR(0x7f5d18e9f888)') called at -e line 0
        eval {...} called at -e line 0

This is very weird as the repository is indeed pub5. So I assume some setting somewhere has been set wrong.

Problem is that I cannot find/understand what I have done.  Both repos have virtual host files looking like:

<VirtualHost *:443>
SSLEngine on
  ServerName pub.epsilon.slu.se

  ServerAdmin eprints-adm at bib.slu.se<mailto:eprints-adm at bib.slu.se>

SSLCertificateFile /etc/apache2/ssl/star_epsilon_slu_se.crt
SSLCertificateKeyFile /etc/apache2/ssl/star.epsilon.slu.se.key
SSLCertificateChainFile /etc/apache2/ssl/DigiCertCA.crt

PerlTransHandler +EPrints::Apache::Rewrite

  <Location "">
    PerlSetVar EPrints_ArchiveID pub5
    PerlSetVar EPrints_Secure yes

    Options +ExecCGI
    Order allow,deny
    Allow from all

  ErrorLog /var/log/apache2/pub_ssl_error.log
  CustomLog /var/log/apache2/pub_ssl_access.log combined
  RewriteEngine On
  RewriteRule .* - [F]

  PerlTransHandler +EPrints::Apache::Rewrite

That is, one file have ServerName= pub.epsilon.slu.se and REPOID=pub5, the other stud.epsilon.slu.se with REPOID=stud5.  If I in the failing pub5-config file choose the other repo-id, then it works (so to me that means that the virtual hosts file are ok).  I then assumed that the problem is the REPO/cfg/cfg.d/10_core.pl files, but these are short and simple:

$c->{aliases} = [];
$c->{securehost} = 'pub.epsilon.slu.se';
$c->{secureport} = 443;
$c->{http_root} = undef

And with host 'stud.epsilon.slu.se' for the other (working repo).

/usr/share/eprints3/bin/epadmin test pub5
Everything seems OK.

I have also re-genreated all static pages.

Any suggestion what I have missed to check/change is most welcome.  Please let me know!


-- The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302). The Open University is authorised and regulated by the Financial Conduct Authority in relation to its secondary activity of credit broking.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/attachments/20180227/7e428338/attachment-0001.html