- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: bad dumpfile
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
тАО08-10-2004 07:45 AM
тАО08-10-2004 07:45 AM
Re: bad dumpfile
Willem
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2004 07:59 AM
тАО08-10-2004 07:59 AM
Re: bad dumpfile
@sys$update:swapfiles
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2004 08:35 AM
тАО08-10-2004 08:35 AM
Re: bad dumpfile
But no - but I may have made a mistake (though the system should handle it).
* I created a new dumpfile using @sys$update:swapfiles.
* rebooted
* during reboot, ^P and CRASH on prompt (this I should not have done?)
* boot
* examine CLUE output:
$ type clue*.LOG
SYS$SYSROOT:[SYSMGR]CLUE$STARTUP_DIANA.LOG;21
$ Set NoOn
$ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY"))
OpenVMS (TM) system dump analyzer
%SDA-E-NOTALPHADUMP, dump file does not contain an OpenVMS Alpha dump
OpenVMS (TM) system analyzer
%CLUE-I-CLEANUP, housekeeping started...
%CLUE-I-MAXBLOCK, maximum blocks allowed 5000 blocks
%CLUE-I-STAT, total of 8 CLUE files, 504 blocks.
SYSTEM job terminated at 10-AUG-2004 20:47:23.53
Accounting information:
Buffered I/O count: 136 Peak working set size: 11472
Direct I/O count: 229 Peak virtual size: 180416
Page faults: 803 Mounted volumes: 0
Charged CPU time: 0 00:00:01.11 Elapsed time: 0 00:00:07.77
$
ANA/CRASH didn't do much good either, the very same message.
Now ANA/CRASH/OVER shows:
$ ANA/crash SYS$SYSTEM:SYSDUMP.DMP/OVER
OpenVMS (TM) system dump analyzer
%SDA-W-NOTALPHADUMP, dump file does not contain an OpenVMS Alpha dump
%SDA-W-DUMPEMPTY, dump file contains no valid dump
%SDA-W-INCDUMPFORM, dump file format incompatible with this version of SDA
...analyzing an Alpha full memory dump in override mode...
%LIB-F-BADBLOSIZ, bad block size
I'll try to OPCCRASH from VMS (then there SHOULD be a valid dump, I guess...)
Willem
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2004 08:55 AM
тАО08-10-2004 08:55 AM
Re: bad dumpfile
To summarize:
In case of an invalid dumpfile like above, do this:
1. $ @SYS$UPDATE:AUTOGEN GETDATA TESTFILES NOFEEDBACK
2. Keep the size of SYSDUMP.DMP
3. if SYSDUMP.DMP is smaller than this calculated size:
3.a. $ @SYS$UPDATE:SWAPFILES
3.a.1 leave pagefile sizes unchanged
3.a.2 Enter new (calculated) size of DUMPFILE.DMP
3.b I assume (haven't tried) that if SYSDUMP.DMP is larger than calculated, you won't need to re-create a new dumpfile. But here I may be wrong
4. Reboot the system
5. After system has come up:
6. $ MCR OPCCRASH
7. Boot the system
If step 6 isn't done, I think the dumpfile will NOT be created properly. CRASH on the SRM prompt didn't work (but I may have issued it too early (during boot), I may have neded to wait until system was up).
Anyway, so far so good. Now wait for the next (real) crash...
Thanx to all.
Willem
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2004 06:11 PM
тАО08-10-2004 06:11 PM
Re: bad dumpfile
your attachment shows, that you had a good and big enough (443600. blocks) dumpfile on that system disk. It had been written to under V7.3-2 (you'll see the string V7.3-2 and the nodename, process name and system type in the first block). The file was also perfectly contiguous (just 1 retrieval pointer with the length of the file).
If you want to look just at the file header, use DUMP/HEADER/BLOCK=COUNT=0 !
In your first attempt to create a dump with CTRL-P CRASH, you may have been too early during boot. Once STARTUP executes, the system is ready to write a dump. Did you capture the console output ? It would have told you, if a dump has been written.
Note that you can have AUTOGEN create the dumpfile for you. Just let it run beyond the GENFILES phase. If AUTOGEN creates a new (smaller) dumpfile, don't forget to purge the old one AFTER the next reboot.
As you observed MACHINECHK crashes in ERRLOG.SYS, be aware that there may be situations (due to hardware errors), which prevent the dumpfile write to complete ! This may well explain the message from SDA:
%SDA-F-DUMPINCOMPL, the dump file write was not completed
There is no need to run OPCCRASH to 'create' the dumpfile. @AUTOGEN or @SWAPFILES creates the file. And if the system crashes, it writes the dump into SYSDUMP.DMP.
Now let's wait for the real crash...
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2004 07:15 PM
тАО08-10-2004 07:15 PM
Re: bad dumpfile
thank you for information.
Will be useful next time.
Antonio Vigliotti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2004 07:59 PM
тАО08-10-2004 07:59 PM
Re: bad dumpfile
Anyway, so far so good. Now wait for the next (real) crash...
/quote>
wishing you (and expecting) a looooooooooooong wait!
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2004 09:35 PM
тАО08-10-2004 09:35 PM
Re: bad dumpfile
now there are more questions than answers.
DUMPSTYLE is set to 9 which means selective and compressed dump (bit 0 and 3). See
HELP SYS_PARA DUMPSTYLE in SYSGEN.
But SDA in your log says "...analyzing an Alpha full memory dump in override mode...". Also you get the message %SDA-W-INCDUMPFORM.
But in CLUE logfile you can see "...analyzing an Alpha compressed selective memory dump...".
This looks like your ANA/CRASH is using a different file as CLUE?!?
Please can you provide the console log of a crash and the line with the dumpfile from SHOW DEVICE/SYS SYS$SYSDEVICE:!
Helmut
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-08-2004 08:03 AM
тАО10-08-2004 08:03 AM
Re: bad dumpfile
the CLUE logging is created during startup - and SDA was started using SYS$SYSTEM:SYSDUMP.DMP. So I am puzzled as well now.
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-08-2004 08:06 AM
тАО10-08-2004 08:06 AM
Re: bad dumpfile
Helmuth's suggestion is woirthwhile but first I need to find some machine where I can actually DUMP the screen....
OpenVMS Developer & System Manager
- « Previous
- Next »