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

Alexander Tim TAlexander at triley.co.uk
Tue Feb 11 12:28:06 EST 2014


Log file was too big.

From: Alexander Tim
Sent: 11 February 2014 17:21
To: 'Elliot Voris'; evergreen-admin at list.evergreen-ils.org
Subject: RE: [Evergreen-admin] Fresh 2.5.2 install error connecting via Staff Client (Windows)

Indeed it is all on the local box.  The reason I poked around the pg_hba.conf was I was initially getting a "Connection Refused" error while using the perl script to generate the database.  I googled about and added the following to pg_hba.conf:

host all all 10.168.0.0/16 trust

I then amended postgresql.conf with:

listen_addresses = '*'

This then allowed the perl script to generate the necessary database etc.

I am using the username root, laziness on my part while setting this up for a test.  This is the admin username I setup while running the perl script.

I have attached the log file.  I note there are some errors from this morning in there but anything from about 1300 on should be about correct for the current run of the installation process.

Regards

Tim

From: 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:57
To: evergreen-admin at list.evergreen-ils.org
Subject: Re: [Evergreen-admin] Fresh 2.5.2 install error connecting via Staff Client (Windows)

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

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/46cb82ce/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ejabberdclipped.log
Type: application/octet-stream
Size: 22572 bytes
Desc: ejabberdclipped.log
URL: <http://list.evergreen-ils.org/pipermail/evergreen-admin/attachments/20140211/46cb82ce/attachment-0001.obj>


More information about the Evergreen-admin mailing list