Found some more information about sm dying: Mon Oct 22 09:34:38 2007 sm.c:203 got a packet Mon Oct 22 09:34:38 2007 pkt.c:108 creating new packet Mon Oct 22 09:34:38 2007 mm.c:458 dispatching in-router chain Mon Oct 22 09:34:38 2007 mm.c:468 calling module session Mon Oct 22 09:34:38 2007 sess.c:108 session requested for [EMAIL PROTECTED]/Adium Mon Oct 22 09:34:38 2007 mm.c:620 dispatching user-load chain Mon Oct 22 09:34:38 2007 mm.c:629 calling module active Mon Oct 22 09:34:38 2007 storage.c:224 storage_get: type=active [EMAIL PROTECTED] filter=(null) Mon Oct 22 09:34:38 2007 storage.c:103 adding type 'active' to driver 'db' Mon Oct 22 09:34:38 2007 mm.c:636 user-load chain returning 1 Mon Oct 22 09:34:38 2007 user.c:67 modules failed user load for [EMAIL PROTECTED] Mon Oct 22 09:34:38 2007 sess.c:120 auto-creating user [EMAIL PROTECTED] Mon Oct 22 09:34:38 2007 user.c:91 create user request for [EMAIL PROTECTED] Mon Oct 22 09:34:38 2007 mm.c:620 dispatching user-load chain Mon Oct 22 09:34:38 2007 mm.c:629 calling module active Mon Oct 22 09:34:38 2007 storage.c:224 storage_get: type=active [EMAIL PROTECTED] filter=(null) Mon Oct 22 09:34:38 2007 mm.c:636 user-load chain returning 1 Mon Oct 22 09:34:38 2007 user.c:67 modules failed user load for [EMAIL PROTECTED] Mon Oct 22 09:34:38 2007 mm.c:647 dispatching user-create chain Mon Oct 22 09:34:38 2007 mm.c:656 calling module active Mon Oct 22 09:34:38 2007 mod_active.c:51 activating user [EMAIL PROTECTED] Mon Oct 22 09:34:38 2007 object.c:85 creating new object Mon Oct 22 09:34:38 2007 object.c:136 adding field time (val bfb433e8 type 1) to object Mon Oct 22 09:34:38 2007 storage.c:198 storage_put: type=active [EMAIL PROTECTED] os=8D38D50 Mon Oct 22 09:34:38 2007 storage_db.c:152 serialising object Mon Oct 22 09:34:38 2007 object.c:324 got iter field time (val 471ca6ee type 1) to object Mon Oct 22 09:34:38 2007 storage_db.c:161 serialising key time Segmentation fault
Any idea what is failing here? Ryan Pugatch wrote: > I seem to have resolved the authentication issue, but now when I log in > the server dies. > > ROUT: sx (io.c:169) 9 ready for reading > ROUT: sx (io.c:175) tag 9 event 2 data 0x8ed50a0 > ROUT: Fri Oct 19 14:16:29 2007 router.c:526 reading from 9 > ROUT: Fri Oct 19 14:16:29 2007 router.c:584 read 492 bytes > ROUT: sx (io.c:191) passed 492 read bytes > ROUT: sx (chain.c:93) calling io read chain > ROUT: sx (io.c:215) decoded read data (492 bytes): <route > xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' > from='tripadvisor.com' to='s2s'><iq xmlns='jabber:client' id='dc4zxhc1' > from='tripadvisor.com' to='s2s' type='get'><query > xmlns='http://jabber.org/protocol/disco#info'/></iq></route><route > xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' $ > C2S : Fri Oct 19 14:16:40 2007 [notice] [7] [192.168.40.145, port=49758] > connect > C2S : sx (io.c:169) 5 ready for reading > C2S : Fri Oct 19 14:16:41 2007 [notice] [7] SASL authentication > succeeded: mechanism=PLAIN; [EMAIL PROTECTED] > C2S : sx (io.c:175) tag 5 event 2 data 0x93347f8 > ROUT: Fri Oct 19 14:16:41 2007 [notice] [127.0.0.1, port=38141] disconnect > ROUT: sx (io.c:70) completed nad: <route > xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' to='s2s' > from='tripadvisor.com'><iq xmlns='jabber:client' type='get' to='s2s' > from='tripadvisor.com' id='dc4zxhc1'><query > xmlns='http://jabber.org/protocol/disco#info'/></iq></route> > ERROR: sm died. Shutting down server. > JBRD: Got a signal... pass it on. > JBRD: It was a TERM. Shut it all down! > > > Tomasz Sterna wrote: > >> Dnia 18-10-2007, Cz o godzinie 18:30 -0400, Ryan Pugatch pisze: >> >> >>> Thanks for the response. I did that and it didn't solve the >>> problem. >>> I'm sure it's something simple that is making this fail, but I just >>> don't know what it is. >>> >>> >> >> >>> C2S : sx (sasl_gsasl.c:342) gsasl_step failed, no sasl for this conn; >>> (31): Error authenticating user >>> >>> >> Now it's definitely LDAP authentication error. >> Please make sure that your connection data, login and password are >> correct using 'ldapsearch' tool launched from the same machine as the >> C2S process. >> >> Ex. >> ldapsearch -P 3 -h ldap.example.com -p 389 -b "o=Example Corp." \ >> -x "(uid=rpugatch)" dn >> ldapsearch -P 3 -s one -h ldap.example.com -p 389 -b "o=Example Corp." \ >> -x -D "your dn from previous query" -w password >> >> >> >> > _______________________________________________ > Jabberd2 mailing list > [email protected] > http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com > _______________________________________________ Jabberd2 mailing list [email protected] http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
