Description of problem: router segfaults after just basic configuration of jabberd (according to http://jabberd2.xiaoka.com/wiki/InstallGuide/BasicConfiguration). Version-Release number of selected component (if applicable): jabberd-2.2.7.1-2.fc11.x86_64 How reproducible: 100% Steps to Reproduce: 1. service jabberd stop 2.ulimit -c unlimited ; router -D 3.service jabberd start Actual results: service jabberd status says that router doesn't run, but the subsystem is locked Expected results: all subsystems of jabberd should run Additional info:
Gosh, and then I forgot to paste the backtrace: Core was generated by `router -D'. Program terminated with signal 11, Segmentation fault. #0 _sx_chain_io_read (s=0x19e7ff0, buf=0x1c19350) at chain.c:95 95 for(scan = s->rio; scan != NULL; scan = scan->rnext) Thread 1 (Thread 10456): #0 _sx_chain_io_read (s=0x19e7ff0, buf=0x1c19350) at chain.c:95 #1 0x00000000004094d3 in sx_can_read (s=0x19e7ff0) at io.c:222 #2 0x0000000000404fa9 in router_mio_callback (m=0x19e7e50, a=<value optimized out>, fd=0x19df9c0, data=0x0, arg=0x19dfa90) at router.c:866 #3 0x00000000004105e4 in _mio_run (m=0x19e7e50, timeout=<value optimized out>) at mio_impl.h:257 #4 0x0000000000404550 in main (argc=<value optimized out>, argv=<value optimized out>) at main.c:420 In /var/log/messages I have message: Apr 26 02:18:39 viklef kernel: router[10969]: segfault at 10 ip 000000000040f560 sp 00007fffa7198940 error 4 in router[400000+20000]
Copied to upstream bugtracker.
From launchpad: Could you print the value of: s s->rio scan scan->rnext
Answering upstream
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I've just installed 2.1.7 version, and I've tried to rebuild 2.1.8 one... Same issue :/ Upstream does not seems to know what is the problem and/or how to repair it : https://bugs.launchpad.net/jabberd2/+bug/367783 The only solution I've found for now to get my jabberd server running under F-11 is to rebuild the latest F-10 version (2.2.4) :-(
Created attachment 348504 [details] use size_t stead of int for gsasl calls This patch fixes the bug. The problem was the type of the len variable. It was 4 bytes (int), but on 64-bit platforms it has to be 8 bytes (size_t), because that is what libgsasl expects (it gets passed a pointer to len).
Thanks for the patch. I have updated jabberd to 2.2.8 on the devel branch and included your patch. I will update jabberd on the other branches also in the next few days.
I have just tried to apply the patch myself for F11 and it seems to work. Thank you.
I also have rebuild RPM for 2.2.8 on F-11-x86_64 with patch applied : that works fine :-) Many thanks.
(In reply to comment #9) > I have just tried to apply the patch myself for F11 and it seems to work. Thank > you. bradford:~$ date -I 2009-07-05 bradford:~$ sudo yum list jabberd\* Loaded plugins: allowdowngrade, changelog, presto, refresh-packagekit, remove- : with-leaves Available Packages jabberd.x86_64 2.2.7.1-2.fc11 fedora jabberd-debuginfo.x86_64 2.2.7.1-2.fc11 fedora-debuginfo bradford:~$
So, given this is filed against F11, this bug should certainly not be VERIFIED.
I am not 100% sure, but I assume this means that I should finally upgrade jabberd for F11 ;-) It is building right now and will push the update as soon as possible. Sorry for the delay.
jabberd-2.2.8-2.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/jabberd-2.2.8-2.fc11
jabberd-2.2.8-2.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update jabberd'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7454
jabberd-2.2.8-2.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.