[OPEN-ILS-DEV] ejabberd problems

[Lyons, Cyrus 2]

Hi all,

Interesting discussions on this list - I think I'll stay subscribed
(even though I've now fixed my problem.... read on.)

In a moment of impatience, I followed RobertC's advice to simply
rebuild the system:
	" When you installed Deiban did you do a generic webserver
install or did you also install Jabber and Postgresql? If I remember
correctly, I just did a webserver install and no additional packages
then followed the instructions at:
	
http://www.open-ils.org/dokuwiki/doku.php?id=installing_evergreen_1.2_
on_debian_etch_x86_32-bit
	the automated script takes care of the rest of the packages
needed.  

	You can verify that Apache is working correctly before
proceeding with the Evergreen install. 

	RobertC "

So I used my lunch break to do another rebuild of the system. The only
difference between the two builds IIRC was that I didn't install a
database server the second time around, which I had the first time. It
seems that if I had simply used dpkg to get rid of PostgreSQL 7.4, I
may have had fewer problems; I remember noticing that there were some
7.4 directories kicking around the place even after I had used apt-get
to remove it.

Anyway, after going through the install for OpenSRF and Open-ILS,
starting the webserver initially threw a couple of errors:
	root at evergreen:/etc/apache2/ssl# /etc/init.d/apache2 restart
	Forcing reload of web server (apache2)... waiting Syntax error
on line 69 of /etc/apache2/sites-enabled/eg.conf:
	Invalid command 'CacheRoot', perhaps misspelled or defined by
a module not included in the server configuration
	 failed!

Fortunately, this is easily enough solved by enabled mod_cache and
mod_disk_cache:
	root at evergreen:/etc/apache2/ssl# ln -s
/etc/apache2/mods-available/cache.load
/etc/apache2/mods-enabled/cache.load
	root at evergreen:/etc/apache2/ssl# ln -s
/etc/apache2/mods-available/disk_cache.load
/etc/apache2/mods-enabled/disk_cache.load
	root at evergreen:/etc/apache2/ssl# /etc/init.d/apache2 start
	Starting web server (apache2)....
	root at evergreen:/etc/apache2/ssl#

And that gives some joy. I couldn't believe that it was working until
I actually loaded up http://evergreen/, but sure enough, it is.

Thanks for all of your suggestions, folks - sorry I didn't man up to a
real solution rather than just skirting the problem. Maybe next
time...


Cyrus



-----Original Message-----
From: open-ils-dev-bounces at list.georgialibraries.org
[mailto:open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of
Dan Scott
Sent: 14 July 2008 14:18
To: Evergreen Development Discussion List
Subject: Re: [OPEN-ILS-DEV] ejabberd problems

Hi Cyrus:

2008/7/14 Lyons, Cyrus 2 <lyonsc2 at lsbu.ac.uk>:
> Dear all,
>
> Apologies in advance if this has already been looked at, but
extensive
> searching hasn't yielded many results.
>
> I'm having a number of issues after an automated install on Debian
> Etch. This is actually my second install on this machine: The first
> had similar problems which I assumed were due to numerous hostname
> changes throughout it's life, and I figured it would be quicker to
> just build the computer cleanly to get rid of any old config files
and
> start from scratch than to weed out the problem. Bad call,
> unfortunately - having identical problems now, so perhaps a waste of
> time...

Perhaps. You said you did an automated install - was it using John
Schmidt's script? This might help us narrow down the problem. What
version of Evergreen?

In the Debian Etch install instructions, I think I'll insert a "If you
run into problems with the "login via srfsh" step, stop now. Run
Open-ILS/src/support-scripts/settings-tester.pl; if that doesn't
provide any helpful feedback, post your problem to the open-ils-dev
mailing list before making any drastic changes to your system
configuration. You're probably closer to a solution than you think."
(something along the lines of the advice to sit still rather than keep
wandering in a forest when you're lost).

> The issues are as follows.
>
> First, after the install, running the admin login command failed:
>        root at evergreen:~# /openils/bin/srfsh
>        srfsh# login admin open-ils
>        ???: login admin open-ils
>        srfsh# exit
>
> I had seen various error messages thrown during the install script
> itself, but unfortunately flashing past too quickly to really take
> notes.
>
> ~/srfsh.log yielded some information:
>        [/*--S
> osrfMessage--*/{"threadTrace":"0","type":"CONNECT"}/*--E
> osrfMessage--*/]
>
>        srfsh 2008-07-14 07:42:44 [DEBG:9022:osrf_stack.c:73:] We
> received 1 messages from router at evergreen.lsbu.ac.uk/open-ils.auth
>        srfsh 2008-07-14 07:42:44 [WARN:9022:osrf_stack.c:84:]  !!!
> Received Jabber layer error message
>        srfsh 2008-07-14 07:42:44 [WARN:9022:osrf_stack.c:94:]  *
> Jabber Error is for top level remote id
> [router at evergreen.lsbu.ac.uk/open-ils.auth], no one to send my
message
> too!!!
>        srfsh 2008-07-14 07:42:44 [INFO:9022:osrf_stack.c:103:]
> Message processing duration 0.000065
>        srfsh 2008-07-14 07:42:44 [DEBG:9022:osrf_stack.c:106:] after
> msg delete
>        srfsh 2008-07-14 07:42:44 [DEBG:9022:osrf_app_session.c:554:]
> AppSession in queue_wait with timeout 5
>        srfsh 2008-07-14 07:42:49 [DEBG:9022:osrf_app_session.c:554:]
> AppSession in queue_wait with timeout 0
>        srfsh 2008-07-14 07:42:49 [WARN:9022:srfsh.c:539:] Unable to
> connect to remote service open-ils.auth

How did you start Evergreen - did you use start_all or start_router /
start_perl / start_c ? Just asking because the former method can
invoke a race condition that prevents the C services from starting -
and open-ils.auth is a C service.

> I read somewhere that it'd be a good idea to clean up any reference
to
> 'localhost' in ejabberd.cfg, openils.xml, and openils_core.xml.
After

Actually, the current thinking is that that's a really bad idea on a
single-server machine. The only hostname that needs to be changed on a
single-server machine is the hostname in the "<hosts>" entry in
opensrf.xml - and even that requirement will be removed in Evergreen
1.4. Changing hostnames in ejabberd.cfg can really upset ejabberd.

> doing so, went to stop apache2, openils, and ejabberd (and then
start
> in reverse order), but now having problems restarting (assuming they
> were really running before, which I now doubt) opensrf and apache:
>        opensrf at evergreen:~$ osrf_ctl.sh -c
> /openils/conf/opensrf_core.xml -a start_router
>        Starting OpenSRF Router
>        !!!! Unable to connect router to jabber server
> evergreen.lsbu.ac.uk... exiting
>        opensrf at evergreen:~$ exit
>        logout
>        root at evergreen:/openils/conf# /etc/init.d/ejabberd start
>        Starting jabber server: ejabberd already running.
>
> Didn't quite see the point of trying perl and c, but here goes
> anyway...
>        opensrf at evergreen:~$ osrf_ctl.sh -c
> /openils/conf/opensrf_core.xml -a start_perl
>        Starting OpenSRF Perl
>        opensrf at evergreen:~$ osrf_ctl.sh -c
> /openils/conf/opensrf_core.xml -a start_c
>        Starting OpenSRF C (host=evergreen.lsbu.ac.uk)
>        Ctrl + C
>
> As you can see, Perl starts fine; C hangs around seemingly doing
> nothing and needs me to Ctrl+C to be able to carry on. Next up,
> apache:
>        root at evergreen:/openils/conf# /etc/init.d/apache2 start
>        Starting web server (apache2)...Syntax error on line 51 of
> /etc/apache2/sites-     available/eg_vhost.conf:
>        Invalid command 'XMLEntStripPI', perhaps misspelled or
defined
> by a module not included in the server configuration
>         failed!

Hmm, your apache server should be loading a new apache module named
mod_xmlent.so (which will give it the XMLEntStripPI command, among
others) and osrf_json_gateway.so as part of /etc/apache2/httpd.conf.
Perhaps apache was already running?

> I will attach opensrf.xml and opensrf_core.xml if necessary, but
this
> message seems long enough without, and I thought someone might have
> some inspired counsel to offer.

First thing I would try doing is running settings-tester.pl - if that
turns up nothing obvious, then I would work towards getting
ejabberd.cfg back to recognizing localhost. You might need to purge
the package entirely with dpkg to remove all traces of it, then
reinstall ejabberd and follow the ejabberd configuration steps in
http://open-ils.org/dokuwiki/doku.php?id=installing_evergreen_1.2_on_d
ebian_etch_x86_32-bit
starting at step 12.

Keep us informed!

-- 
Dan Scott
Laurentian University

Email has been scanned for spam and viruses by Altman Technologies'
email management service - www.altman.co.uk/emailsystems/
Any queries regarding these services should be emailed to
ICTemail at lsbu.ac.uk or you can check our web site at
www.lsbu.ac.uk/email/ for up todate information about this service.

--
Email has been scanned for spam and viruses by Altman Technologies' email management service

Copyright in this email and in any attachments belongs to London South Bank University. This email, and its attachments if any, may be confidential or legally privileged and is intended to be seen only by the person to whom it is addressed. If you are not the intended recipient, please note the following: (1) You should take immediate action to notify the sender and delete the original email and all copies from your computer systems; (2) You should not read copy or use the contents of the email nor disclose it or its existence to anyone else.

The views expressed herein are those of the author(s) and should not be taken as those of London South Bank University, unless this is specifically stated.

London South Bank University is a company limited by guarantee registered in England and Wales. The following details apply to London South Bank University: Company number - 00986761; Registered office and trading address - 103 Borough Road London SE1 0AA; VAT number - 778 1116 17; Email address - lsbuinfo at lsbu.ac.uk