1 = Installing the Evergreen server =
4 == Preamble: referenced user accounts ==
6 In subsequent sections, we will refer to a number of different accounts, as
10 ** The *user* Linux account is the account that you use to log onto the
11 Linux system as a regular user.
12 ** The *root* Linux account is an account that has system administrator
13 privileges. On Debian you can switch to this account from
14 your *user* account by issuing the `su -` command and entering the
15 password for the *root* account when prompted. On Ubuntu you can switch
16 to this account from your *user* account using the `sudo su -` command
17 and entering the password for your *user* account when prompted.
18 ** The *opensrf* Linux account is an account that you create when installing
19 OpenSRF. You can switch to this account from the *root* account by
20 issuing the `su - opensrf` command.
21 ** The *postgres* Linux account is created automatically when you install
22 the PostgreSQL database server. You can switch to this account from the
23 *root* account by issuing the `su - postgres` command.
24 * PostgreSQL user accounts:
25 ** The *evergreen* PostgreSQL account is a superuser account that you will
26 create to connect to the PostgreSQL database server.
27 * Evergreen administrator account:
28 ** The *egadmin* Evergreen account is an administrator account for
29 Evergreen that you will use to test connectivity and configure your
32 == Preamble: developer instructions ==
35 Skip this section if you are using an official release tarball downloaded
36 from http://evergreen-ils.org/egdownloads
38 Developers working directly with the source code from the Git repository,
39 rather than an official release tarball, must perform one step before they
40 can proceed with the `./configure` step.
42 As the *user* Linux account, issue the following command in the Evergreen
43 source directory to generate the configure script and Makefiles:
46 ------------------------------------------------------------------------------
48 ------------------------------------------------------------------------------
50 == Installing prerequisites ==
52 * **PostgreSQL**: The minimum supported version is 10.
53 * **Linux**: Evergreen has been tested on
56 Ubuntu Jammy Jellyfish (22.04),
57 and Ubuntu Focal Fossa (20.04).
58 If you are running an older version of these distributions, you may want
59 to upgrade before upgrading Evergreen. For instructions on upgrading these
60 distributions, visit the Debian or Ubuntu websites.
61 * **OpenSRF**: The minimum supported version of OpenSRF is 3.2.0.
64 Evergreen has a number of prerequisite packages that must be installed
65 before you can successfully configure, compile, and install Evergreen.
67 1. Begin by installing the most recent version of OpenSRF (3.2.0 or later).
68 You can download OpenSRF releases from http://evergreen-ils.org/opensrf-downloads/
70 2. Issue the following commands as the *root* Linux account to install
71 prerequisites using the `Makefile.install` prerequisite installer,
72 substituting `debian-bullseye`,`debian-buster`,`ubuntu-jammy`,
73 or `ubuntu-focal` for <osname> below:
77 ------------------------------------------------------------------------------
78 make -f Open-ILS/src/extras/Makefile.install <osname>
79 ------------------------------------------------------------------------------
81 [[optional_developer_additions]]
82 3. OPTIONAL: Developer additions
84 To perform certain developer tasks from a Git source code checkout,
85 additional packages are required. As the *root* Linux account:
87 * To install packages needed for retrieving and managing web dependencies,
88 use the <osname>-developer Makefile.install target. Currently,
89 this is only needed for building and installing the web
91 * To optionally run Angular and AngularJS tests you will need to manually
92 install Firefox and your choice of Chromium or Chrome.
95 ------------------------------------------------------------------------------
96 make -f Open-ILS/src/extras/Makefile.install <osname>-developer
97 ------------------------------------------------------------------------------
99 * To install packages required for building Evergreen translations, use
100 the <osname>-translator Makefile.install target.
103 ------------------------------------------------------------------------------
104 make -f Open-ILS/src/extras/Makefile.install <osname>-translator
105 ------------------------------------------------------------------------------
107 * To install packages required for building Evergreen release bundles, use
108 the <osname>-packager Makefile.install target.
111 ------------------------------------------------------------------------------
112 make -f Open-ILS/src/extras/Makefile.install <osname>-packager
113 ------------------------------------------------------------------------------
115 == Extra steps for web staff client ==
118 Skip this entire section if you are using an official release tarball downloaded
119 from http://evergreen-ils.org/downloads. Otherwise, ensure you have installed the
120 xref:#optional_developer_additions[optional developer additions] before proceeding.
122 [[install_files_for_web_staff_client]]
123 === Install AngularJS files for web staff client ===
125 1. Building, Testing, Minification: The remaining steps all take place within
126 the staff JS web root:
129 ------------------------------------------------------------------------------
130 cd $EVERGREEN_ROOT/Open-ILS/web/js/ui/default/staff/
131 ------------------------------------------------------------------------------
133 2. Install Project-local Dependencies. npm inspects the 'package.json' file
134 for dependencies and fetches them from the Node package network.
137 ------------------------------------------------------------------------------
138 npm install # fetch JS dependencies
139 ------------------------------------------------------------------------------
141 3. Run the build script.
144 ------------------------------------------------------------------------------
146 ------------------------------------------------------------------------------
148 4. OPTIONAL: Test web client code if the <osname>-developer packages and
149 the necessary browsers are installed.
150 CHROME_BIN should be set to the path to chrome or chromimum, e.g.,
154 ------------------------------------------------------------------------------
155 CHROME_BIN=/path/to/chrome npm run test
156 ------------------------------------------------------------------------------
158 [[install_files_for_angular_web_staff_client]]
159 === Install Angular files for web staff client ===
161 1. Building, Testing, Minification: The remaining steps all take place within
162 the Angular staff root:
165 ------------------------------------------------------------------------------
166 cd $EVERGREEN_ROOT/Open-ILS/src/eg2/
167 ------------------------------------------------------------------------------
169 2. Install Project-local Dependencies. npm inspects the 'package.json' file
170 for dependencies and fetches them from the Node package network.
173 ------------------------------------------------------------------------------
174 npm install # fetch JS dependencies
175 ------------------------------------------------------------------------------
177 3. Run the build script.
180 ------------------------------------------------------------------------------
181 ng build --configuration=production
182 ------------------------------------------------------------------------------
184 This can be a memory-intensive build. If the process does not finish, and you
185 get the message "Killed" in the console, try running it with
186 https://nodejs.org/api/cli.html#cli_max_old_space_size_size_in_megabytes[an explicit max-old-space-size option]
187 to encourage more garbage collection. For example, on a machine with 4GB of
188 memory, you can limit max-old-space-size to 3GB with:
191 ------------------------------------------------------------------------------
192 NODE_OPTIONS=--max-old-space-size=3072 ng build --configuration=production
193 ------------------------------------------------------------------------------
195 4. OPTIONAL: Test eg2 web client code if the <osname>-developer packages and
196 the necessary browsers are installed:
197 CHROME_BIN should be set to the path to chrome or chromimum, e.g.,
201 ------------------------------------------------------------------------------
202 CHROME_BIN=/path/to/chrome npm run test
203 ------------------------------------------------------------------------------
205 [[install_opac_deps]]
206 === Install OPAC skin dependencies ===
208 1. The following steps take place within the OPAC dependencies root:
211 ------------------------------------------------------------------------------
212 cd $EVERGREEN_ROOT/Open-ILS/web/opac/deps
213 ------------------------------------------------------------------------------
215 2. Install Project-local Dependencies. npm inspects the 'package.json' file
216 for dependencies and fetches them from the Node package network.
219 ------------------------------------------------------------------------------
220 npm install # fetch JS and CSS dependencies
221 ------------------------------------------------------------------------------
223 Note that there is no build step.
225 == Configuration and compilation instructions ==
227 For the time being, we are still installing everything in the `/openils/`
228 directory. From the Evergreen source directory, issue the following commands as
229 the *user* Linux account to configure and build Evergreen:
232 ------------------------------------------------------------------------------
233 PATH=/openils/bin:$PATH ./configure --prefix=/openils --sysconfdir=/openils/conf
235 ------------------------------------------------------------------------------
237 These instructions assume that you have also installed OpenSRF under `/openils/`.
238 If not, please adjust PATH as needed so that the Evergreen `configure` script
239 can find `osrf_config`.
241 == Installation instructions ==
243 1. Once you have configured and compiled Evergreen, issue the following
244 command as the *root* Linux account to install Evergreen and copy
245 example configuration files to `/openils/conf`.
248 ------------------------------------------------------------------------------
250 ------------------------------------------------------------------------------
252 == Change ownership of the Evergreen files ==
254 All files in the `/openils/` directory and subdirectories must be owned by the
255 `opensrf` user. Issue the following command as the *root* Linux account to
256 change the ownership on the files:
259 ------------------------------------------------------------------------------
260 chown -R opensrf:opensrf /openils
261 ------------------------------------------------------------------------------
265 On Ubuntu or Debian, run the following command as the root user:
268 ------------------------------------------------------------------------------
270 ------------------------------------------------------------------------------
272 == Additional Instructions for Developers ==
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 ==
294 . Use the example configuration files to configure your Web server for
295 the Evergreen catalog, web staff client, Web services, and administration
296 interfaces. Issue the following commands as the *root* Linux account:
299 ------------------------------------------------------------------------------------
300 cp Open-ILS/examples/apache_24/eg_24.conf /etc/apache2/sites-available/eg.conf
301 cp Open-ILS/examples/apache_24/eg_vhost_24.conf /etc/apache2/eg_vhost.conf
302 cp Open-ILS/examples/apache_24/eg_startup /etc/apache2/
304 mkdir /etc/apache2/ssl
306 ------------------------------------------------------------------------------------
308 . The `openssl` command cuts a new SSL key for your Apache server. For a
309 production server, you should purchase a signed SSL certificate, but you can
310 just use a self-signed certificate and accept the warnings in the
311 and browser during testing and development. Create an SSL key for the Apache
312 server by issuing the following command as the *root* Linux account:
315 ------------------------------------------------------------------------------
316 openssl req -new -x509 -days 365 -nodes -out server.crt -keyout server.key
317 ------------------------------------------------------------------------------
319 . As the *root* Linux account, edit the `eg.conf` file that you copied into
321 a. To enable access to the offline upload / execute interface from any
322 workstation on any network, make the following change (and note that
323 you *must* secure this for a production instance):
324 * Replace `Require host 10.0.0.0/8` with `Require all granted`
325 . Change the user for the Apache server.
326 * As the *root* Linux account, edit
327 `/etc/apache2/envvars`. Change `export APACHE_RUN_USER=www-data` to
328 `export APACHE_RUN_USER=opensrf`.
329 . As the *root* Linux account, configure Apache with KeepAlive settings
330 appropriate for Evergreen. Higher values can improve the performance of a
331 single client by allowing multiple requests to be sent over the same TCP
332 connection, but increase the risk of using up all available Apache child
333 processes and memory.
334 * Edit `/etc/apache2/apache2.conf`.
335 a. Change `KeepAliveTimeout` to `1`.
336 b. Change `MaxKeepAliveRequests` to `100`.
337 . As the *root* Linux account, configure the prefork module to start and keep
338 enough Apache servers available to provide quick responses to clients without
339 running out of memory. The following settings are a good starting point for a
340 site that exposes the default Evergreen catalog to the web:
342 .`/etc/apache2/mods-available/mpm_prefork.conf`
344 ------------------------------------------------------------------------------
345 <IfModule mpm_prefork_module>
350 MaxConnectionsPerChild 500
352 ------------------------------------------------------------------------------
354 . As the *root* user, enable the mpm_prefork module:
357 ------------------------------------------------------------------------------
360 ------------------------------------------------------------------------------
362 . As the *root* Linux account, enable the Evergreen site:
365 ------------------------------------------------------------------------------
366 a2dissite 000-default # OPTIONAL: disable the default site (the "It Works" page)
368 ------------------------------------------------------------------------------
370 . As the *root* Linux account, enable Apache to write
371 to the lock directory; this is currently necessary because Apache
372 is running as the `opensrf` user:
375 ------------------------------------------------------------------------------
376 chown opensrf /var/lock/apache2
377 ------------------------------------------------------------------------------
379 Learn more about additional Apache options in the following sections:
381 * xref:admin:apache_rewrite_tricks.adoc#apache_rewrite_tricks[Apache Rewrite Tricks]
382 * xref:admin:apache_access_handler.adoc#apache_access_handler_perl_module[Apache Access Handler Perl Module]
384 == Configure OpenSRF for the Evergreen application ==
386 There are a number of example OpenSRF configuration files in `/openils/conf/`
387 that you can use as a template for your Evergreen installation. Issue the
388 following commands as the *opensrf* Linux account:
391 ------------------------------------------------------------------------------
392 cp -b /openils/conf/opensrf_core.xml.example /openils/conf/opensrf_core.xml
393 cp -b /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml
394 ------------------------------------------------------------------------------
396 When you installed OpenSRF, you created four Jabber users on two
397 separate domains and edited the `opensrf_core.xml` file accordingly. Please
398 refer back to the OpenSRF README and, as the *opensrf* Linux account, edit the
399 Evergreen version of the `opensrf_core.xml` file using the same Jabber users
400 and domains as you used while installing and testing OpenSRF.
403 The `-b` flag tells the `cp` command to create a backup version of the
404 destination file. The backup version of the destination file has a tilde (`~`)
405 appended to the file name, so if you have forgotten the Jabber users and
406 domains, you can retrieve the settings from the backup version of the files.
408 `eg_db_config`, described in xref:#creating_the_evergreen_database[Creating the Evergreen database], sets the database connection information in `opensrf.xml` for you.
410 === Configure action triggers for the Evergreen application ===
411 _Action Triggers_ provide hooks for the system to perform actions when a given
412 event occurs; for example, to generate reminder or overdue notices, the
413 `checkout.due` hook is processed and events are triggered for potential actions
414 if there is no checkin time.
416 To enable the default set of hooks, issue the following command as the
417 *opensrf* Linux account:
420 ------------------------------------------------------------------------------
421 cp -b /openils/conf/action_trigger_filters.json.example /openils/conf/action_trigger_filters.json
422 ------------------------------------------------------------------------------
424 For more information about configuring and running action triggers, see
425 xref:admin:actiontriggers_process.adoc#processing_action_triggers[Notifications / Action Triggers].
427 [[creating_the_evergreen_database]]
428 == Creating the Evergreen database ==
430 === Setting up the PostgreSQL server ===
432 For production use, most libraries install the PostgreSQL database server on a
433 dedicated machine. Therefore, by default, the `Makefile.install` prerequisite
434 installer does *not* install the PostgreSQL database server that is required
435 by every Evergreen system. You can install the packages required by Debian or
436 Ubuntu on the machine of your choice using the following commands as the
437 *root* Linux account:
439 . Installing PostgreSQL server packages
441 Each OS build target provides the postgres server installation
442 packages required for each operating system. To install Postgres
443 server packages, use the make target
444 'postgres-server-<OSTYPE>-<POSTGRESVERSION>'. Choose the most
445 appropriate command below based on your operating system and desired
448 The first below will install PostgreSQL 10, the minimum supported
449 version and the version recommended for production use of Evergreen:
452 ------------------------------------------------------------------------------
453 make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-bullseye-10
454 make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-buster-10
455 make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-focal-10
456 make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-jammy-10
457 ------------------------------------------------------------------------------
461 Evergreen support for PostgreSQL server versions greater than 10 is
462 still exprimental. The use of the following is discouraged in
463 production environments. The following are only recommended if you
464 are willing to test newer PostgreSQL versions for performance and
468 To install PostgreSQL version 11, use the following command for your operating
472 ------------------------------------------------------------------------------
473 make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-bullseye-11
474 make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-buster-11
475 make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-focal-11
476 make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-jammy-11
477 ------------------------------------------------------------------------------
479 To install PostgreSQL version 12, use the following command for your operating
483 ------------------------------------------------------------------------------
484 make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-bullseye-12
485 make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-buster-12
486 make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-focal-12
487 make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-jammy-12
488 ------------------------------------------------------------------------------
490 To install PostgreSQL version 13, use the following command for your operating
494 ------------------------------------------------------------------------------
495 make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-bullseye-13
496 make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-buster-13
497 make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-focal-13
498 make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-jammy-13
499 ------------------------------------------------------------------------------
501 To install PostgreSQL version 14, use the following command for your operating
505 ------------------------------------------------------------------------------
506 make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-bullseye-14
507 make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-buster-14
508 make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-focal-14
509 make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-jammy-14
510 ------------------------------------------------------------------------------
512 To install PostgreSQL version 15, use the following command for your operating
516 ------------------------------------------------------------------------------
517 make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-bullseye-15
518 make -f Open-ILS/src/extras/Makefile.install postgres-server-debian-buster-15
519 make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-focal-15
520 make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-jammy-15
521 ------------------------------------------------------------------------------
523 For a standalone PostgreSQL server, install the following Perl modules for your
524 distribution as the *root* Linux account:
527 No extra modules required for these distributions.
529 You need to create a PostgreSQL superuser to create and access the database.
530 Issue the following command as the *postgres* Linux account to create a new
531 PostgreSQL superuser named `evergreen`. When prompted, enter the new user's
535 ------------------------------------------------------------------------------
536 createuser -s -P evergreen
537 ------------------------------------------------------------------------------
539 .Enabling connections to the PostgreSQL database
541 Your PostgreSQL database may be configured by default to prevent connections,
542 for example, it might reject attempts to connect via TCP/IP or from other
543 servers. To enable TCP/IP connections from localhost, check your `pg_hba.conf`
544 file, found in the `/etc/postgresql/` directory on Debian and Ubuntu.
545 A simple way to enable TCP/IP
546 connections from localhost to all databases with password authentication, which
547 would be suitable for a test install of Evergreen on a single server, is to
548 ensure the file contains the following entries _before_ any "host ... ident"
551 ------------------------------------------------------------------------------
552 host all all ::1/128 md5
553 host all all 127.0.0.1/32 md5
554 ------------------------------------------------------------------------------
556 When you change the `pg_hba.conf` file, you will need to reload PostgreSQL to
557 make the changes take effect. For more information on configuring connectivity
559 http://www.postgresql.org/docs/devel/static/auth-pg-hba-conf.html
561 === Creating the Evergreen database and schema ===
563 Once you have created the *evergreen* PostgreSQL account, you also need to
564 create the database and schema, and configure your configuration files to point
565 at the database server. Issue the following command as the *root* Linux account
566 from inside the Evergreen source directory, replacing <user>, <password>,
567 <hostname>, <port>, and <dbname> with the appropriate values for your
568 PostgreSQL database (where <user> and <password> are for the *evergreen*
569 PostgreSQL account you just created), and replace <admin-user> and <admin-pass>
570 with the values you want for the *egadmin* Evergreen administrator account:
573 ------------------------------------------------------------------------------
574 perl Open-ILS/src/support-scripts/eg_db_config --update-config \
575 --service all --create-database --create-schema --create-offline \
576 --user <user> --password <password> --hostname <hostname> --port <port> \
577 --database <dbname> --admin-user <admin-user> --admin-pass <admin-pass>
578 ------------------------------------------------------------------------------
580 This creates the database and schema and configures all of the services in
581 your `/openils/conf/opensrf.xml` configuration file to point to that database.
582 It also creates the configuration files required by the Evergreen `cgi-bin`
583 administration scripts, and sets the user name and password for the *egadmin*
584 Evergreen administrator account to your requested values.
586 You can get a complete set of options for `eg_db_config` by passing the
589 === Loading sample data ===
591 If you add the `--load-all-sample` parameter to the `eg_db_config` command,
592 a set of authority and bibliographic records, call numbers, copies, staff
593 and regular users, and transactions will be loaded into your target
594 database. This sample dataset is commonly referred to as the _concerto_
595 sample data, and can be useful for testing out Evergreen functionality and
596 for creating problem reports that developers can easily recreate with their
597 own copy of the _concerto_ sample data.
599 === Creating the database on a remote server ===
601 In a production instance of Evergreen, your PostgreSQL server should be
602 installed on a dedicated server.
604 To create the database instance on a remote database server, simply
605 use the `--create-database` flag on `eg_db_config`.
607 == Starting Evergreen ==
609 1. As the *root* Linux account, start the `memcached` and `ejabberd` services
610 (if they aren't already running):
613 ------------------------------------------------------------------------------
614 /etc/init.d/ejabberd start
615 /etc/init.d/memcached start
616 ------------------------------------------------------------------------------
618 2. As the *opensrf* Linux account, start Evergreen. The `-l` flag in the
619 following command is only necessary if you want to force Evergreen to treat the
620 hostname as `localhost`; if you configured `opensrf.xml` using the real
621 hostname of your machine as returned by `perl -ENet::Domain 'print
622 Net::Domain::hostfqdn() . "\n";'`, you should not use the `-l` flag.
625 ------------------------------------------------------------------------------
626 osrf_control -l --start-all
627 ------------------------------------------------------------------------------
629 ** If you receive the error message `bash: osrf_control: command not found`,
630 then your environment variable `PATH` does not include the `/openils/bin`
631 directory; this should have been set in the *opensrf* Linux account's
632 `.bashrc` configuration file. To manually set the `PATH` variable, edit the
633 configuration file `~/.bashrc` as the *opensrf* Linux account and add the
637 ------------------------------------------------------------------------------
638 export PATH=$PATH:/openils/bin
639 ------------------------------------------------------------------------------
641 3. As the *opensrf* Linux account, generate the Web files needed by the web staff
642 client and catalog and update the organization unit proximity (you need to do
643 this the first time you start Evergreen, and after that each time you change the library org unit configuration.
647 ------------------------------------------------------------------------------
649 ------------------------------------------------------------------------------
651 4. As the *root* Linux account, restart the Apache Web server:
654 ------------------------------------------------------------------------------
655 /etc/init.d/apache2 restart
656 ------------------------------------------------------------------------------
658 If the Apache Web server was running when you started the OpenSRF services, you
659 might not be able to successfully log in to the OPAC or web staff client until the
660 Apache Web server is restarted.
662 == Testing connections to Evergreen ==
664 Once you have installed and started Evergreen, test your connection to
665 Evergreen via `srfsh`. As the *opensrf* Linux account, issue the following
666 commands to start `srfsh` and try to log onto the Evergreen server using the
667 *egadmin* Evergreen administrator user name and password that you set using the
668 `eg_db_config` command:
671 ------------------------------------------------------------------------------
673 srfsh% login <admin-user> <admin-pass>
674 ------------------------------------------------------------------------------
676 You should see a result like:
678 Received Data: "250bf1518c7527a03249858687714376"
679 ------------------------------------
680 Request Completed Successfully
681 Request Time in seconds: 0.045286
682 ------------------------------------
686 "textcode":"SUCCESS",
689 "stacktrace":"oils_auth.c:304",
691 "authtoken":"e5f9827cc0f93b503a1cc66bee6bdd1a",
697 ------------------------------------
698 Request Completed Successfully
699 Request Time in seconds: 1.336568
700 ------------------------------------
701 [[install-troubleshooting-1]]
702 If this does not work, it's time to do some troubleshooting.
704 * As the *opensrf* Linux account, run the `settings-tester.pl` script to see
705 if it finds any system configuration problems. The script is found at
706 `Open-ILS/src/support-scripts/settings-tester.pl` in the Evergreen source
708 * Follow the steps in the http://evergreen-ils.org/dokuwiki/doku.php?id=troubleshooting:checking_for_errors[troubleshooting guide].
709 * If you have faithfully followed the entire set of installation steps
710 listed here, you are probably extremely close to a working system.
711 Gather your configuration files and log files and contact the
712 http://evergreen-ils.org/communicate/mailing-lists/[Evergreen development
713 mailing list] for assistance before making any drastic changes to your system
718 Need help installing or using Evergreen? Join the mailing lists at
719 http://evergreen-ils.org/communicate/mailing-lists/ or contact us on the Freenode
720 IRC network on the #evergreen channel.
724 This work is licensed under the Creative Commons Attribution-ShareAlike 3.0
725 Unported License. To view a copy of this license, visit
726 http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative
727 Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.