[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]

Re: conserver coreing

Phil Dibowitz phil@usc.edu
Fri, 18 Feb 2005 01:44:20 -0800 (PST)


On Fri, Feb 18, 2005 at 01:37:20AM -0800, Phil Dibowitz wrote:
> Conserver started coring on us tonight out of nowhere. BT:
> 
> #0  0xff0518a0 in _memset ()
> #1  0xfec4d754 in krb5_kt_free_entry ()
> #2  0xfecc738c in key_in_keytab ()
> #3  0xfecc350c in _ex_text0 ()
> #4  0xff212e1c in run_stack ()
> #5  0xff213124 in pam_authenticate ()
> #6  0x19dd0 in CheckPass ()
> #7  0x1afc0 in CheckPasswd ()
> #8  0x24c64 in DoNormalRead ()
> #9  0x256d0 in Master ()
> #10 0x23e8c in main ()

And here's what an strace shows when it dies:

lseek(9, 0, SEEK_CUR)                           = 62
llseek(9, 0, SEEK_CUR)                          = 62
read(9, 0xFF03FD6C, 1)                          = 0
llseek(9, 0, SEEK_CUR)                          = 62
fcntl(9, F_SETLKW, 0xFFBFEC8C)                  = 0
close(9)                                        = 0
    Incurred fault #5, FLTACCESS  %pc = 0xFEC5F954
      siginfo: SIGBUS BUS_ADRALN addr=0x6835D421
    Received signal #10, SIGBUS [default]
      siginfo: SIGBUS BUS_ADRALN addr=0x6835D421




-- 
Phil Dibowitz
Systems Architect and Administrator
Enterprise Infrastructure / ISD / USC
UCC 174 - 213-821-5427

Attachment: pgp00001.pgp
Description: PGP signature