User Tools

Site Tools


redhat_evergreen_cluster

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
redhat_evergreen_cluster [2010/03/10 14:06]
leed created
redhat_evergreen_cluster [2012/05/03 22:28] (current)
lebbeous
Line 1: Line 1:
 ======Installing an Evergreen cluster on Redhat====== ======Installing an Evergreen cluster on Redhat======
 +
 +//Obviously this document is a little dated now anyway, and the reader should know that as of May 2012 RHEL and CentOS targets in the prerequisites installer "​Makefile.install"​ have been removed. ​ It's not that we think it's impossible to get Evergreen working on these systems (we know it isn't, at least in the former case), but that we haven'​t had anyone share with the community up-to-date working Redhat configs or volunteer to test them. Start here if you want to resurrect what we had from our version control system to try to get it working again: [[http://​git.evergreen-ils.org/?​p=working/​Evergreen.git;​a=shortlog;​h=refs/​heads/​user/​dbs/​update_makefile_prereqs]]//​
  
 On a typical cluster install you will have an apache server, multiple drones, a database server, and a utility server. ​ You will need to refer to this document for the next few steps: [[redhat_opensrf_trunk|Installation instructions for OpenSRF trunk on redhat]] On a typical cluster install you will have an apache server, multiple drones, a database server, and a utility server. ​ You will need to refer to this document for the next few steps: [[redhat_opensrf_trunk|Installation instructions for OpenSRF trunk on redhat]]
Line 20: Line 22:
   - For the postgresql steps remember to perform these steps on the database server, **not the apache server.** When you get to the pg_hba.conf section edit it with the following lines replacing the marked sections with your network info:<​code bash>   - For the postgresql steps remember to perform these steps on the database server, **not the apache server.** When you get to the pg_hba.conf section edit it with the following lines replacing the marked sections with your network info:<​code bash>
 local all all trust  local all all trust 
-host all all 127.0.0.1 255.255.255.255 ​trust +host all all 127.0.0.1 255.255.255.255 ​md5 
-host all all <​local.network.address>​ <​local.subnet> ​trust</​code>​+host all all <​local.network.address>​ <​local.subnet> ​md5</​code>​
   - Now edit /​var/​lib/​pgsql/​data/​postgresql.conf and edit the line:<​code bash>   - Now edit /​var/​lib/​pgsql/​data/​postgresql.conf and edit the line:<​code bash>
 “listen_addresses = '​localhost'​” ​ “listen_addresses = '​localhost'​” ​
Line 36: Line 38:
   - As the **opensrf** user, download the brick_ctl.sh script and it's corresponding config file. Edit it the config file to contain your settings:<​code bash>   - As the **opensrf** user, download the brick_ctl.sh script and it's corresponding config file. Edit it the config file to contain your settings:<​code bash>
 cd /​openils/​bin cd /​openils/​bin
-wget http://​svn.open-ils.org/​trac/​ILS/​browser/​trunk/​Open-ILS/​src/​support-scripts/​brick_ctl.sh+wget http://​svn.open-ils.org/​trac/​ILS/​export/​16289/​trunk/​Open-ILS/​src/​support-scripts/​brick_ctl.sh
 chmod +x brick_ctl.sh chmod +x brick_ctl.sh
 cd ~ cd ~
-wget http://​svn.open-ils.org/​trac/​ILS/​browser/​trunk/​Open-ILS/​src/​support-scripts/​oils_brick.cfg.example+wget http://​svn.open-ils.org/​trac/​ILS/​export/​16289/​trunk/​Open-ILS/​src/​support-scripts/​oils_brick.cfg.example
 mv oils_brick.cfg.example .oils_brick.cfg mv oils_brick.cfg.example .oils_brick.cfg
 vi .oils_brick.cfg</​code>​ vi .oils_brick.cfg</​code>​
   - Start up your cluster as the **opensrf** user!<​code bash>   - Start up your cluster as the **opensrf** user!<​code bash>
 brick_ctl.sh -a start_all</​code>​ brick_ctl.sh -a start_all</​code>​
- 
  
  
redhat_evergreen_cluster.1268247960.txt.gz · Last modified: 2010/03/10 14:06 by leed

© 2008-2017 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a member of Software Freedom Conservancy.