My immediate thought would be whether the file at...
/cgi/saved_search
...has permission to be executed.

Now normally, the permission bits for the actual file do not need to be set to execute,
as long as the cgi folder itself is set in the apache config to be able to execute perl scripts or cgi files.
EPrints provides a utility that will automatically set up your apache config for you.
It is normally ran when you first create your repository - so you might have ran this already.

If it's not an apache config issue,
it could be database-related, since saved searches get saved to the database.
To make sure your code and database are talking together nicely,
there's a command to automatically update your database to ensure it has the relevant datasets and fields that EPrint needs it to have.

So here are the commands I've spoken of:

Most people install eprints to the /opt/eprints3/ directory,
so that is what I'm assuming with the commands examples below
- feel free to change the path if you have installed it somewhere else.

Am also using "archive_id" as the name of the archive/repository - this should be changed to the name of your archive.

To generate the default apache configuration files:

/opt/eprints3/bin/generate_apacheconf --verbose archive_id

These are the flags that command can take too:

--replace
    Replace existing configuration files, overwriting any changes made.
--system
    Update the system configuration file, overwriting any changes made.
--help
    Print a brief help message and exit.
--man
    Print the full manual page and then exit.
--quiet
    Be vewwy vewwy quiet. This option will suppress all output unless an error occurs.
--verbose
    Explain in detail what is going on. May be repeated for greater effect.
--version
    Output version information and exit.

And here is some advice from the wiki to be done afterwards unless you've already done it of course:
https://wiki.eprints.org/w/Installing_EPrints_on_RHEL/Fedora/CentOS#getting_started_and_apache
Remember - any changes to apache configuration will also require a restart of apache before taking effect.

To update your database anytime you are adding new datasets or fields, there is this command:

Dry run that shows you what would happen,
without actually doing anything:

/opt/eprints3/bin/epadmin update_dry_run archive_id

Actual update, when you're happy to go ahead:

/opt/eprints3/bin/epadmin update archive_id


Of course, maybe your problem is neither of these things.

You can also run:

/opt/eprints3/bin/epadmin test --verbose

...which will test starting up your archive (typically it checks configuration and database connection), and will report any problems it is encountering.

I'm new to EPrints this year, so others with more experience may have further to advice to add.
Am also interested in hearing of your experience(s) - and how you get on trying these potential solutions.


________________________________________
From: eprints-tech-request@ecs.soton.ac.uk <eprints-tech-request@ecs.soton.ac.uk> on behalf of zen zenitram <quickfire28@gmail.com>
Sent: 11 December 2023 04:26
To: David Newman
Cc: eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] Installing Eprints 3.4.5 using GIT

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

Thank you for your help, i successfully migrated my eprints 3.3.16 to 3.4.5 version. my only problem now is when i click save searches it give's internal server error. (
Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at mcmartinez@dlsud.edu.ph<mailto:mcmartinez@dlsud.edu.ph> to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

________________________________
Apache/2.4.52 (Ubuntu) Server at thesis.dlsud.edu.ph<http://thesis.dlsud.edu.ph/> Port 80)

Thank you again

On Thu, Dec 7, 2023 at 6:13 PM David R Newman <drn@ecs.soton.ac.uk<mailto:drn@ecs.soton.ac.uk>> wrote:

Hi,

I think the issues is that the /usr/share/eprints3/perl_lib/EPrints/SystemSettings.pm that you have hard codes the path of EPrints as /opt/eprints3 but you have checked out the codebase to /usr/share/eprints3.  You either need to follow the instructions again and check out to /opt/eprints3 or edit your SystemSettings.pm and change the line:

    'base_path' => '/opt/eprints3',

to:

    'base_path' => '/usr/share/eprints3',

Regards

David Newman

On 07/12/2023 09:50, zen zenitram wrote:
CAUTION: This e-mail originated outside the University of Southampton.
here is the file inside flavours
root@eprints:/usr/share/eprints3/flavours/pub_lib# ls
cfg.d  citations  defaultcfg  inc  lang  namedsets  plugins  static  workflows
root@eprints:/usr/share/eprints3/flavours/pub_lib# ls -l
total 36
drwxrwsr-x 2 eprints eprints 4096 Dec  7 09:30 cfg.d
drwxrwsr-x 3 eprints eprints 4096 Dec  7 09:30 citations
drwxrwsr-x 5 eprints eprints 4096 Dec  7 09:30 defaultcfg
-rw-rw-r-- 1 eprints eprints  845 Dec  7 09:30 inc
drwxrwsr-x 3 eprints eprints 4096 Dec  7 09:30 lang
drwxrwsr-x 2 eprints eprints 4096 Dec  7 09:30 namedsets
drwxrwsr-x 7 eprints eprints 4096 Dec  7 09:30 plugins
drwxrwsr-x 3 eprints eprints 4096 Dec  7 09:30 static
drwxrwsr-x 3 eprints eprints 4096 Dec  7 09:30 workflows
root@eprints:/usr/share/eprints3/flavours/pub_lib# ^C
root@eprints:/usr/share/eprints3/flavours/pub_lib#


On Thu, Dec 7, 2023 at 4:33 AM David R Newman <drn@ecs.soton.ac.uk<mailto:drn@ecs.soton.ac.uk>> wrote:
Hi,

This is a Git rather than EPrints related issue.  It basically means you are in a directory which does not contain a .git sub-directory and neither does any of the parent directories (up to the / directory) contains a .git sub-directory.  If you clone EPrints 3.4.5 you would do something like:

su root
mkdir /opt/eprints3
chmod 2775 /opt/eprints3
chown eprints:eprints /opt/eprints3
su eprints
git clone https://github.com/eprints/eprints3.4.git<https://github.com/eprints/eprints3.4.git> /opt/eprints3
cd /opt/eprints3/
git checkout tags/3.4.5

I can see from the instructions on https://wiki.eprints.org/w/Installing_EPrints_on_RHEL/Fedora/CentOS#Installing_EPrints_3.4.x_from_Source<https://wiki.eprints.org/w/Installing_EPrints_on_RHEL/Fedora/CentOS#Installing_EPrints_3.4.x_from_Source> has been missing the penultimate (cd /opt/eprints3/) instruction, so I have added this.  If you make sure you are in the /opt/eprints3/ directory before running "git checkout tags/3.4.5", this command should work and not return the error you reported.

Regards

David Newman

On 05/12/2023 4:45 am, zen zenitram wrote:
CAUTION: This e-mail originated outside the University of Southampton.
CAUTION: This e-mail originated outside the University of Southampton.
Good day!


Im trying to install eprints 3.4.5 using git and i encounter this error


Solving “Fatal: Not A Git Repository” (Or Any Of The Parent Directories) Error


Any help with this?



*** Options: https://wiki.eprints.org/w/Eprints-tech_Mailing_List<https://wiki.eprints.org/w/Eprints-tech_Mailing_List>
*** Archive: https://www.eprints.org/tech.php/<https://www.eprints.org/tech.php/>
*** EPrints community wiki: https://wiki.eprints.org/<https://wiki.eprints.org/>



*** Options: https://wiki.eprints.org/w/Eprints-tech_Mailing_List
*** Archive: https://www.eprints.org/tech.php/
*** EPrints community wiki: https://wiki.eprints.org/