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

Wed Feb 12 13:22:01 EST 2014

Good call, Aleksey! I didn't even think about checking the firewall.

I probably should have asked these things at the start: What OS are you using? What version of OpenSRF did you install? Any chance you installed OpenSRF and/or Evergreen with the --enable-python flag (if that seems completely unfamiliar, then you probably didn't)? Have you run through the steps outlined here: http://evergreen-ils.org/dokuwiki/doku.php?id=troubleshooting:checking_for_errors ? If so, what were the results?

Double check two steps for me:
1) From the OpenSRF install instructions: http://evergreen-ils.org/documentation/install/OpenSRF/README_2_2_2.html#_testing_the_default_opensrf_services
2) From the Evergreen-ILS install instructions: http://docs.evergreen-ils.org/2.5/_testing_connections_to_evergreen.html

I recall when I was trying to install Evergreen for the first time, it took me a bunch of tries. I was also fairly new to Linux at the time, too. It was like trying to learn how to administer software, using a language I was learning simultaneously. It was really easy to overlook things and get myself lost.

Thanks!

Elliot J. Voris

-----Original Message-----
From: evergreen-admin-bounces at list.evergreen-ils.org [mailto:evergreen-admin-bounces at list.evergreen-ils.org] On Behalf Of Lazar, Alexey Vladimirovich
Sent: 12 February, 2014 11: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, Alexander.

I'm guessing answer is already probably yes, but did you check over UFW settings on the DB server? Like,

sudo ufw status

You also have to reload UFW for new settings to take effect.

Also, when setting up my first Evergreen instance a while back, I vaguely remember having some issues with special characters in ejabberd passwords. Speaking from memory, I seem to recall having to change to simpler passwords - not shorter, but alphanumeric.

Aleksey

On 2014-02-12, at 05:25 , Alexander Tim <TAlexander at triley.co.uk> wrote:

> Well I carried out a complete rebuild of the server from scratch and ended up at teh same point, though it didn't take as long to get here.  Still getting a not connected error from the Staff Client from my Windows box.  I am addressing the server by IP address but not sure why that would cause a problem (I followed Elliots suggestion to use 'localhost' when running the perl script to create the db).
>  
> Any help greatly appreciated.
>  
> 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 
> [1392203617.715091.13922036172019], thread trace [1]:\nException: 
> OpenSRF::EX::Session 2014-02-12T11:13:37 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-12T11:13:37 
> OpenILS::Application::AppUtils 
> /usr/local/share/perl/5.14.2/OpenILS/Application/AppUtils.pm:201 
> Session Error: router at private.localhost/open-ils.storage IS NOT 
> CONNECTED TO THE NETWORK!!!\n : \n\n","status":500}
> STATUS:
>  
>  
> From: evergreen-admin-bounces at list.evergreen-ils.org 
> [mailto:evergreen-admin-bounces at list.evergreen-ils.org] On Behalf Of 
> Alexander Tim
> Sent: 12 February 2014 08:53
> 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)
>  
> I will certainly be looking in to postgresql a lot more as I have 
> never set up this particular database before.  When I ran the perl 
> script I did use the IP address rather than 'localhost'.  I will give 
> that another go and see what I the outcome is.  With any luck maybe 
> third times the charm for installing it J
>  
> 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 19:32
> To: evergreen-admin at list.evergreen-ils.org
> Subject: Re: [Evergreen-admin] Fresh 2.5.2 install error connecting 
> via Staff Client (Windows)
>  
> Sure enough, my assumption was incorrect: ejabberd looks like it's working fine.
>  
> You're definitely going to want to adjust your postgres connection settings for production. The settings you've got right now are pretty dangerous. >From the PostgreSQL docs:
>  
> trust
> Allow the connection unconditionally. This method allows anyone that can connect to the PostgreSQL database server to login as any PostgreSQL user they wish, without the need for a password or any other authentication. See Section 19.3.1 for details.
>  
> It might not be a huge security concern right now, but it's definitely something you won't want to forget about later on. It could also throw a wrench in the works while you're testing stuff out.
>  
> When you ran that Perl script to configure the database, did you use the actual hostname (or IP address) of the test server, or did you use 'localhost'? I've always used 'localhost' if I'm running through a one-server install, and haven't had any problems. If you ran it with the actual hostname (or IP address), try to run the script with localhost instead.
>  
> Thanks!
>  
> Elliot J. Voris
>  
> From: Alexander Tim [mailto:TAlexander at triley.co.uk]
> Sent: 11 February, 2014 11:28
> 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)
>  
> 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.htm
> l#_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.
> 
>  
> 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.
> 
> 
> _______________________________________________
> Evergreen-admin mailing list
> Evergreen-admin at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-admin

Aleksey Lazar
IS Developer and Integrator - PALS
http://www.mnpals.org/

_______________________________________________
Evergreen-admin mailing list
Evergreen-admin at list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-admin