Hi Rob,

 i think the problem is the new version of "perl".

From 5.16+ the utf8::decode($param) return e different value if $param is "undef" so you can try apply a patch https://github.com/eprints/eprints/commit/157db0d27d423d38f9c0fc31ce47e519cd861d45

or use:

sed -i -e 's/utf8::decode($value);/if( EPrints::Utils::is_set( $value ) ) {\n\t\tutf8::decode($value);\n\t}/' perl_lib/EPrints/Repository.pm
sed -i -e 's/utf8::decode($_) for @result;/for( @result ) {\n\t\tnext if( !EPrints::Utils::is_set( $_ ) );\n\t\tutf8::decode($_);\n\t}/' perl_lib/EPrints/Repository.pm

  Enio

Il 21/11/2016 15:43, Rob McMahon ha scritto:

This is a new installation, to move a current archive from Ubuntu to CentOS.
EPrints 3.3.10

CentOS 7, with SELinux enabled

I've seen a couple of references to this problem in the archives.
[EP-tech] EPrints 3.3.12 Installation (from source) - Gilles Fournié

who refers to
[EP-tech] Move 302 - David McElroy

But I don't see an answer, except to re-install.  I'd much rather not go down that route.

I've installled 3.3.10 from source (3.3.10 because I want the new box to look as much like the original as possible before upgrading it).  This is on CentOS 7, and I had a few issues with permissions initially, but which I now believe are resolved, mostly by putting the eprints directory in the httpd_sys_content_t context.

When you try to login as the admin user that I set up during epadmin create, you are taken to a page (cgi/users/login?login_check=1) that says

302 Moved.
Moved
The document has moved here.

The apache ssl_access_log says

[21/Nov/2016:10:43:09 +0000] "GET / HTTP/1.1" 200 7984
[21/Nov/2016:10:44:03 +0000] "GET /cgi/users/home HTTP/1.1" 302 -
[21/Nov/2016:10:44:03 +0000] "GET /cgi/users/login?target=https%3A%2F%2F---%2Fcgi%2Fusers%2Fhome HTTP/1.1" 401 6119
[21/Nov/2016:10:51:05 +0000] "POST /cgi/users/login HTTP/1.1" 302 -
[21/Nov/2016:10:51:06 +0000] "GET /cgi/users/login?login_check=1 HTTP/1.1" 302 184

If you press the "back" button you are back to the front screen, and appear to be logged in successfully, although it has an error message saying "The requested screen does not exist, or has a fatal error: ."

Has anyone got any clues as to what causes this ?  Can anyone help me debug this ?  I really don't want to start again, and have no confidence that I won't just hit the same error again.  I'm tempted to use Gilles' hack.

Cheers,

Rob

*** 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/
*** EPrints developers Forum: http://forum.eprints.org/

*** 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/
*** EPrints developers Forum: http://forum.eprints.org/