1 Installing the Evergreen server
2 ===============================
6 Preamble: referenced user accounts
7 ----------------------------------
9 In subsequent sections, we will refer to a number of different accounts, as
12 * Linux user accounts:
13 ** The *user* Linux account is the account that you use to log onto the
14 Linux system as a regular user.
15 ** The *root* Linux account is an account that has system administrator
16 privileges. On Debian and Fedora you can switch to this account from
17 your *user* account by issuing the `su -` command and entering the
18 password for the *root* account when prompted. On Ubuntu you can switch
19 to this account from your *user* account using the `sudo su -` command
20 and entering the password for your *user* account when prompted.
21 ** The *opensrf* Linux account is an account that you create when installing
22 OpenSRF. You can switch to this account from the *root* account by
23 issuing the `su - opensrf` command.
24 ** The *postgres* Linux account is created automatically when you install
25 the PostgreSQL database server. You can switch to this account from the
26 *root* account by issuing the `su - postgres` command.
27 * PostgreSQL user accounts:
28 ** The *evergreen* PostgreSQL account is a superuser account that you will
29 create to connect to the PostgreSQL database server.
30 * Evergreen administrator account:
31 ** The *egadmin* Evergreen account is an administrator account for
32 Evergreen that you will use to test connectivity and configure your
35 Preamble: developer instructions
36 --------------------------------
39 Skip this section if you are using an official release tarball downloaded
40 from http://evergreen-ils.org/egdownloads
42 Developers working directly with the source code from the Git repository,
43 rather than an official release tarball, must perform one step before they
44 can proceed with the `./configure` step.
46 As the *user* Linux account, issue the following command in the Evergreen
47 source directory to generate the configure script and Makefiles:
50 ------------------------------------------------------------------------------
52 ------------------------------------------------------------------------------
54 Installing prerequisites
55 ------------------------
57 * **PostgreSQL**: Version 9.3 is recommended. The minimum supported version
59 * **Linux**: Evergreen 2.8 has been tested on Debian Jessie (8.0),
60 Debian Wheezy (7.0), Ubuntu Trusty Tahr (14.04),
61 Ubuntu Precise Pangolin (12.04), and Fedora.
62 If you are running an older version of these distributions, you may want
63 to upgrade before upgrading Evergreen. For instructions on upgrading these
64 distributions, visit the Debian, Ubuntu or Fedora websites.
65 * **OpenSRF**: The minimum supported version of OpenSRF is 2.4.0.
68 Evergreen has a number of prerequisite packages that must be installed
69 before you can successfully configure, compile, and install Evergreen.
71 1. Begin by installing the most recent version of OpenSRF (2.4.0 or later).
72 You can download OpenSRF releases from http://evergreen-ils.org/opensrf-downloads/
73 2. On some distributions, it is necessary to install PostgreSQL 9.1+ from external
76 * Debian Wheezy and Jessie Ubuntu Precise and Trusty comes with
77 PostgreSQL 9.1+, so no additional steps are required.
78 * Fedora 19 and 20 come with PostgreSQL 9.2+, so no additional steps are required.
80 3. On Debian and Ubuntu, run `aptitude update` as the *root* Linux account to
81 retrieve the new packages from the backports repository.
82 4. Issue the following commands as the *root* Linux account to install
83 prerequisites using the `Makefile.install` prerequisite installer,
84 substituting `debian-jessie`, `debian-wheezy`, `fedora`,
85 `ubuntu-trusty`, or `ubuntu-precise` for <osname> below:
88 ------------------------------------------------------------------------------
89 make -f Open-ILS/src/extras/Makefile.install <osname>
90 ------------------------------------------------------------------------------
92 5. Add the libdbi-libdbd libraries to the system dynamic library path by
93 issuing the following commands as the *root* Linux account:
96 You should skip this step if installing on Ubuntu Precise, Trusty or Debian Jessie. The ubuntu
97 and Debian Jessie targets use libdbd-pgsql from packages.
101 ------------------------------------------------------------------------------
102 echo "/usr/local/lib/dbd" > /etc/ld.so.conf.d/eg.conf
104 ------------------------------------------------------------------------------
108 ------------------------------------------------------------------------------
109 echo "/usr/lib64/dbd" > /etc/ld.so.conf.d/eg.conf
111 ------------------------------------------------------------------------------
113 6. OPTIONAL: Developer additions
115 To perform certain developer tasks from a Git source code checkout,
116 additional packages may be required. As the *root* Linux account:
118 * To install packages needed for retriving and managing web dependencies,
119 use the <osname>-developer Makefile.install target. Currently,
120 this is only needed for building and installing the (preview) browser
124 ------------------------------------------------------------------------------
125 make -f Open-ILS/src/extras/Makefile.install <osname>-developer
126 ------------------------------------------------------------------------------
128 * To install packages required for building Evergreen release bundles, use
129 the <osname>-packager Makefile.install target.
132 ------------------------------------------------------------------------------
133 make -f Open-ILS/src/extras/Makefile.install <osname>-packager
134 ------------------------------------------------------------------------------
136 Optional: Extra steps for browser-based staff client
137 ----------------------------------------------------
140 Skip this entire section if you are using an official release tarball downloaded
141 from http://evergreen-ils.org/downloads
144 You make skip the subsection `Install dependencies for browser-based staff client'
145 if you are installing on either Debian Jessie or Ubuntu Trusty and you have
146 installed the `Optional: Developer Additions' described above. You will still
147 need to do the steps in `Install files for browser-based staff client' below.
149 Install dependencies for browser-based staff client
150 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
152 1. Install Node.js. For more information see also:
153 https://github.com/joyent/node/wiki/installation[Node.js Installation]
156 ------------------------------------------------------------------------------
157 # Go to a temporary directory
160 # Clone the code and checkout the necessary version
161 git clone https://github.com/joyent/node.git
163 git checkout -b v0.10.28 v0.10.28
165 # set -j to the number of CPU cores on the server + 1
166 ./configure && make -j2 && sudo make install
170 ------------------------------------------------------------------------------
175 ------------------------------------------------------------------------------
176 % sudo npm install -g grunt-cli
177 ------------------------------------------------------------------------------
182 ------------------------------------------------------------------------------
183 % sudo npm install -g bower
184 ------------------------------------------------------------------------------
186 Install files for browser-based staff client
187 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
189 1. Building, Testing, Minification: The remaining steps all take place within
190 the staff JS web root:
193 ------------------------------------------------------------------------------
194 cd $EVERGREEN_ROOT/Open-ILS/web/js/ui/default/staff/
195 ------------------------------------------------------------------------------
197 2. Install Project-local Dependencies. npm inspects the 'package.json' file
198 for dependencies and fetches them from the Node package network.
201 ------------------------------------------------------------------------------
202 npm install # fetch Grunt dependencies
203 bower install # fetch JS dependencies
204 ------------------------------------------------------------------------------
206 3. Run the build script.
209 ------------------------------------------------------------------------------
210 # build, run tests, concat+minify
212 ------------------------------------------------------------------------------
215 Configuration and compilation instructions
216 ------------------------------------------
218 For the time being, we are still installing everything in the `/openils/`
219 directory. From the Evergreen source directory, issue the following commands as
220 the *user* Linux account to configure and build Evergreen:
223 ------------------------------------------------------------------------------
224 PATH=/openils/bin:$PATH ./configure --prefix=/openils --sysconfdir=/openils/conf
226 ------------------------------------------------------------------------------
228 These instructions assume that you have also installed OpenSRF under `/openils/`.
229 If not, please adjust PATH as needed so that the Evergreen `configure` script
230 can find `osrf_config`.
232 Installation instructions
233 -------------------------
235 1. Once you have configured and compiled Evergreen, issue the following
236 command as the *root* Linux account to install Evergreen, build the server
237 portion of the staff client, and copy example configuration files to
239 Change the value of the `STAFF_CLIENT_STAMP_ID` variable to match the version
240 of the staff client that you will use to connect to the Evergreen server.
243 ------------------------------------------------------------------------------
244 make STAFF_CLIENT_STAMP_ID=rel_name install
245 ------------------------------------------------------------------------------
247 2. The server portion of the staff client expects `http://hostname/xul/server`
248 to resolve. Issue the following commands as the *root* Linux account to
249 create a symbolic link pointing to the `server` subdirectory of the server
250 portion of the staff client that we just built using the staff client ID
254 ------------------------------------------------------------------------------
255 cd /openils/var/web/xul
256 ln -sf rel_name/server server
257 ------------------------------------------------------------------------------
259 Change ownership of the Evergreen files
260 ---------------------------------------
262 All files in the `/openils/` directory and subdirectories must be owned by the
263 `opensrf` user. Issue the following command as the *root* Linux account to
264 change the ownership on the files:
267 ------------------------------------------------------------------------------
268 chown -R opensrf:opensrf /openils
269 ------------------------------------------------------------------------------
271 Additional Instructions for Developers
272 --------------------------------------
275 Skip this section if you are using an official release tarball downloaded
276 from http://evergreen-ils.org/egdownloads
278 Developers working directly with the source code from the Git repository,
279 rather than an official release tarball, need to install the Dojo Toolkit
280 set of JavaScript libraries. The appropriate version of Dojo is included in
281 Evergreen release tarballs. Developers should install the Dojo 1.3.3 version
282 of Dojo by issuing the following commands as the *opensrf* Linux account:
285 ------------------------------------------------------------------------------
286 wget http://download.dojotoolkit.org/release-1.3.3/dojo-release-1.3.3.tar.gz
287 tar -C /openils/var/web/js -xzf dojo-release-1.3.3.tar.gz
288 cp -r /openils/var/web/js/dojo-release-1.3.3/* /openils/var/web/js/dojo/.
289 ------------------------------------------------------------------------------
292 Configure the Apache Web server
293 -------------------------------
295 1. Use the example configuration files in `Open-ILS/examples/apache/` (for
296 Apache versions below 2.4) or `Open-ILS/examples/apache_24/` (for Apache
297 versions 2.4 or greater) to configure your Web server for the Evergreen
298 catalog, staff client, Web services, and administration interfaces. Issue the
299 following commands as the *root* Linux account:
301 .Debian Wheezy and Ubuntu Precise
303 ------------------------------------------------------------------------------
304 cp Open-ILS/examples/apache/eg.conf /etc/apache2/sites-available/
305 cp Open-ILS/examples/apache/eg_vhost.conf /etc/apache2/
306 cp Open-ILS/examples/apache/eg_startup /etc/apache2/
308 mkdir /etc/apache2/ssl
310 ------------------------------------------------------------------------------
312 .Ubuntu Trusty and Debian Jessie
314 ------------------------------------------------------------------------------------
315 cp Open-ILS/examples/apache_24/eg_24.conf /etc/apache2/sites-available/eg.conf
316 cp Open-ILS/examples/apache_24/eg_vhost_24.conf /etc/apache2/eg_vhost.conf
317 cp Open-ILS/examples/apache/eg_startup /etc/apache2/
319 mkdir /etc/apache2/ssl
321 ------------------------------------------------------------------------------------
325 ------------------------------------------------------------------------------
326 cp Open-ILS/examples/apache_24/eg_24.conf /etc/httpd/conf.d/
327 cp Open-ILS/examples/apache_24/eg_vhost_24.conf /etc/httpd/eg_vhost.conf
328 cp Open-ILS/examples/apache/eg_startup /etc/httpd/
332 ------------------------------------------------------------------------------
334 2. The `openssl` command cuts a new SSL key for your Apache server. For a
335 production server, you should purchase a signed SSL certificate, but you can
336 just use a self-signed certificate and accept the warnings in the staff client
337 and browser during testing and development. Create an SSL key for the Apache
338 server by issuing the following command as the *root* Linux account:
341 ------------------------------------------------------------------------------
342 openssl req -new -x509 -days 365 -nodes -out server.crt -keyout server.key
343 ------------------------------------------------------------------------------
345 3. As the *root* Linux account, edit the `eg.conf` file that you copied into
347 a. To enable access to the offline upload / execute interface from any
348 workstation on any network, make the following change (and note that
349 you *must* secure this for a production instance):
350 * (Apache 2.2): Replace `Allow from 10.0.0.0/8` with `Allow from all`
351 * (Apache 2.4): Replace `Require host 10.0.0.0/8` with `Require all granted`
352 b. (Fedora): Change references from the non-existent `/etc/apache2/` directory
354 4. Change the user for the Apache server.
355 * (Debian and Ubuntu): As the *root* Linux account, edit
356 `/etc/apache2/envvars`. Change `export APACHE_RUN_USER=www-data` to
357 `export APACHE_RUN_USER=opensrf`.
358 * (Fedora): As the *root* Linux account , edit `/etc/httpd/conf/httpd.conf`.
359 Change `User apache` to `User opensrf`.
360 5. Configure Apache with performance settings appropriate for Evergreen:
361 * (Debian and Ubuntu): As the *root* Linux account, edit
362 `/etc/apache2/apache2.conf`:
363 * (Fedora): As the *root* Linux account, edit `/etc/httpd/conf/httpd.conf`:
364 a. Change `KeepAliveTimeout` to `1`. Higher values reduce the chance of
365 a request timing out unexpectedly, but increase the risk of using up
366 all available Apache child processes.
367 b. 'Optional': Change `MaxKeepAliveRequests` to `100`
368 c. (Debian Wheezy, Ubuntu Precise, and Fedora) Update the prefork configuration
369 section to suit your environment. The following settings apply to a busy
373 ------------------------------------------------------------------------------
374 <IfModule mpm_prefork_module>
379 MaxRequestsPerChild 10000
381 ------------------------------------------------------------------------------
382 d. (Ubuntu Trusty, Debian Jessie) As the *root* user, edit
383 /etc/apache2/mods-available/mpm_prefork.conf to match the above values.
384 Then, also as the *root* user, enable the mpm_prefork module by doing:
387 ------------------------------------------------------------------------------
390 ------------------------------------------------------------------------------
392 6. (Fedora): As the *root* Linux account, edit the `/etc/httpd/eg_vhost.conf`
393 file to change references from the non-existent `/etc/apache2/` directory
395 7. (Debian Wheezy and Ubuntu Precise): As the *root* Linux account, enable the Evergreen site:
398 ------------------------------------------------------------------------------
399 a2dissite default # OPTIONAL: disable the default site (the "It Works" page)
401 ------------------------------------------------------------------------------
403 (Ubuntu Trusty, Debian Jessie):
406 ------------------------------------------------------------------------------
407 a2dissite 000-default # OPTIONAL: disable the default site (the "It Works" page)
409 ------------------------------------------------------------------------------
411 8. (Ubuntu): As the *root* Linux account, enable Apache to write
412 to the lock directory; this is currently necessary because Apache
413 is running as the `opensrf` user:
416 ------------------------------------------------------------------------------
417 chown opensrf /var/lock/apache2
418 ------------------------------------------------------------------------------
420 9. Learn more about additional Apache options in the following sections:
421 * <<_apache_rewrite_tricks,Apache Rewrite Tricks>>
422 * <<_apache_access_handler_perl_module,Apache Access Handler Perl Module>>
424 Configure OpenSRF for the Evergreen application
425 -----------------------------------------------
426 There are a number of example OpenSRF configuration files in `/openils/conf/`
427 that you can use as a template for your Evergreen installation. Issue the
428 following commands as the *opensrf* Linux account:
431 ------------------------------------------------------------------------------
432 cp -b /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml
433 cp -b /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml
434 ------------------------------------------------------------------------------
436 When you installed OpenSRF, you created four Jabber users on two
437 separate domains and edited the `opensrf_core.xml` file accordingly. Please
438 refer back to the OpenSRF README and, as the *opensrf* Linux account, edit the
439 Evergreen version of the `opensrf_core.xml` file using the same Jabber users
440 and domains as you used while installing and testing OpenSRF.
443 The `-b` flag tells the `cp` command to create a backup version of the
444 destination file. The backup version of the destination file has a tilde (`~`)
445 appended to the file name, so if you have forgotten the Jabber users and
446 domains, you can retrieve the settings from the backup version of the files.
448 `eg_db_config`, described in the following section, sets the database
449 connection information in `opensrf.xml` for you.
451 Creating the Evergreen database
452 -------------------------------
454 Setting up the PostgreSQL server
455 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
457 For production use, most libraries install the PostgreSQL database server on a
458 dedicated machine. Therefore, by default, the `Makefile.install` prerequisite
459 installer does *not* install the PostgreSQL 9 database server that is required
460 by every Evergreen system. You can install the packages required by Debian or
461 Ubuntu on the machine of your choice using the following commands as the
462 *root* Linux account:
464 .(Debian / Ubuntu / Fedora) Installing PostgreSQL server packages
466 Each OS build target provides the postgres server installation packages
467 required for each operating system. To install Postgres server packages,
468 use the make target 'postgres-server-<OSTYPE>'. Choose the most appropriate
469 command below based on your operating system.
472 ------------------------------------------------------------------------------
473 make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-jessie
474 make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-wheezy
475 make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-precise
476 make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-trusty
477 make -f Open-ILS/src/extras/Makefile.install postgres-server-fedora
478 ------------------------------------------------------------------------------
480 .(Fedora) Postgres initialization
482 Installing Postgres on Fedora also requires you to initialize the PostgreSQL
483 cluster and start the service. Issue the following commands as the *root* user:
486 ------------------------------------------------------------------------------
487 postgresql-setup initdb
488 systemctl start postgresql
489 ------------------------------------------------------------------------------
491 For a standalone PostgreSQL server, install the following Perl modules for your
492 distribution as the *root* Linux account:
496 ---------------------------------------------------------------------------------
498 ---------------------------------------------------------------------------------
500 .(Debian "wheezy" and Ubuntu Trusty)
501 No extra modules required for these distributions.
505 ------------------------------------------------------------------------------
507 ------------------------------------------------------------------------------
509 You need to create a PostgreSQL superuser to create and access the database.
510 Issue the following command as the *postgres* Linux account to create a new
511 PostgreSQL superuser named `evergreen`. When prompted, enter the new user's
515 ------------------------------------------------------------------------------
516 createuser -s -P evergreen
517 ------------------------------------------------------------------------------
519 .Enabling connections to the PostgreSQL database
521 Your PostgreSQL database may be configured by default to prevent connections,
522 for example, it might reject attempts to connect via TCP/IP or from other
523 servers. To enable TCP/IP connections from localhost, check your `pg_hba.conf`
524 file, found in the `/etc/postgresql/` directory on Debian and Ubuntu, and in
525 the `/var/lib/pgsql/data/` directory on Fedora. A simple way to enable TCP/IP
526 connections from localhost to all databases with password authentication, which
527 would be suitable for a test install of Evergreen on a single server, is to
528 ensure the file contains the following entries _before_ any "host ... ident"
531 ------------------------------------------------------------------------------
532 host all all ::1/128 md5
533 host all all 127.0.0.1/32 md5
534 ------------------------------------------------------------------------------
536 When you change the `pg_hba.conf` file, you will need to reload PostgreSQL to
537 make the changes take effect. For more information on configuring connectivity
539 http://www.postgresql.org/docs/devel/static/auth-pg-hba-conf.html
541 Creating the Evergreen database and schema
542 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
544 Once you have created the *evergreen* PostgreSQL account, you also need to
545 create the database and schema, and configure your configuration files to point
546 at the database server. Issue the following command as the *root* Linux account
547 from inside the Evergreen source directory, replacing <user>, <password>,
548 <hostname>, <port>, and <dbname> with the appropriate values for your
549 PostgreSQL database (where <user> and <password> are for the *evergreen*
550 PostgreSQL account you just created), and replace <admin-user> and <admin-pass>
551 with the values you want for the *egadmin* Evergreen administrator account:
554 ------------------------------------------------------------------------------
555 perl Open-ILS/src/support-scripts/eg_db_config --update-config \
556 --service all --create-database --create-schema --create-offline \
557 --user <user> --password <password> --hostname <hostname> --port <port> \
558 --database <dbname> --admin-user <admin-user> --admin-pass <admin-pass>
559 ------------------------------------------------------------------------------
561 This creates the database and schema and configures all of the services in
562 your `/openils/conf/opensrf.xml` configuration file to point to that database.
563 It also creates the configuration files required by the Evergreen `cgi-bin`
564 administration scripts, and sets the user name and password for the *egadmin*
565 Evergreen administrator account to your requested values.
567 You can get a complete set of options for `eg_db_config` by passing the
572 If you add the `--load-all-sample` parameter to the `eg_db_config` command,
573 a set of authority and bibliographic records, call numbers, copies, staff
574 and regular users, and transactions will be loaded into your target
575 database. This sample dataset is commonly referred to as the _concerto_
576 sample data, and can be useful for testing out Evergreen functionality and
577 for creating problem reports that developers can easily recreate with their
578 own copy of the _concerto_ sample data.
580 Creating the database on a remote server
581 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
582 In a production instance of Evergreen, your PostgreSQL server should be
583 installed on a dedicated server.
585 PostgreSQL 9.1 and later
586 ^^^^^^^^^^^^^^^^^^^^^^^^
587 To create the database instance on a remote database server running PostgreSQL
588 9.1 or later, simply use the `--create-database` flag on `eg_db_config`.
592 1. As the *root* Linux account, start the `memcached` and `ejabberd` services
593 (if they aren't already running):
596 ------------------------------------------------------------------------------
597 /etc/init.d/ejabberd start
598 /etc/init.d/memcached start
599 ------------------------------------------------------------------------------
601 2. As the *opensrf* Linux account, start Evergreen. The `-l` flag in the
602 following command is only necessary if you want to force Evergreen to treat the
603 hostname as `localhost`; if you configured `opensrf.xml` using the real
604 hostname of your machine as returned by `perl -ENet::Domain 'print
605 Net::Domain::hostfqdn() . "\n";'`, you should not use the `-l` flag.
608 ------------------------------------------------------------------------------
609 osrf_control -l --start-all
610 ------------------------------------------------------------------------------
612 ** If you receive the error message `bash: osrf_control: command not found`,
613 then your environment variable `PATH` does not include the `/openils/bin`
614 directory; this should have been set in the *opensrf* Linux account's
615 `.bashrc` configuration file. To manually set the `PATH` variable, edit the
616 configuration file `~/.bashrc` as the *opensrf* Linux account and add the
620 ------------------------------------------------------------------------------
621 export PATH=$PATH:/openils/bin
622 ------------------------------------------------------------------------------
624 3. As the *opensrf* Linux account, generate the Web files needed by the staff
625 client and catalogue and update the organization unit proximity (you need to do
626 this the first time you start Evergreen, and after that each time you change the library org unit configuration.
630 ------------------------------------------------------------------------------
632 ------------------------------------------------------------------------------
634 4. As the *root* Linux account, restart the Apache Web server:
637 ------------------------------------------------------------------------------
638 /etc/init.d/apache2 restart
639 ------------------------------------------------------------------------------
641 If the Apache Web server was running when you started the OpenSRF services, you
642 might not be able to successfully log in to the OPAC or staff client until the
643 Apache Web server is restarted.
645 Testing connections to Evergreen
646 --------------------------------
648 Once you have installed and started Evergreen, test your connection to
649 Evergreen via `srfsh`. As the *opensrf* Linux account, issue the following
650 commands to start `srfsh` and try to log onto the Evergreen server using the
651 *egadmin* Evergreen administrator user name and password that you set using the
652 `eg_db_config` command:
655 ------------------------------------------------------------------------------
657 srfsh% login <admin-user> <admin-pass>
658 ------------------------------------------------------------------------------
660 You should see a result like:
662 Received Data: "250bf1518c7527a03249858687714376"
663 ------------------------------------
664 Request Completed Successfully
665 Request Time in seconds: 0.045286
666 ------------------------------------
670 "textcode":"SUCCESS",
673 "stacktrace":"oils_auth.c:304",
675 "authtoken":"e5f9827cc0f93b503a1cc66bee6bdd1a",
681 ------------------------------------
682 Request Completed Successfully
683 Request Time in seconds: 1.336568
684 ------------------------------------
685 [[install-troubleshooting-1]]
686 If this does not work, it's time to do some troubleshooting.
688 * As the *opensrf* Linux account, run the `settings-tester.pl` script to see
689 if it finds any system configuration problems. The script is found at
690 `Open-ILS/src/support-scripts/settings-tester.pl` in the Evergreen source
692 * Follow the steps in the http://evergreen-ils.org/dokuwiki/doku.php?id=troubleshooting:checking_for_errors[troubleshooting guide].
693 * If you have faithfully followed the entire set of installation steps
694 listed here, you are probably extremely close to a working system.
695 Gather your configuration files and log files and contact the
696 http://evergreen-ils.org/communicate/mailing-lists/[Evergreen development
697 mailing list] for assistance before making any drastic changes to your system
703 Need help installing or using Evergreen? Join the mailing lists at
704 http://evergreen-ils.org/communicate/mailing-lists/ or contact us on the Freenode
705 IRC network on the #evergreen channel.
709 This work is licensed under the Creative Commons Attribution-ShareAlike 3.0
710 Unported License. To view a copy of this license, visit
711 http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative
712 Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.