Re: Two Simple Questions

--On Friday, October 15, 2004 12:42:54 -0500 Robin Holt <[email protected]> 
wrote:

> On Fri, Oct 15, 2004 at 12:38:37PM -0500, Robin Holt wrote:
>> On Fri, Oct 15, 2004 at 10:38:24AM -0700, Jay Lan wrote:
>> > Robin Holt wrote:
>> > > On Fri, Oct 15, 2004 at 10:52:44AM -0400, Andrew Fant wrote:
>> > >
>> > >> Wow, activity on the mailing list just as I get CSA installed on my
>> > >> testbed.  My timing gets better and better.  I have two questions
>> > >> for  anyone who might have answers
>> > >>
>> > >> 1)  Has anyone gotten CSA to work with LSF under Linux?
>> > >
>> > >
>> > > We had it working with lsf and PBS Pro under the 2.4 kernel.  I
>> > > am not sure if it is working there now.
>> >
>> > Yes, still working! :)
>> >
>> > >
>> > >
>> > >> 2)  When I use ja, all my reports terminate with a segfault.  For
>> > >> example:
>> >
>> > Did you install job rpm, chkconfig on job, and modify /etc/pam.d/ files
>> > as noted when you installed job rpm?
>> >
>> > I have not received reports on ja segfault before.
>>
>> I don't think you can get the job accounting started without the above.
>> Let me try.
>
> Nope, there must be something else going on.  We would need to know
> a lot more to help you.  I guess we would need to start with kernel
> version and patches, job and csa userland versions, glibc version,
> and compiler version.
>
> It will probably be easier to get a core dump and just issue 'where'.
> That will probably be the best information.
>
> Thanks,
> Robin
>
>
>


Well, the core dump was less than helpful.  The traceback I got was:
(gdb) where
#0  0x0e10567b in __register_atfork () from /lib/libc.so.6
#1  0x0e07199f in __cxa_finalize () from /lib/libc.so.6
#2  0x0e01f590 in ?? () from /lib/libm.so.6
#3  0x0e03d600 in ?? () from /lib/libm.so.6
#4  0x0e03d720 in ?? () from /lib/libm.so.6
#5  0xdfffeb18 in ?? ()
#6  0x0e0370d6 in ?? () from /lib/libm.so.6
#7  0x0e01c000 in ?? ()
#8  0x0e0139dc in ?? () from /lib/ld-linux.so.2
#9  0xdfffeba8 in ?? ()
#10 0x0e00afc6 in _dl_rtld_di_serinfo () from /lib/ld-linux.so.2
Previous frame inner to this frame (corrupt stack?)

I'm going to try another kernel rebuild and see if that helps.

Andy