[OPEN-ILS-DEV] Errors at testing stage of OpenSRF installation (OpenSRF trunk)

[Wiktor Rzeczkowski]

I had a similar experience on Fedora 9 early in 2009; findings are here:

http://www.mail-archive.com/open-ils-dev@list.georgialibraries.org/msg03030.html

Newer versions of ejabberd, such as those in Fedora 9 and Ubuntu 9.10, 
were incompatible with Evergreen. ejabberd v. 2.0.2 (max) was compatible.


Wiktor Rzeczkowski
McMaster University

On Sat, 2 Jan 2010, Soulliere, Robert wrote:

> Hi Bradley,
>
> If you haven't tried already, you might want to stop and restart ejabberd and memcahced before restarting opensrf. I found that sometimes ejabberd stalls and needs to be restarted before opensrf can start. I had similar errors and resolved them with an ejabberd restart.
>
> Robert
>
> ________________________________________
> From: open-ils-dev-bounces at list.georgialibraries.org [open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of Bradley Peters [bdp+eg at moberley.com]
> Sent: January 1, 2010 2:42 PM
> To: open-ils-dev at list.georgialibraries.org
> Subject: [OPEN-ILS-DEV] Errors at testing stage of OpenSRF installation (OpenSRF trunk)
>
> I have been attempting to set up an installation of Evergreen on
> Ubuntu 9.10 but have run into some difficulty with OpenSRF. I used a
> checkout from trunk (1879) because 1.2.0 didn't have a prerequisites
> target for ubuntu-karmic whereas trunk did.
>
> I followed the instructions on the wiki [1] for 1.2.0, except for the
> configure program. I changed the prefix to install in /opt/openils. I
> have not yet retried the installation with the /openils prefix.
>
>  $ ./configure --prefix=/opt/openils --sysconfdir=/opt/openils/conf
> --enable-python
>
> At the testing connection step, srfsh was unable to communicate and
> returned this message:
>
>  srfsh# request opensrf.math add 2 2
>  Unable to communicate with service opensrf.math
>
> I tested this with both the public.localhost and private.localhost
> servers in the srfsh.xml file and got the same response.
>
> I went through the troubleshooting steps on the wiki [2] and it
> appears the problem is occurring with the OpenSRF C part. First off,
> when I noticed that OpenSRF C was not running but the other parts
> apparently were running when I ran the stop_all command.
>
>  $ /opt/openils/bin/osrf_ctl.sh -c /opt/openils/conf/opensrf_core.xml
> -l -a stop_all
>  OpenSRF C not running
>  Stopping OpenSRF Perl
>  * stopping all services for localhost
>  * stopping service pid=8921 opensrf.persist
>  * stopping service pid=8910 opensrf.settings
>  Stopping OpenSRF Router process 8863 8864...
>
> I ran the three separate start commands as documented on the
> troubleshooting wiki. I did not find any errors on the first 2 steps
> (start_router and start_perl). However, the start_c step did produce
> some errors in the logs.
>
>  $ /opt/openils/bin/osrf_ctl.sh -c /opt/openils/conf/opensrf_core.xml
> -l -a start_c
>  Starting OpenSRF C (host=localhost)
>  opensrf at ichabod:/opt/openils$ grep ERR
> var/log/*.logvar/log/osrfsys.log:opensrf 2010-01-01 13:31:34 [ERR
> :14047:osrf_settings.c:117:] No osrfMessage received from host
> localhost (timeout?)
>  var/log/osrfsys.log:opensrf 2010-01-01 13:31:34 [ERR
> :14047:osrf_settings.c:136:] Unable to load config for host localhost
>  var/log/osrfsys.log:opensrf 2010-01-01 13:31:34 [ERR
> :14047:osrf_system.c:105:] Unable to retrieve settings for host
> localhost from configuration file /opt/openils/conf/opensrf_core.xml
>  var/log/osrfsys.log:opensrf 2010-01-01 13:31:34 [ERR
> :14047:opensrf.c:23:] Server Loop returned an error condition, exiting
> with -1
>
> Per the instructions on the troubleshooting page I am sending this
> report and copies of my log files to open-ils-dev. What is my next
> step?
>
> Sincerely,
> Bradley Peters
>
> 1. http://www.open-ils.org/dokuwiki/doku.php?id=opensrf:1.2:install
> 2. http://evergreen-ils.org/dokuwiki/doku.php?id=troubleshooting:checking_for_errors
>
> This E-mail contains privileged and confidential information intended
> only for the individual or entity named in the message.  If the reader
> of this message is not the intended recipient, or the agent responsible
> to deliver it to the intended recipient, you are hereby notified that
> any review, dissemination, distribution or copying of this communication
> is prohibited.  If this communication was received in error, please
> notify the sender by reply E-mail immediately, and delete and destroy
> the original message.
>