Running the eprints server.......first time.

Seems that there was couple of reasons for server to not work, even after the complete installation. First issue was related to the SELiinux (Security Enhanced Linux in Fedora and RedHat). It took some time to figure out and understand this. As eprints server keep the files in a directory (/opt/…) other than usual path of http files, SELinux do not give it access by default. Just to check this we disabled the SELinux temporarily. This allowed starting the apache server properly. And now we can access the server using https (secure link, as we configured the eprints to use https). Great…

Although server started working using https link, most of the links on the web page were in http, which was restricting the smooth access of site. We realized it was easier to make http working, compared to converting everything to https. With the help of internet search, we did some appropriate changes in apache configuration file to run the http (80). After reconfiguring the eprints server for port 80, we got THE EPRINTS SEVER RUNNING on a http address (finally!).

Later, we applied the required SELinux authorizations to web directories of eprints and enabled the SELinux. We still need to check the SELinux issues in depth. But we will do it only if we run in to problem again or get some volunteer to do it ;)

(Monday, April 24, 2006)