User Tools

Site Tools


troubleshooting:checking_for_errors

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
troubleshooting:checking_for_errors [2009/11/30 16:05] rsoullieretroubleshooting:checking_for_errors [2022/02/10 13:34] (current) – external edit 127.0.0.1
Line 1: Line 1:
 If you have Evergreen installed and are encountering systematic errors, here is how you might go about troubleshooting and gathering logs for others to troubleshoot.  These instructions assume standard locations and filenames for Evergreen installations, and may also include commands that assume a Debian or Ubuntu Linux operating system. If you have Evergreen installed and are encountering systematic errors, here is how you might go about troubleshooting and gathering logs for others to troubleshoot.  These instructions assume standard locations and filenames for Evergreen installations, and may also include commands that assume a Debian or Ubuntu Linux operating system.
 +
 +**NOTE:** This content is also available in the Evergreen documentation at http://docs.evergreen-ils.org/1.6/draft/html/. In github: http://github.com/rsoulliere/Evergreen-DocBook/blob/master/1.6/admin/troubleshooting.xml. 
  
 ===== Step 1: Stop all the OpenSRF services, as well as Apache ===== ===== Step 1: Stop all the OpenSRF services, as well as Apache =====
Line 46: Line 48:
 </code> </code>
  
-If you run into any troubles with stopping services, stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#openils-evergreen]].  Other tips may be available on this [[troubleshooting:checking_for_errors_step1|page]].+If you run into any troubles with stopping services, stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#evergreen]].  Other tips may be available on this [[troubleshooting:checking_for_errors_step1|page]].
  
 Occasionally, in the trunk/ version of Evergreen, I have seen osrf_ctl.sh fail to kill OpenSRF processes, so we should check to make sure that none are still running with a command like this:  Occasionally, in the trunk/ version of Evergreen, I have seen osrf_ctl.sh fail to kill OpenSRF processes, so we should check to make sure that none are still running with a command like this: 
Line 116: Line 118:
 rm –R /openils/var/run/*.pid rm –R /openils/var/run/*.pid
 </code> </code>
-This will remove the temporary OpenSRF process files from the run directory which may have been left over from a previous reboot.+This will remove the temporary OpenSRF process files from the run directory which may have been left over from a previous shutdown of the system.
  
  
Line 159: Line 161:
 </code> </code>
  
-If you have trouble getting memcached and apache running, stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#openils-evergreen]].  There may also be tips available on this [[troubleshooting:checking_for_errors_step3|page]].+If you have trouble getting memcached and apache running, stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#evergreen]].
  
  
Line 185: Line 187:
 </code> </code>
  
-If we get really desperate with troubleshooting, we may want to use a loglevel of 5, instead.  And if we narrow things down to the database, we might want to change the logging options for Postgres as well, but I'll defer such tinkering to this [[troubleshooting:checking_for_errors_step4|page]].  If you run into trouble changing these settings, please stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#openils-evergreen]].+If we get really desperate with troubleshooting, we may want to use a loglevel of 5, instead.  And if we narrow things down to the database, we might want to change the logging options for Postgres as well, but I'll defer such tinkering to this [[troubleshooting:checking_for_errors_step4|page]].  If you run into trouble changing these settings, please stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#evergreen]].
  
 ===== Step 5: Start the OpenSRF router and check for errors ===== ===== Step 5: Start the OpenSRF router and check for errors =====
Line 198: Line 200:
 </code> </code>
  
-If you do not, then please stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#openils-evergreen]].  There may also be tips available on this [[troubleshooting:checking_for_errors_step_5|page]].  We will want to see a copy of your router log and configuration files here:+If you do not, then please stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#evergreen]].  We will want to see a copy of your router log and configuration files here:
 <code> <code>
 /openils/var/log/router.log /openils/var/log/router.log
Line 268: Line 270:
 </code> </code>
  
-If you do not, then please stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#openils-evergreen]].  There may also be tips available on this [[troubleshooting:checking_for_errors_step_6|page]].  At a minimum, we will want to see a copy of your router log, osrfsys log and configuration files here:+If you do not, then please stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#evergreen]].  At a minimum, we will want to see a copy of your router log, osrfsys log and configuration files here:
 <code> <code>
 /openils/var/log/router.log /openils/var/log/router.log
Line 381: Line 383:
 </code> </code>
  
-If you do not, then please stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#openils-evergreen]].  There may also be tips available on this [[troubleshooting:checking_for_errors_step_7|page]].  At a minimum, we will want to see a copy of your router log, osrfsys log and configuration files here:+If you do not, then please stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#evergreen]]. At a minimum, we will want to see a copy of your router log, osrfsys log and configuration files here:
 <code> <code>
 /openils/var/log/*router.log /openils/var/log/*router.log
Line 442: Line 444:
 </code> </code>
  
-If you encounter any issues with Autogen, then please stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#openils-evergreen]].  There may also be tips available on this [[troubleshooting:checking_for_errors_step_8|page]].  We will be interested in the usual log and configuration files:+If you encounter any issues with Autogen, then please stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#evergreen]].   We will be interested in the usual log and configuration files:
 <code> <code>
 /openils/var/log/*.log /openils/var/log/*.log
Line 460: Line 462:
 srfsh# srfsh#
 </code> </code>
-If it does not, then please stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#openils-evergreen]].  There may also be tips available on this [[troubleshooting:checking_for_errors_step_9|page]].  At a minimum, we will want to see a copy of your router log, osrfsys log and configuration files here:+If it does not, then please stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#evergreen]].   At a minimum, we will want to see a copy of your router log, osrfsys log and configuration files here:
 <code> <code>
 /openils/var/log/*router.log /openils/var/log/*router.log
Line 472: Line 474:
 ~/.srfsh.xml ~/.srfsh.xml
 </code> </code>
-Assuming you have a srfsh prompt, enter this command:+Assuming you have a srfsh prompt, try logging in, **substituting the admin account credentials you created during the install process** into the following command:
 <code> <code>
-login admin open-ils+login myAdminUsername myAdminPassword
 </code> </code>
 You should see output similar to this: You should see output similar to this:
Line 557: Line 559:
 </code> </code>
  
-If you encounter any issues with Apache, then please stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#openils-evergreen]].  There may also be tips available on this [[troubleshooting:checking_for_errors_step_10|page]].  In addition to your normal log and configuration files, we'll also want to see some pertinent Apache configuration files:+If you encounter any issues with Apache, then please stop here and ask for help on either [[http://open-ils.org/listserv.php|OPEN-ILS-DEV]] or [[http://open-ils.org/irc.php|#evergreen]].   In addition to your normal log and configuration files, we'll also want to see some pertinent Apache configuration files:
 <code> <code>
 /etc/apache2/eg_vhost.conf /etc/apache2/eg_vhost.conf
Line 574: Line 576:
 ===== Step 12: Try to authenticate with the OPAC ===== ===== Step 12: Try to authenticate with the OPAC =====
    
 +===== Bonus Step: Checking Ejabberd Account Credentials =====
  
 +You may have an ejabberd account problem, if you see an error like:
 +
 +<code>
 +Checking Jabber connection for user router, domain public.localhost
 +Use of uninitialized value $@ in concatenation (.) or string at /usr/local/share/perl/5.10.1/OpenSRF/Transport/SlimJabber/Client.pm line 147, <DATA> line 35.
 +* Error connecting to jabber:
 +SCALAR(0x1244e20)
 +</code>
 +
 +Verify that the username/password combinations are set correctly in opensrf_core.xml, but you can also check with ejabberd to make sure that they were setup correctly in the first place.
 +
 +As root:
 +
 +<code>
 +ejabberdctl check_password <user> <host> <password>; echo $?
 +</code>
 +
 +If the result is 0, then things are fine with that username/password on the given host.  If the result is 1, then the credentials are not working.
 +
 +You can change your ejabberd password with:
 +
 +<code>
 +ejabberdctl change_password <user> <host> <new_password>
 +</code>
troubleshooting/checking_for_errors.1259615130.txt.gz · Last modified: 2022/02/10 13:33 (external edit)

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.