[OPEN-ILS-DEV] libxml2 router issue on Debian Etch

2008-09-16 Thread Bill Erickson

Hi all,

Just a heads up...  I just found what appears to be a bug in libxml2  
version on 2.6.27.dfsg-4 on Debian Etch, which is the latest stable  
libxml2 release (as of late August).  After parsing a certain number of  
jabber messages within a given SAX parser context, it just stops  
working.  In my test environment (2.6.18-5-amd64), it always breaks  
between 26k and 31k messages.  This manifests itself as failed messages to  
the OpenSRF router:  the requests go in, but they never come out the other  
end.


You can see what version you have installed with

$ dpkg -l libxml2 libxml2-dev

I downgraded my machine to libxml2_2.6.27.dfsg-2_amd64 and  
libxml2-dev_2.6.27.dfsg-2_amd64 (to match other local machines) and  
problem solved.


Finding old Debian packages isn't always easy, so I've put our AMD 64  
versions on the open-ils.org site in case they can be of use to anyone:


http://open-ils.org/~erickson/libxml2_2.6.27.dfsg-2_amd64.deb
http://open-ils.org/~erickson/libxml2-dev_2.6.27.dfsg-2_amd64.deb

I'll try to isolate the problem so I can send something useful to the  
libxml2 folks.


Thanks,

-b

--
Bill Erickson
| VP, Software Development  Integration
| Equinox Software, Inc. / The Evergreen Experts
| phone: 877-OPEN-ILS (673-6457)
| email: [EMAIL PROTECTED]
| web: http://esilibrary.com


RE: [OPEN-ILS-DEV] Installation issues/problems Thanks but ...one more problem ;

2008-09-16 Thread Thomas Edward

 Hi Dan, Your email was quick and a huge help. I am even more excited about 
Evergreen. I have one problem though:When I initiate the apache server 
(section: Starting the Web server) I get the following error message. [EMAIL 
PROTECTED]:~# /etc/init.d/apache2 start* Starting web server apache2 apache2: 
Could not reliably determine the server's fully qualified domain name, using 
127.0.1.1 for ServerName(98)Address already in use: make_sock: could not bind 
to address 0.0.0.0:443no listening sockets available, shutting downUnable to 
open logs-- I have examine the following flies for 
clues:/etc/apache2/sites-available/eg.conf/etc/apache2/eg_vhost.conf/etc/apache2/startup.pl/openils/conf/opensrf_core.xml/openils/conf/opensrf.xml
 Also, why is the IP address given as 127.0.1.1 and not 
127.0.0.1?-note also the outputfor the fqdn:[EMAIL 
PROTECTED]:/etc/apache2/sites-available# perl -MNet::Domain -e 'print 
Net::Domain::hostfqdn();'thomas-desktop.uwichill.edu.bb-- which 
is the same as is in the /openils/conf/opensrf.xml file. Anxiously waiting your 
response. Thomas  Thomas  Rebirth, renew, Starting a new Life.   
 Date: Sun, 14 Sep 2008 20:23:28 
-0400 From: [EMAIL PROTECTED] To: open-ils-dev@list.georgialibraries.org 
Subject: Re: [OPEN-ILS-DEV] Installation issues/problems Hi Thomas: 
2008/9/14 Thomas Edward : Hi, I have installed Evergreen server on 
Ubuntu 7.10 and have followed all the instructions on 
http://open-ils.org/dokuwiki/doku.php?id=installing_evergreen_1.2_on_ubuntu_7.10.
 I have a small lab with four machines whic dual boot Windows Vista and Linux 
Unbuntu 7.10. This is a exercise for me but I'd like to demo to the local 
library. Issue #1. When I run instruction 2 (i) under Starting 
Evergreen I get the following error message. [EMAIL 
PROTECTED]:/home/thomas# su opensrf [EMAIL PROTECTED]:/home/thomas$ 
osrf_ctl.sh -c /openils/conf/opensrf_core.xml -a start_router Starting 
OpenSRF Router  Unable to connect router to jabber server localhost... 
exiting I think this is the big problem - it's mirrored by the error that 
you got in settings-tester.pl. Checking opensrf_core.xml, you have two 
different passwords for the opensrf Jabber user - mypass and mypassword. 
These passwords have to be correct so that the opensrf Jabber user can connect 
to Jabber and talk to the router Jabber user Issue #2 Quote from 
instruction document: Instruction 17 (ii) Change the name of the child 
element of the element in opensrf.xml from ... to match the fully-qualified 
domain name of your server. For example, if the fully-qualified domain name of 
your server is evergreen.rocks.com: I have run the instruction perl 
-MNet::Domain -e 'print Net::Domain::hostfqdn() but get this output: 
[EMAIL 
PROTECTED]:/home/opensrf/Evergreen-ILS-1.2.2.3/Open-ILS/src/support-scripts# 
perl -MNet::Domain -e 'print Net::Domain::hostfqdn()What do you think the 
problem might be? You're missing the ending semicolon-singlequote characters 
for the command; it should be: perl -MNet::Domain -e 'print 
Net::Domain::hostfqdn();' Issue #3 I have executed the file 
Open-ILS/src/support-scripts/settings-tester.pl and haveattached the results 
for your analysis. Teh file is called settings-tester-results. The list of 
Perl modules shows that Net::Z3950::ZOOM wasn't installed successfully, 
probably because indexdata's test server is still down. See 
http://list.georgialibraries.org/pipermail/open-ils-general/2008-August/000838.html
 for details and a workaround. You won't need this until you get the staff 
client running, though, so no rush. We also see the failure to connect to the 
Jabber router, which I covered in issue 1. Issue #4 Quote from 
instruction document:Section Testing connections to Evergreen  Once you 
have installed and started Evergreen, test your connection to Evergreen via 
srfsh:  question: Must I run this as root, as opensrf or as [EMAIL 
PROTECTED]:/$ ? You can run this as any user that has .srfsh.xml set up in 
their home directory. Issue #5: I am not clear on instruction # 19. Copy 
/openils/conf/srfsh.xml.example to .srfsh.xml in the home directory of each 
user you want to use to run the srfsh command line client for testing OpenSRF, 
and edit .srfsh.xml as follows:  Must this file be copied to the 
/home/opensrf directory? You can copy the configuration file to the home 
directory of any user. I often have /home/opensrf/.srfsh.xml and 
/home/dan/.srfsh.xml both set up so that I don't have to switch users just to 
run some srfsh commands. Issue #6 Attachments I have also included the 
following files as attachments: opensrf.xml, opensrf_core.xml Very helpful in 
diagnosing the problem - thanks! Let us know what happens. Hopefully once you 
work out the Jabber username/password problem, everything else will fall into 
place. -- Dan Scott Laurentian University