Operating System - Tru64 Unix
1753935 Members
9735 Online
108811 Solutions
New Discussion юеВ

no dump file no crash log files either on ES40

 
bouazzaoui
Frequent Advisor

no dump file no crash log files either on ES40

hi,
I had a system crash on ES40 server but when I tried to show log files, nothing was created
Can you please tell me whish parameters should I check in order that server will be able to create automatically required file for diag?
thanks in advance

regards
2 REPLIES 2
Ralf Puchner
Honored Contributor

Re: no dump file no crash log files either on ES40

a crashdump is created within /var/adm/crash.
You can check by simple type in:

kdbx -k /vmunix /dev/mem
(dbx) set hz = 0

system will crash. Use

>>> crash
>>> boot

possible reasons if no crash dumps will be written:

1. Swap device space:
The dump is saved on your combined primary and secondary swaps before being sent to /usr/adm/crash.

2. Hardware problems can also prevent a successful crash. The controller provides the data path between the system memory and the drive; unavailable paths can cause unsuccessful dumps. The system errorlog or /usr/adm/messages should show any associated errors.

3. Never overlook the configuration.

o Proper firmware for this software revision?
o Proper configuration file entries.
o Is the fstab file ok? Especially check the entry for primary swap.
o Unsupported, third-party drives have also been known to cause problems.

4. Kernel parameter "dont_dump" is set.

5. The dump device must be on a LUN 0 device.

6. LSM swap issues.




Help() { FirstReadManual(urgently); Go_to_it;; }
Dave Bechtold
Respected Contributor

Re: no dump file no crash log files either on ES40

Hello,

I suggest you try running /sbin/dumpsys, Tru64 UNIX V5, to see if the system can take a dump and write it to the /var/adm/crash/ directory. You can do this to a live system it will not cause it to panic or anything. See "man dumpsys" for details.

Also, make sure /sbin/savecore is executing at boot time. It runs based on a link in /sbin/rc2.d named S00savecore.

# ls -l /sbin/rc2.d/S00savecore
lrwxr-xr-x 1 root bin 18 Aug 21 2002 /sbin/rc2.d/S00savecore ->
../init.d/savecore

The savecore man page has good information on the process of saving a core dump on the system and possible problems. Another good resource is the man page for vmzcore and sys_attrs_generic. The sys_attrs_generic reference page documents the dump related sysconfig attributes.

If this doesn't help, please post the Tru64 UNIX version your working with.

Hope that helps,
Dave Bechtold