- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: system log file
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО03-14-2005 11:58 AM
тАО03-14-2005 11:58 AM
does anybody know what this means
I even tried to view on syslog.log
and I have sample errors below stating that
"btlan1: Initializing 10/100BASE-T card at 10/16/16.......
Networking memory for fragment reassembly is restricted to 204800 bytes
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 2097152
WARNING: Insufficient space on dump device to save full crashdump.
Only 1073741824 of 2684355584 bytes will be saved.
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0 - major is 31, minor is 0x46000; start = 207712, size = 1048576
netisr real-time priority reset to 100
Starting the STREAMS daemons.
9245XB HP-UX (B.10.20) #1: Sun Jun 9 06:31:19 PDT 1996"
thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2005 12:43 PM
тАО03-14-2005 12:43 PM
Solutionafter the failure.
See if there is a subdirectory. There probably is. Clear old crash dumps, make sure there is room for a new one.
If yes, check the date and do a q4 crash dump analysis on it.
If there is no crash, change the first variable in /etc/rc.config.d/savecrash to 1, Restart the system, wait for the next crash.
If its a traditional crash, you'll get data to run q4 analysis on.
If your system has GSP, log on during a frozen condition and do a TC, which is really a TOC Tranfer of Control. That will do a crash dump.
After analyzing any crash dump, send it to the response center. They will analyze it, tell you what is wrong and give you instructions on how to fix it.
Also, check /var/adm/syslog/syslog.log and dmesg output for hardware problems.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2005 01:42 PM
тАО03-14-2005 01:42 PM
Re: system log file
- /etc/shutdownlog (if you have a support contract with HP, you might want to include this in the list of files to send)
- /var/adm/tombstones (check for ts* files with the same timestamp as when the crash occurred)
- /var/adm/syslog/OLDsyslog.log (check the last entries of the log file)
Please note that the warning message as indicated in your post suggests that there was insufficient disk space on your dump device to save a full crashdump.
Regards,
Ira
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2005 03:40 PM
тАО03-14-2005 03:40 PM
Re: system log file
Have a look at your OLDsyslog.log.
you should also check your GSP console.
regards
yogeeraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2005 06:30 PM
тАО03-14-2005 06:30 PM
Re: system log file
on the GSP (console)
SL (: Show Logs (chassis code buffer)
Select Chassis Code Buffer to be displayed:
Incoming, Activity, Error, Current boot or Last boot? (I/A/E/C/L) E
check the entries .
regards
Henk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2005 07:11 AM
тАО03-17-2005 07:11 AM
Re: system log file
sar -d 5 30
sar -u 5 30
swapinfo -tam
This can and will tell you something of the performance (place in a loop, and run continuously, then review after the reboot to get a clue as to what is going on.