[OPEN-ILS-GENERAL] Evergreen 1.4 install problems after running staff client

[Robert Soulliere]

To get it going I had to stop and restart Evergreen after a reboot. 

In other words, I ran these 2 commands as opensrf:
1. osrf_ctl.sh -l -a stop_all
2 osrf_ctl.sh -l -a start_all

It seems that there may be a deeper problem here since I think Evergreen
should start correctly at reboot, but this is a fix to get over this error. 

I checked the various logs for errors after reboot. The osrfsys.log
contains a number of errors similar to the following: 

/usr/sbin/apache2 [ERR :4119:EX.pm:66:] Exception:
OpensSRF::EX::JabberDisconnected... OpenSRF::Transport... This Jabber
Instance is no longer connected to the server.

I am not sure if these are errors during the shutting down process which
I can ignore or important errors during the booting up process. 


Sorry about not providing the details but I wanted to be sure my hunches
were correct before providing the details.
 
Thanks,
Robert
   



----- Original Message -----
From: Jason Etheridge <jason at esilibrary.com>
Date: Wednesday, November 12, 2008 2:48 pm
Subject: Re: [OPEN-ILS-GENERAL] Evergreen 1.4 install problems after
running staff client
To: Evergreen Discussion Group <open-ils-general at list.georgialibraries.org>

> > I got it going again. I think I have a good idea as to what 
> caused the
> > problem.
> 
> Excellent.  Don't be shy with sharing gory details.  Someone else may
> run into the same issue.
> 
> -- 
> Jason Etheridge
> | VP, Community Support and Advocacy
> | Equinox Software, Inc. / The Evergreen Experts
> | phone:  1-877-OPEN-ILS (673-6457)
> | email:  jason at esilibrary.com
> | web:  http://www.esilibrary.com
> 


This E-mail contains privileged and confidential information intended
only for the individual or entity named in the message.  If the reader
of this message is not the intended recipient, or the agent responsible
to deliver it to the intended recipient, you are hereby notified that
any review, dissemination, distribution or copying of this communication
is prohibited.  If this communication was received in error, please
notify the sender by reply E-mail immediately, and delete and destroy
the original message.