[OPEN-ILS-DEV] <SPAM-RBL> Opensrf install issues.

[Erik Mallory]

Okay, I goofed here, opensrf.math is in "C" so using the
opensrf-perl.pl to start it is wrong.

A few things I've noticed:
1.
On my system (RHEL 4 Update 7) there are two instances of the
opensrf-perl.pl that are chewing up CPU cycles.
6847 opensrf   25   0 22116  13m 1100 S 100.1  0.4   3:23.45
opensrf-perl.pl                                                 
 6857 opensrf   25   0 22116  13m 1100 R 99.8  0.4   3:19.82
opensrf-perl.pl 

2.
In about 15 minutes I get 2 MB of logging.. most of which is:

opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [WARN:6858:osrf_stack.c:30:]
transport_client had trouble reading from the socket..
opensrf 2009-03-24 15:26:20 [INFO:6858:osrf_app_session.c:167:]
Returning NULL from app_request_recv after timeout:
opensrf.settings.host_config.get ["apptest-504.wichita.edu"]
opensrf 2009-03-24 15:26:20 [ERR :6858:osrf_settings.c:48:] No
osrfMessage received from host apptest-504.wichita.edu (timeout?)
opensrf 2009-03-24 15:26:20 [ERR :6858:osrf_settings.c:67:] Unable to
load config for host apptest-504.wichita.edu
opensrf 2009-03-24 15:26:20 [ERR :6858:osrf_system.c:105:] Unable to
retrieve settings for host apptest-504.wichita.edu from configuration
file /u01/app/openils/conf/opensrf_core.xml
opensrf 2009-03-24 15:26:20 [ERR :6858:opensrf.c:23:] Server Loop
returned an error condition, exiting with -1
                         

-- 
Erik Mallory <Erik.Mallory at wichita.edu>
Wichita State 

On Tue, 2009-03-24 at 14:46 -0500, Erik Mallory wrote:
> (Addendum)
> I ran /u01/app/openils/bin/opensrf-perl.pl \
> --pid-dir /u01/app/openils/var/run/ \
> --config /u01/app/openils/conf/opensrf_core.xml --service opensrf.math \
> --no-daemon --action start
> 
> and I get 
> * opensrf.math is not configured to run on apptest-504.wichita.edu
> I think I have configured OpenSRF to use the fqdn of the host. I have configured /etc/hosts and the 
> jabber config and I still get 
> * opensrf.math is not configured to run on apptest-504.wichita.edu
> 
> I THINK my configuration is sane, I could be wrong.
> please send along any trouble shooting steps I'm missing.
>