Bug 508182

Summary: sm: symbol lookup error: /usr/lib64/jabberd/storage_db.so: undefined symbol: ser_string_set
Product: [Fedora] Fedora EPEL Reporter: Jonathan Steffan <jonathansteffan>
Component: jabberdAssignee: Adrian Reber <adrian>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: el5CC: adrian, bernie+fedora, christoph.sievers, dgoodwin, mastahnke, noa, tremble
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: ActualBug
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-23 08:51:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jonathan Steffan 2009-06-25 22:32:35 UTC
Description of problem:
sm: symbol lookup error: /usr/lib64/jabberd/storage_db.so: undefined symbol: ser_string_set

Version-Release number of selected component (if applicable):
jabberd-2.2.5-1.el5

How reproducible:
Always

Steps to Reproduce:
1. yum install jabberd
2. Try starting it.
  
Actual results:
Failure starting.

Expected results:
Works.

Additional info:
This is fixed upstream. Please update.

http://www.mail-archive.com/jabberd2@lists.xiaoka.com/msg01179.html
https://bugs.launchpad.net/jabberd2/+bug/345947

Comment 1 Jonathan Steffan 2009-06-25 23:10:48 UTC
Please build this http://koji.fedoraproject.org/koji/buildinfo?buildID=107036 for the EL-5 branch and at least send it to epel-testing.

Comment 2 Adrian Reber 2009-06-26 09:55:10 UTC
I would first like to try if a recompile fixes it. Could you test it?

Comment 3 Jonathan Steffan 2009-07-04 18:52:48 UTC
I'll try a rebuild on Monday. I doubt it will fix the issue, however.

Comment 4 Adrian Reber 2009-07-04 21:01:36 UTC
A rebuild is available at:

http://koji.fedoraproject.org/koji/taskinfo?taskID=1454553

Comment 5 Jonathan Steffan 2009-07-08 18:31:15 UTC
/usr/bin/sm: symbol lookup error: /usr/lib64/jabberd/storage_db.so: undefined symbol: ser_string_set

Please submit an update to epel-testing for the new build. Thanks.

Comment 6 Adrian Reber 2009-07-09 12:04:47 UTC
(In reply to comment #5)
> /usr/bin/sm: symbol lookup error: /usr/lib64/jabberd/storage_db.so: undefined
> symbol: ser_string_set

I am sorry. But I do not understand what this means. Does it mean that the new version still does not work?

> Please submit an update to epel-testing for the new build. Thanks.

I have tried jabberd-2.2.5-2.el5.x86_64 and it works without a problem.

Comment 7 Jonathan Steffan 2009-07-13 18:26:01 UTC
The rebuild does not work for us, no.

Comment 8 Christoph Sievers 2009-07-16 23:14:00 UTC
move sm to sm.orig and create a new sm that looks like this:

#!/bin/sh
LD_PRELOAD=/usr/lib64/jabberd/authreg_pipe.so
export LD_PRELOAD
exec /usr/bin/sm.orig


yes - it's ugly.

rgds
Christoph

Comment 9 Adrian Reber 2009-07-17 10:03:54 UTC
Ah, good point. Which backends are you (original reporter) using. I have done my tests with PAM and BDB. Maybe that is the reason I cannot reproduce it.

Comment 10 Devan Goodwin 2009-07-22 15:57:50 UTC
We've run into this problem with Fedora 11 i386, jabberd-2.2.7.1-2.fc11.i586.

Any chance we could get a 2.2.8 rebuild for F11? 

Our driver is "db".

Comment 11 Devan Goodwin 2009-07-22 16:03:56 UTC
Sorry scratch that, just saw that there is already a build in updates-testing for Fedora 11. Testing now and will add karma in koji if all is well.

Comment 12 Devan Goodwin 2009-07-22 16:42:21 UTC
Rebuild of 2.2.8 has been submitted for EL5 as well for those who are interested, should land in updates-testing soon.

http://koji.fedoraproject.org/koji/taskinfo?taskID=1492414

Comment 13 Noa Resare 2009-09-23 08:18:20 UTC
with the jabberd-2.2.8-2.el5 available in EPEL for el5, using the db backend I can not reproduce this. I think it is safe to close this as FIXED.

Comment 14 Mark Chappell 2010-09-23 08:51:42 UTC
The new package has been in EPEL for over a year, and there has been no negative response to either Devan's or Noa's comments.  As such closing this one off as ERRATA.