- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- 310 Tru64 UNIX Time Stamp Message
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
тАО07-07-2008 04:45 AM
тАО07-07-2008 04:45 AM
I am looking at 2 hung systems and 310 was the last event. There were no hardware errors and no messages/logs entries. I have no idea why the systems went away, there is no crash dump, there was no-reboots just a hang that required the operator to get in the SRM console and re-boot. Both systems, DS25s, hung over a weekend and needed a Monday morning re-boot.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2008 10:45 AM
тАО07-07-2008 10:45 AM
Re: 310 Tru64 UNIX Time Stamp Message
If I remember correctly, the timestamp messages are written to the binary event log periodically, simply so you can tell that the event logging system is working properly.
The fact that you have 310s up onto the hang, simply tells you that the logging system was working correctly up to that point...
I've seen DS25s exhibit similar problems when they get too hot. Do you have any environmental issues ?
Cheers,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2008 03:57 AM
тАО07-08-2008 03:57 AM
SolutionIf you do find a hung system, it's worth trying to force a crash dump rather than just rebooting, since rebooting clears the contents of memory. The way to do this is to halt the system to get to the SRM console. How to halt the system depends on the system type -- on a DS25 and many other systems, there's a halt button on the front panel. Then when you get to the SRM prompt, enter "CRASH". The console firmware will dump the contents of memory to swap space, just as is done when the system panics. When the dump completes, boot the system normally. During the boot sequence, a startup script will detect the presence of the dump in swap space and save it to a crash dump in the crash directory -- /var/adm/crash by default, although you can change this in /etc/rc.config. The crash dump can be submitted to HP for analysis if you have Tru64 UNIX software support, or you can try looking at it yourself if you're knowledgeable (or adventurous).
Hope this helps,
Martin
A quick resolution to technical issues for your HPE products is just a click away HPE Support Center
See Self Help Post for more details
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2008 04:50 AM
тАО07-08-2008 04:50 AM
Re: 310 Tru64 UNIX Time Stamp Message
There is not an environmental issue, the systems are well cooled in the Air Traffic Controllers room.
Unfortunately the local system managers didn't make a forced crash which I'd liked to have a look at.
I suspected a memory error but on exercising the memory we got a SYSFAULT on CPU1 on 1 system.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2008 09:46 PM
тАО07-08-2008 09:46 PM