| Subject: | simple2zoom is throwing segmentation faults on Ubuntu 12 |
| Date: | Wed, 24 Apr 2013 15:28:20 -0500 |
| To: | bug-Net-Z3950-Simple2ZOOM [...] rt.cpan.org |
| From: | Alan Rykhus <alan.rykhus [...] mnsu.edu> |
Hello,
This is a bug I filed with the Evergreen group. It was suggested that it
be sent to here. I'm not sure how to replicate the problem, I can only
tell you that our Z39.50 server gets used a lot and we were seeing a lot
of these errors.
If you have any questions, feel free to contact me -- al
The Evergreen bug report:
While simple2zoom is a stand alone product, it is used by Evergreen as
its Z39.50 server. If you are running Ubuntu 12 the simple2zoom program
is aborting throwing segmentation faults. This does not happen on Ubuntu
10.
If you run simple2zoom on an Ubuntu 10 server you can point it to the
newer Evergreen server that is running on Ubuntu 12 without any issues.
But running an older version of Ubuntu and a separate server just for
Z39.50 access is not desirable.
To see if you are having this issue you can look in the system log and
sees lines like:
Apr 24 08:04:49 ecrl kernel: [1243984.330118] simple2zoom[27566]:
segfault at 12c1 ip 00007f1c9ceb5be1 sp 00007fff3de0b198 error 4 in
libc-2.15.so[7f1c9cd53000+1b5000]
Apr 24 09:19:45 ecrl kernel: [1248471.191697] simple2zoom[31188] general
protection ip:7f1c9ceb5c05 sp:7fff3de0b198 error:0 in
libc-2.15.so[7f1c9cd53000+1b5000]
Our current production machine that is seeing the segmentation faults
Evergreen version - 2.3.1
OpenSRF version - 2.1.2
Postgres version - 9.1
Linux - Ubuntu 12 kernel 3.2.0-40-generic
Our former production machine that we are using as our simple2zoom
server because it is stable
Evergreen version - 2.0.9
OpenSRF version - 2.1.2
Postgres version - 9.0
Linux - Ubuntu 10 kernel 2.6.32-46-server
I also have some further information as to things that are required for
simple2zoom. I tried to install simle2zoom on a machine that was not
running Evergreen and these are some of the dependencies that came up. I
then looked at the 2 machines to see what version of them they were each
running. I'm guessing that either one of these introduced the problem,
or libc itself.
UBUNTU 10.04.4 LTS
perl 5.10.1
libc-2.11.1.so
libgcrypt11-dev 1.4.4-5ubuntu2.1
libgnutls-dev 2.8.5-2ubuntu0.3
libgpg-error-dev 1.6-1ubuntu2
libicu-dev 4.2.1-3ubuntu0.10.04.1
libicu42 4.2.1-3ubuntu0.10.04.1
libmarc-charset-perl 1.1-1
libmarc-record-perl 2.0.0-2
libmarc-xml-perl 0.92-1
libtasn1-3-dev 2.4-1ubuntu0.1
libwrap0-dev 7.6.q-18
libxml2-dev 2.7.6.dfsg-1ubuntu1.8
libxslt1-dev 1.1.26-1ubuntu1.2
libyaz3 3.0.52-1
libyaz3-dev 3.0.52-1
tcl8.4 8.4.19-4
yaz 3.0.52-1
UBUNTU 12.04.2 LTS
perl 5.14.2
libc-2.15.so
libgcrypt11 version 1.5
libgnutls version 2.12.14
ibgpg-error-dev version 1.10
libicu-dev Version: 4.8.1.1-3
libicu42 Version: 4.8.1.1-3
libmarc-charset-perl Version: 1.33-1
libmarc-record-perl ersion: 2.0.3-1
libmarc-xml-perl Version: 0.92-1
libtasn1-3-dev Version: 2.10-1ubuntu1.1
libwrap0-dev Version: 7.6.q-21
libxml2-dev Version: 2.7.8.dfsg-5.1ubuntu4.4
libxslt1-dev Version: 1.1.26-8ubuntu1.3
libyaz3 Version: 4.2.18-1build1
libyaz3-dev Version: 4.2.18-1build1
tcl8.4 Version: 8.4.19-4ubuntu3
yaz Version: 4.2.18-1build1
--
Alan Rykhus
PALS, A Program of the Minnesota State Colleges and Universities
(507)389-1975
alan.rykhus@mnsu.edu
"Be pleasant until ten o'clock in the morning and the rest of the day
will take care of itself." ~ Elbert Hubbard