[OPEN-ILS-DEV] Startup problem with OpenSRF settings listener

[Eric Lesage]

Hello,

I hope this is the right mailing list for this problem; otherwise, my 
apologies.

I'm having a problem starting the opensrf settings listener. All the other 
listeners defined in opensrf.xml (let's start simple) seem to be up except 
that one.

What is also surprising is that when the system is started, there is no 
status line pair indicating the [UnixServer/Listener] is being started 
(yet there is a <appname>opensrf.settings</appname> line in my 
opensrf.xml). Is the settings server special somehow?

Instead, the settings listener consumes 100% CPU and does not 
register as a XMPP resource within the "ils" account (it is however, 
registered with the router).

The "stateless" property does not seem to be a factor (altough, I must 
admit I don't really understand what it does).

The opensrf.settings_unix.log says:

--begin--
2006/12/17-23:12:39 OpenSRF::UnixServer (type OpenSRF) starting! pid(32114)
Binding to UNIX socket file 
/usr/local/openils/var/sock/opensrf.settings_unix.sock using SOCK_STREAM
Group Not Defined.  Defaulting to EGID '1509 1509'
User Not Defined.  Defaulting to EUID '1503'
Setting up serialization via flock
Beginning prefork (5 processes)
Starting "5" children
2006/12/17-23:12:40 CONNECT UNIX Socket: "/usr/local/openils/var/sock/opensrf.settings_unix.sock"
MessageWrapper received bad XML : error = :1: namespace error : Namespace prefix stream on error is not defined
<stream:error><conflict xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text xml:l
              ^ at /usr/local/lib/site_perl/OpenSRF/Transport/SlimJabber/MessageWrapper.pm line 17.

XML = <stream:error><conflict xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text xml:lang='' xmlns='urn:ietf:params:xml:ns:xmpp-streams'>Replaced by new connection</text></stream:error>
:1: namespace error : Namespace prefix stream on error is not defined
<stream:error><conflict xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text xml:l
              ^ at /usr/local/lib/site_perl/OpenSRF/Transport/SlimJabber/MessageWrapper.pm line 17.

Starting "2" children
Processing diff (-1), Waiting diff (0)
Killing "1" children
Starting "1" children
2006/12/17-23:13:33 Server closing!
--end--

There are matching log entries in osrfsys.log.

Running with INTL logging, the listener keeps repeating:
[2006-12-17 23:13:33] -e [INTL:32121:::]  Got [] from the socket

I'm attempting to run evergreen 1.0.1 on a Gentoo/amd64 system using 
ejabberd (which, otherwise, seems to work). The fact that the settings 
listener has problems will cause opensrf-c to crash later.

Has anyone else seen this problem?

Thanks,

-- 
Eric Lesage