This issue was resolved by using mysql rather than bdb. I guess there
was something wrong with my bdb, but whatever.. it works!
Ryan Pugatch wrote:
> Ryan Pugatch wrote:
>
>> Harald Braumann wrote:
>>
>>
>>> On Tue, 23 Oct 2007 01:00:08 +0200
>>> Tomasz Sterna <[EMAIL PROTECTED]> wro
Ryan Pugatch wrote:
> Harald Braumann wrote:
>
>> On Tue, 23 Oct 2007 01:00:08 +0200
>> Tomasz Sterna <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>>> Dnia 22-10-2007, Pn o godzinie 15:03 -0400, Ryan Pugatch pisze:
>>>
>>>
Yes, I did a make clean. Backtrace just has a bunch of s
Harald Braumann wrote:
> On Tue, 23 Oct 2007 01:00:08 +0200
> Tomasz Sterna <[EMAIL PROTECTED]> wrote:
>
>
>> Dnia 22-10-2007, Pn o godzinie 15:03 -0400, Ryan Pugatch pisze:
>>
>>> Yes, I did a make clean. Backtrace just has a bunch of stuff like:
>>>
>>> #0 0x0030 in ?? ()
>>> #1 0x
Dnia 23-10-2007, Wt o godzinie 03:19 +0200, Harald Braumann pisze:
> Hm, but even if glibc is stripped, there has to be one function in
> this
> back trace that's inside sm and thus should be printed.
>
> Also, there are 256 lines in the bt. How do you get so
> many nested function calls? AFAIK ja
On Tue, 23 Oct 2007 01:00:08 +0200
Tomasz Sterna <[EMAIL PROTECTED]> wrote:
> Dnia 22-10-2007, Pn o godzinie 15:03 -0400, Ryan Pugatch pisze:
> > Yes, I did a make clean. Backtrace just has a bunch of stuff like:
> >
> > #0 0x0030 in ?? ()
> > #1 0x082456a0 in ?? ()
> > #2 0x082456a0 in ?
Dnia 22-10-2007, Pn o godzinie 15:03 -0400, Ryan Pugatch pisze:
> Yes, I did a make clean. Backtrace just has a bunch of stuff like:
>
> #0 0x0030 in ?? ()
> #1 0x082456a0 in ?? ()
> #2 0x082456a0 in ?? ()
> #3 0x00c44158 in main_arena () from /lib/libc.so.6
Looks like your glibc is stri
Harald Braumann wrote:
> On Mon, 22 Oct 2007 12:41:07 -0400
> Ryan Pugatch <[EMAIL PROTECTED]> wrote:
>
>
>> Harald Braumann wrote:
>>
>>> On Mon, 22 Oct 2007 10:54:21 -0400
>>> Ryan Pugatch <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>>
(gdb) run
Starting program: /usr/local/
On Mon, 22 Oct 2007 12:41:07 -0400
Ryan Pugatch <[EMAIL PROTECTED]> wrote:
>
>
> Harald Braumann wrote:
> > On Mon, 22 Oct 2007 10:54:21 -0400
> > Ryan Pugatch <[EMAIL PROTECTED]> wrote:
> >
> >
> >> (gdb) run
> >> Starting program: /usr/local/bin/sm
> >> [Thread debugging using libthread_db
Harald Braumann wrote:
> On Mon, 22 Oct 2007 10:54:21 -0400
> Ryan Pugatch <[EMAIL PROTECTED]> wrote:
>
>
>> (gdb) run
>> Starting program: /usr/local/bin/sm
>> [Thread debugging using libthread_db enabled]
>> [New Thread -1208580416 (LWP 20792)]
>> Error while reading shared library symbols:
On Mon, 22 Oct 2007 10:54:21 -0400
Ryan Pugatch <[EMAIL PROTECTED]> wrote:
> (gdb) run
> Starting program: /usr/local/bin/sm
> [Thread debugging using libthread_db enabled]
> [New Thread -1208580416 (LWP 20792)]
> Error while reading shared library symbols:
> Cannot find new threads: generic error
(gdb) run
Starting program: /usr/local/bin/sm
[Thread debugging using libthread_db enabled]
[New Thread -1208580416 (LWP 20792)]
Error while reading shared library symbols:
Cannot find new threads: generic error
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208580416
On Mon, 22 Oct 2007 09:32:03 -0400
Ryan Pugatch <[EMAIL PROTECTED]> wrote:
> Found some more information about sm dying:
> [...]
> Mon Oct 22 09:34:38 2007 storage_db.c:161 serialising key time
> Segmentation fault
>
> Any idea what is failing here?
Try running it with gdb. Then you should be abl
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:1
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
R
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 t
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. Related output below:
C2S : Thu Oct 18 18:29:49 2007 [notice] [7] [192.168.41.21, port=50373]
connect
C2S : sx (io.c:169) 7 ready fo
Dnia 18-10-2007, Cz o godzinie 16:25 -0400, Ryan Pugatch pisze:
> I am attempting to set up a jabberd2 server that uses our LDAP server
> for authentication. However, when a user attempts to log in to the
> jabber server, it does not accept the username and password [...]
You need to disable DI
Greetings,
I am attempting to set up a jabberd2 server that uses our LDAP server
for authentication. However, when a user attempts to log in to the
jabber server, it does not accept the username and password (I'm using
Adium, so it ends up asking me if I want to register which of course
fails
18 matches
Mail list logo
