Primo users can't login after upgrade
- Product: Primo
- Product Version: July 2015 and onwards
- Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care
Symptoms
After a Primo upgrade, users can't log in. When they enter their credentials, they get this apache error:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, primo@dc03vg0137eu and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/0.9.8zf mod_perl/2.0.5 Perl/v5.8.9 Server at north-primo.hosted.exlibrisgroup.com Port 443
(with the relevant URL, of course).
In the error_log_ssl at apcl you can see this kind of error:
[Mon Aug 17 10:53:13 2015] [error] [client 212.219.63.253] Can't locate PDSUtil.pm in @INC (@INC contains: /exlibris/product/perl-5.8.9/lib/5.8.9/i686-linux /exlibris/pro
duct/perl-5.8.9/lib/5.8.9 /exlibris/product/perl-5.8.9/lib/site_perl/5.8.9/i686-linux /exlibris/product/perl-5.8.9/lib/site_perl/5.8.9 .) at /exlibris/primo/p4_1/primoe/a
pache/htdocs/shib/44NORTH/pds_main line 3., referer: https://north-primo.hosted.exlibrisg...&isMobile=fals
e&url=http://nelson.northampton.ac.uk:80/p...ion%2fsearch.d
o%3fdscnt%3d0%26amp%3bdstmp%3d1439805188011%26amp%3bvid%3d44NORTH_V1%26amp%3binitializeIndex%3dtrue
The cause for this seems to be that the older versions were using perl from a very old release, and it seems that that version of pearl had pdsroot/program hardcoded into its path. The new release switched to a new version of perl and deleted the older release, and so perl doesn't know where to look for the PDS programs.
Workaround
Add the following line to httpd.conf under the apache configuration folder (apcc):
setenv PERL5LIB /exlibris/primo/p4_1/pds/program/
- Article last edited: 14-03-2016