- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- no dump file no crash log files either on ES40
Operating System - Tru64 Unix
1753935
Members
9735
Online
108811
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-07-2003 12:02 PM
тАО08-07-2003 12:02 PM
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-07-2003 11:20 PM
тАО08-07-2003 11:20 PM
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.
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;; }
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2003 04:56 AM
тАО08-08-2003 04:56 AM
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
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
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP