[OPEN-ILS-GENERAL] Error starting Evergreen

[bfeifarek at q.com]

Hi John, 


I'm not familiar with those ejabberd log entries, but if you are sure the public and private passwords for opensrf and router are correct, another possible problem can be with the ejabberd service. I had a situation where I got that same "NOT CONNECTED TO THE NETWORK" where the problem was that the server had changed IP addresses on the network, and ejabberd somewhere had retained the original IP address. The way that I fixed it was by following the instructions in step 5 in the OpenSRF installation guide : (same steps for OpenSRF 1.6.x or 2.0) 






    1. 
As the root user, stop the ejabberd service: / etc / init.d / ejabberd stop 
        • 
If ejabberd reports that it is already stopped, it may have run into a problem starting back at the installation stage. One possible fix is to kill any remaining beam and epmd processes, then edit /etc/default/ejabberd to hardcode a domain: epmd -kill killall beam; killall beam.smp rm / var / lib / ejabberd /* echo 'ERLANG_NODE=ejabberd at localhost' >> / etc / default / ejabberd 


Brian Feifarek 
----- Original Message -----
From: "John Boggs" <boggs at plsinfo.org> 
To: "Evergreen Discussion Group (open-ils-general at list.georgialibraries.org)" <open-ils-general at list.georgialibraries.org> 
Sent: Monday, August 8, 2011 6:16:27 PM 
Subject: [OPEN-ILS-GENERAL] Error starting Evergreen 




I’m trying to get a new instance of Evergreen 2.something-or-other to start up, and I get stuck on the autogen step. My error is: 



opensrf at evergreen:/openils/bin$ ./autogen.sh -c /openils/conf/opensrf_core.xml -u 

Updating Evergreen organization tree and IDL using '/openils/conf/opensrf_core.xml' 



Updating fieldmapper 

Exception: OpenSRF::EX::Session 2011-08-08T11:58:13 OpenSRF::Utils::SettingsClient /usr/local/share/perl/5.10.1/OpenSRF/Utils/SettingsClient.pm:103 Session Error: router at private.localhost/opensrf.settings IS NOT CONNECTED TO THE NETWORK!!! 

opensrf at evergreen:/openils/bin$ 



I’ve seen suggestions that this is a jabber problem, so I tail -f’ed the ejabberd log and got this as I was running autogen: 

=INFO REPORT==== 2011-08-08 11:58:13 === 

I(<0.620.0>:ejabberd_listener:232) : (#Port<0.3566>) Accepted connection {{127,0,1,3},46947} -> {{127,0,1,3},5222} 



=INFO REPORT==== 2011-08-08 11:58:13 === 

I(<0.21513.0>:ejabberd_c2s:466) : ({socket_state,gen_tcp,#Port<0.3566>,<0.21512.0>}) Accepted legacy authentication for opensrf at private.localhost/client_at_evergreen.plsinfo.org_29900 by ejabberd_auth_internal 



=INFO REPORT==== 2011-08-08 11:58:13 === 

I(<0.21513.0>:ejabberd_c2s:1409) : ({socket_state,gen_tcp,#Port<0.3566>,<0.21512.0>}) Close session for opensrf at private.localhost/client_at_evergreen.plsinfo.org_29900 



Any suggestions of where to look next? 



Thanks! 



John D. Boggs, PLAN Database Manager 
Peninsula Library System 
2471 Flores Street 
San Mateo, CA 94403-2273 
(650)571-6799 x3062 
boggs at plsinfo.org 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20110809/ca2ece4f/attachment.htm>