Troubleshooting System ErrorsIf you have Evergreen installed and are encountering systematic errors, here is the steps to find the
cause and solution to most problems. These instructions assume standard locations and file names for Evergreen
installations, and may also include commands for specific Linux distributions.Systematic Evergreen Restart to Isolate ErrorsStop Apache:web serverApachestopping/etc/init.d/apache2 stoporapache2ctl stopStop OpenSRF:OpenSRFosrf_ctl.sh -l -a stop_allYou should get either output simlar to this:
Stopping OpenSRF C process 12515...
Stopping OpenSRF C process 12520...
Stopping OpenSRF C process 12526...
Stopping OpenSRF Perl process 12471...
Stopping OpenSRF Router process 12466...
Or, if services have already been stopped, output may look like this:OpenSRF C not runningOpenSRF Perl not runningOpenSRF Router not runningOccasionally osrf_ctl.sh fails to kill OpenSRF processes, so we should check to make
sure that none are still running with the command:ps -aef | grep OpenSRFYou should manually kill any OpenSRF processes.If you were unable to stop OpenSRF with the above methods, you could also try this
command:rm –R /openils/var/run/*.pidThis will remove the temporary OpenSRF process files from the run directory which may
have been left over from a previous system boot cycle.Restart Ejabberd and
Memcached with the following commands:Ejabberdsudo /etc/init.d/ejabberd restartsudo /etc/init.d/memcached restartmemcachedStart the OpenSRF router and check for errorsOpenSRFservicesrouter/openils/bin/osrf_ctl.sh -l -a start_routerIf the router started correctly, output will be:Starting OpenSRF RouterIf router does not start correctly, you should check the router error log files
for error information.Evergreen 1.6 uses two routers, a public one and a private one, with two different
logfiles:/openils/var/log/private.router.loglogsrouter/openils/var/log/public.router.logA quick way to find error information in the logs is with the grep command.grep ERR /openils/var/log/*router.logAs a final sanity check, look for router processes using the process status
command:ps -aef | grep RouterStart the OpenSRF perl services and check for errorsOpenSRFservicesperl/openils/bin/osrf_ctl.sh -l -a start_perlYou should see the output similar to the following:
Starting OpenSRF Perl
* starting all services for ...
* starting service pid=7484 opensrf.settings
* starting service pid=7493 open-ils.cat
* starting service pid=7495 open-ils.supercat
* starting service pid=7497 open-ils.search
* starting service pid=7499 open-ils.circ
* starting service pid=7501 open-ils.actor
* starting service pid=7502 open-ils.storage
...
If the perl services do not start correctly or you receive errors, search for errors
in the following log files:/openils/var/log/router.log/openils/var/log/osrfsys.loglogsosrfsys.logAt this point you can use the grep command to find errors in
any of the Evergreen log files:grep ERR /openils/var/log/*.logAs a final sanity check, look for OpenSRF processes:ps -aef | grep -i opensrfStart the OpenSRF c services and check for errors:]
OpenSRFservicesC/openils/bin/osrf_ctl.sh -l -a start_cAnd output should be:Starting OpenSRF C (host=localhost)If the c service does not start, check for errors by grepping
the log files for errors:grep ERR /openils/var/log/*.logCheck for OpenSRF processes:ps -aef | grep -i opensrfSmoke test with autogen.shautogenThe autogen tool will take some dynamic information from the database and generate
static JavaScript JavaScript files for use by the OPAC and staff client. It is also able to refresh
the proximity mapproximity map between libraries for the purpose of efficiently routing hold
requests.As user opensrf, you invoke autogen with the command:/openils/bin/autogen.sh -c /openils/conf/opensrf_core.xml -uIf Autogen completes successfully, the output will be:
Updating fieldmapper
Updating web_fieldmapper
Updating OrgTree
removing OrgTree from the cache...
Updating OrgTree HTML
Updating locales selection HTML
Updating Search Groups
Refreshing proximity of org units
Successfully updated the organization proximity
Done
If Autogen does not complete its task and you receive errors, use
grep to find errors in the log files:grep ERR /openils/var/log/*.logConnect to Evergreen using the srfsh command-line OpenSRF clientsrfsh (command-line OpenSRF client)/openils/bin/srfshIn order for you to connect using srfsh, you will need to
have set up the .srfsh.xml configuration file in your home directory as as
described in the installation chapter.You will then see the srfsh prompt:srfsh#At the srfsh prompt, enter this command:login admin open-ilsYou should the request verification:
Received Data: "6f63ff5542da1fead4431c6c280efc75"
------------------------------------
Request Completed Successfully
Request Time in seconds: 0.018414
------------------------------------
Received Data: {
"ilsevent":0,
"textcode":"SUCCESS",
"desc":" ",
"pid":7793,
"stacktrace":"oils_auth.c:312",
"payload":{
"authtoken":"28804ebf99508496e2a4d2593aaa930e",
"authtime":420.000000
}
}
------------------------------------
Request Completed Successfully
Request Time in seconds: 0.552430
------------------------------------
Login Session: 28804. Session timeout: 420.000
srfsh#If you encounter errors or if you are unable to connect, you should consult the
srfsh.log file. The location of this file is configured in your logssrfsh.log.srfsh.xml configuration file and is
/openils/var/log/srfsh.log by default.Pressing
CtrlD
or entering exit will terminate srfsh.Start Apache and check for errors:web serverApachestarting/etc/init.d/apache2 startorapache2ctl startYou should see output:
* Starting web server apache2
...done.
the Apache OpenSRF modules write to the
/openils/var/log/gateway.loglogsgateway.logHowever, you should check all of the log files for errors:grep ERR /openils/var/log/*.logAnother place to check for errors is the Apache error logs
generally located in in the /var/log/Apache2logsApacheApachelogs
directoryIf you encounter errors with Apache, a common source of potential problems are the
Evergreen site configuration files /etc/apache2/eg_vhost.conf and
/etc/apache2/sites-available/eg.confconfiguration filesApacheeg.confconfiguration filesApacheeg_vhost.confTry to login from the staff clientTry to search the catalog from the OPAC