- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- System crash without any warnings on log
Operating System - OpenVMS
1753767
Members
5630
Online
108799
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
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
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-24-2005 04:09 AM
08-24-2005 04:09 AM
System crash without any warnings on log
Hi,
I have three VAX 4105A servers in Duty,Hot & Warm mode running SCADA application in an area.A process which runs in all the three servers monitors Duty check every 60 secs(one duty should be in network) and Data Disk check every 30 secs.So, if there are two duties due to network blip, this process will crash the old duty immediately. In second case, it will issue a read request to external array(BA356) data disks and if does not get response from disk within 30 secs, it will crash the system as there are no data update for 30 secs.
In recent past three different servers from different area have crashed due to disk read error. So, is there any problem with array controller that my process is unable to read the disk in this case and crashed the server.
Please suggest ...
I have three VAX 4105A servers in Duty,Hot & Warm mode running SCADA application in an area.A process which runs in all the three servers monitors Duty check every 60 secs(one duty should be in network) and Data Disk check every 30 secs.So, if there are two duties due to network blip, this process will crash the old duty immediately. In second case, it will issue a read request to external array(BA356) data disks and if does not get response from disk within 30 secs, it will crash the system as there are no data update for 30 secs.
In recent past three different servers from different area have crashed due to disk read error. So, is there any problem with array controller that my process is unable to read the disk in this case and crashed the server.
Please suggest ...
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2005 04:40 AM
08-24-2005 04:40 AM
Re: System crash without any warnings on log
It sounds like the system is doing a voluntary 'crash' (whatever you mean by crash) - how does this 'crash' look like? If this is not an operating system bugcheck, then you will loose the contents of the errorlog buffers in main memory, which are normally saved as part of the crash dump.
I am afraid you cannot really work around the problem of defective hardware. I beleive the default timeout for a SCSI disk happens to be 30 seconds and hardcoded in the driver. The only 'fix' I see is to replace defective or unreliably (disk read errors) hardware.
I am afraid you cannot really work around the problem of defective hardware. I beleive the default timeout for a SCSI disk happens to be 30 seconds and hardcoded in the driver. The only 'fix' I see is to replace defective or unreliably (disk read errors) hardware.
.
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