I ran into a similar (but not identical) issue at the autogen.sh portion of an upgrade. What I had to do was shutdown Evergreen services, ejabberd and memcached. I then restarted ejabberd, memcached and Evergreen and then was able to run ./autogen.sh
For a clean install I would look first at the OpenSRF Jabber users and ensure they were created (part of the OpenSRF install prior to Evergreen) and that the passwords are correct in the opensrf_core.xml file (/openils/conf/opensrf_core.xml) I have also found that if this was, say a backup of an existing system that had the hostname changed (for a test server situation) that I had to re-install ejabberd completely (and then re-register the users/passwords as detailed in the OpenSRF install instructions if I remember right) after the hostname was changed to get everything to play nice. Ejabberd does not like to play nice if the hostname has changed, it saves the hostname information somewhere in an embedded database I believe. Hope this helps some. Jesse McCarty City of Burlington IT Technical Assistant From: [email protected] [mailto:[email protected]] On Behalf Of Lamb Joseph Sent: Tuesday, May 20, 2014 2:03 PM To: [email protected] Subject: [OPEN-ILS-DEV] autogen.sh -u Hello, I am failing on the autogen.sh -u portion of the Evergreen install. This the error that I am getting. Exception: OpenSRF::EX::Jabber 2014-05-20T12:11:22 OpenILS::Utils::Cronscript /usr/local/share/perl/5.14.2/OpenILS/Utils/Cronscript.pm:276 Jabber Exception: Could not open TCP socket to Jabber server: IO::Socket::INET: connect: Connection refused I have looked in the archives and read that this problem has to do with hostname and jabber setup. I have gone back and installed evergreen several times already and would like some direction where to look. Thank you for your help Joseph Lamb
