topic Re: Memory fault(coredump) error when using 'last' command in Operating System - HP-UX

Memory fault(coredump) error when using 'last' command

Simon R Wootton — Tue, 05 Aug 2003 08:49:35 GMT

If I issue a 'last' command

eg. last root

I get a 'Memory fault(coredump)' message. Has anyone seen this before ? Any idea's on cause/rectification ? Could it be to do with the wtmp file ?

ALl help rewarded.
Thanks
Simon

Re: Memory fault(coredump) error when using 'last' command

Pete Randall — Tue, 05 Aug 2003 08:53:19 GMT

Simon,

The usual culprit is a corrupt wtmp file. Try moving it out of the way and re-creating it with "cat /dev/null > /var/adm/wtmp" to see if that cures the problem.

Pete

Re: Memory fault(coredump) error when using 'last' command

James R. Ferguson — Tue, 05 Aug 2003 08:56:23 GMT

Hi Simon:

Yes, it is highly likely that 'var/adm/wtmp' (or perhaps 'var/adm/btmp') is corrupt. You can preserve (copy) both and recreate each to see if the problem disappears. If you find 'wtmp' causes the coredump but not 'btmp' you can restore 'btmp' and null 'wtmp'. To recreate, do:

# cat /dev/null > /var/adm/wtmp
# cat /dev/null > /var/adm/btmp

Regards!

...JRF...

Re: Memory fault(coredump) error when using 'last' command

Simon R Wootton — Tue, 05 Aug 2003 08:57:48 GMT

Problem sorted - thanks guys !

Re: Memory fault(coredump) error when using 'last' command

Tim Adamson_1 — Tue, 05 Aug 2003 08:58:53 GMT

Hi,

It sounds like you may have a corrupt wtmp file or btmp.

Try copying them aside for backup purposes, then zero one out (eg, > wtmp) and try the last command again. If it works then you have found the problem. If not, then zero the other one out and cp the first one back and try again.

Cheers!

Re: Memory fault(coredump) error when using 'last' command

Steve Steel — Tue, 05 Aug 2003 09:00:50 GMT

Hi

99 percent chance of wtmp problems

look at wtmpfix

Steve Steel

Re: Memory fault(coredump) error when using 'last' command

Jim Mills_3 — Wed, 21 Jul 2004 12:58:22 GMT

I had the same problem and just nulled the wtmp file and it fixed my problem. Thanks.