[Evergreen-admin] Fresh 2.5.2 install error connecting via Staff Client (Windows)

Tue Feb 11 11:56:57 EST 2014

Hi, Tim

You mentioned that this is a test setup. Are you setting up everything on one server (database, evergreen, ejabberd, etc.?), or are you putting some components onto separate servers?

If everything's on one server (which should be the case, if you've been following right along with the install docs), you shouldn't have to mess around with pg_hba.conf since everything is happening locally. I know that I've messed up my setup when I tried playing around with pg_hba.conf, so I try to avoid doing that. Mine is using /32, everything local, so it shouldn't be a matter of opening up the local subnet.

In that auth error, it looks like you're trying the username 'root'. Is that so? Make sure you're using the admin-user and admin-pass that you set up when you were creating the evergreen database: http://docs.evergreen-ils.org/2.5/_creating_the_evergreen_database.html#_creating_the_evergreen_database_and_schema
Would you mind sending along the ejabberd log file /var/log/ejabberd/ejabberd.log? Based on your original message, it strikes me as something with ejabberd (granted, I'm not the foremost authority on this stuff haha)

Thanks!

Elliot J. Voris

From: Alexander Tim [mailto:TAlexander at triley.co.uk]
Sent: 11 February, 2014 10:29
To: Elliot Voris
Subject: RE: [Evergreen-admin] Fresh 2.5.2 install error connecting via Staff Client (Windows)

Dear Elliot,

Thanks for that.  I have gone through and all seems to be correct.  I have actually managed to get a step further by opening up the restrictions for connections to the database (had /24 not /16 in the address of pg_hba.conf.  I am now getting auth errors from the client like so:

method=open-ils.auth.authenticate.complete
params=[{"username":"root","type":"temp","agent":"staffclient","password":"3c871099452d006e10b1ac370d115200"}]
THROWN:
{"payload":[],"debug":"osrfMethodException : No authentication seed found. open-ils.auth.authenticate.init must be called first  (check that memcached is running and can be connected to) ","status":404}
STATUS:

Not really sure what could be causing this except maybe some kind of permissions issue per chance?

Regards

Tim
From: evergreen-admin-bounces at list.evergreen-ils.org<mailto:evergreen-admin-bounces at list.evergreen-ils.org> [mailto:evergreen-admin-bounces at list.evergreen-ils.org] On Behalf Of Elliot Voris
Sent: 11 February 2014 16:24
To: evergreen-admin at list.evergreen-ils.org<mailto:evergreen-admin at list.evergreen-ils.org>
Subject: Re: [Evergreen-admin] Fresh 2.5.2 install error connecting via Staff Client (Windows)

Hey, Tim

In opensrf_core.xml there should be four (4) passwords that you'll have to examine: opensrf at private.localhost<mailto:opensrf at private.localhost>, opensrf at public.localhost<mailto:opensrf at public.localhost>, router at private.localhost<mailto:router at private.localhost>, and router at public.localhost<mailto:router at public.localhost>, respectively. The default provided is 'password' for those values, so if you had used that as your password for the jabber users, then you should be all set.

The error message seems to indicate that router at private.localhost<mailto:router at private.localhost> is the culprit, so I would double-check that password specifically in the opensrf_core.xml file. During a recent install, I accidentally inserted a few extra characters (still don't know how that happened) into one of the password fields. It's an easy thing to overlook.

If everything looks right in the configuration file, I would try stopping and starting ejabberd, memcached, all the OpenSRF services, and apache. Then, give it another go.

Let us know how things progress.

Thanks!

Elliot J. Voris

From: evergreen-admin-bounces at list.evergreen-ils.org<mailto:evergreen-admin-bounces at list.evergreen-ils.org> [mailto:evergreen-admin-bounces at list.evergreen-ils.org] On Behalf Of Alexander Tim
Sent: 11 February, 2014 09:56
To: evergreen-admin at list.evergreen-ils.org<mailto:evergreen-admin at list.evergreen-ils.org>
Subject: [Evergreen-admin] Fresh 2.5.2 install error connecting via Staff Client (Windows)

Dear All,

Have hit several stumbling blocks installing Evergreen for the first time but have finally reached one that a reread and retyping of the commands won't fix.  I have installed on Ubuntu Server 12.04 and followed the guide for installing for 2.5.2.  The client is Windows 7 x64 and is using the 2.5.2 client.  All seems well with testing the host but logging in to the server through the client generates the following error:

Network or server failure.  Please check your Internet connection to 10.168.50.99 and choose Retry Network.  If you need to enter Offline Mode, choose Ignore Errors in this and subsequent dialogues.  If you believe this error is due to a bug in Evergreen and not network problems, please contact your help desk or friendly Evergreen administrators, and give them this information:
method=open-ils.actor.org_tree.descendants.retrieve
params=[1,-1]
THROWN:
{"payload":[],"debug":"osrfMethodException :  *** Call to [open-ils.actor.org_tree.descendants.retrieve] failed for session [1392133796.204839.13921337964322], thread trace [1]:\nException: OpenSRF::EX::Session 2014-02-11T15:49:56 OpenSRF::Application /usr/local/share/perl/5.14.2/OpenSRF/Application.pm:233 Session Error: Call to open-ils.storage for method open-ils.storage.actor.org_unit.descendants.atomic \n failed with exception: Exception: OpenSRF::EX::Session 2014-02-11T15:49:56 OpenILS::Application::AppUtils /usr/local/share/perl/5.14.2/OpenILS/Application/AppUtils.pm:201 Session Error: router at private.localhost/open-ils.storage<mailto:router at private.localhost/open-ils.storage> IS NOT CONNECTED TO THE NETWORK!!!\n : \n\n","status":500}
STATUS:

I have cleared the logs and restarted all the constituent parts individually and not received any error messages.  I am also able to connect using srfsh (and then logging in with a user name and password).  The server seems to be responding as it rejects incorrect user names and passwords.  I have also added an SSL exception to allow me to get this far.  I have also tailed the log for the perl start and found that it thinks the storage bit has started correctly:

[2014-02-11 15:06:57] open-ils.storage [INTL:4051:Pg.pm:120:] All is well on the western front
[2014-02-11 15:06:57] open-ils.storage [DEBG:4051:Storage.pm:66:] Success initializing driver!

I am guessing I have messed up something in the opensrf_core.xml file but will admit the guide on that particular part was not exactly something I was able to grasp and understand.  I seemed to find that most of the passwords were already set in the example file to what I had chosen for this test server.  I would be most grateful for any guidance as I believe this is the last step to actually being able to test the server proper and see if our library wants to use it.

Regards

Tim

________________________________
Tindall Riley Marine (UK) Limited
Authorised and regulated in the UK by the Financial Conduct Authority.

Registered Office: Regis House, 45 King William Street, London EC4R 9AN
Company No: 8451968. V.A.T. No.: 174 7460 86
Tel: +44 (0)20 7407 3588 Fax: +44 (0)20 7403 3942

This email (and any attachments) is confidential and may be privileged. It may be read, copied and used only by the addressee. If you have received this in error, please contact us immediately.

________________________________
Tindall Riley Marine (UK) Limited
Authorised and regulated in the UK by the Financial Conduct Authority.

Registered Office: Regis House, 45 King William Street, London EC4R 9AN
Company No: 8451968. V.A.T. No.: 174 7460 86
Tel: +44 (0)20 7407 3588 Fax: +44 (0)20 7403 3942

This email (and any attachments) is confidential and may be privileged. It may be read, copied and used only by the addressee. If you have received this in error, please contact us immediately.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-admin/attachments/20140211/a5c9c688/attachment-0001.html>