Operating System - HP-UX
1833589 Members
3784 Online
110061 Solutions
New Discussion

Re: Save System Crash Dump if needed - Fails

 
SOLVED
Go to solution
Raj Pejathaya
Occasional Advisor

Save System Crash Dump if needed - Fails

Hi,
I have a HP-UX N440 system running HP-UX 11.0. When my system comes up the following 2 show as failed. How do I fix it?

Save System Crash Dump If Needed - Fail
Enable Auxilary Swap Space - Fail.

Thank you in advance.
Raj
14 REPLIES 14
Steven E. Protter
Exalted Contributor

Re: Save System Crash Dump if needed - Fails

/etc/rc.config.d/savecrash

set the first variable to 1 and save crash will be enabled.

Swap space must be set to 50% of RAM or you'll get errors and won't get a crash dump anyway.

/var/adm/crash is where the crash dump directories are created.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Sridhar Bhaskarla
Honored Contributor

Re: Save System Crash Dump if needed - Fails

Hi Raj,

You will get more errors in /etc/rc.log. Search for the strings 'swap' and 'dump'.

Post the following details.

1. Your /etc/fstab.
2. Output of /sbin/crashconf
3. Errors in your /etc/rc.log

Most likely the secondary swap configured in /etc/fstab is not accessable.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Raj Pejathaya
Occasional Advisor

Re: Save System Crash Dump if needed - Fails

Hi Sri,
My fstab is as follows
dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /tmp vxfs delaylog 0 2
/dev/vg00/lvol6 /opt vxfs delaylog 0 2
/dev/vg00/lvol7 /usr vxfs delaylog 0 2
/dev/vg00/lvol8 /var vxfs delaylog 0 2
/dev/vg01/lvol1 /db1 vxfs delaylog 0 2
/dev/vg01/lvol2 /db2 vxfs delaylog 0 2
/dev/vg01/lvol3 /db3 vxfs delaylog 0 2
/dev/vg01/lvol4 /db4 vxfs delaylog 0 2
/dev/vg01/lvol5 /db5 vxfs delaylog 0 2
/dev/vg01/lvol6 /db6 vxfs delaylog,nodatainlog,largefiles,rw,suid 0 2
/dev/vg01/lvol7 /db7 vxfs delaylog,nodatainlog,largefiles,rw,suid 0 2
/dev/vg02/lvvertel /vertel vxfs delaylog 0 2
/dev/vg02/lvcommon /common vxfs delaylog 0 2
/dev/vg02/lvadmin /admin vxfs delaylog 0 2
/dev/vg00/lvol5 /home vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vg00/lvol9 ... swap pri=1 0 0


on my rc.log file, I just had to trim it to 0 as it was eating into my hard disk.

savecrash is a executable right? Do you want me to run it ? please let me know.
Regards
Raj

Raj Pejathaya
Occasional Advisor

Re: Save System Crash Dump if needed - Fails

Sri,
Sorry about "savecrash". You asked me about "crashconf". My question is , do you want me to run it ?
Please let me know.
Raj
Sridhar Bhaskarla
Honored Contributor

Re: Save System Crash Dump if needed - Fails

Hi Raj,

Yes. Run /sbin/crashconf and it will display your dump information.

Also post your 'swapinfo -t' command. If you don't see /dev/vg00/lvol9 in it, then run 'swapon -a' and see what errors you get.

Look for errors in your /etc/rc.log.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Raj Pejathaya
Occasional Advisor

Re: Save System Crash Dump if needed - Fails

info on crashconf

/sbin/crashconf
CLASS PAGES INCLUDED IN DUMP DESCRIPTION
-------- ---------- ---------------- -------------------------------------
UNUSED 276653 no, by default unused pages
USERPG 126510 no, by default user process pages
BCACHE 68782 no, by default buffer cache pages
KCODE 2092 no, by default kernel code pages
USTACK 2739 yes, by default user process stacks
FSDATA 258 yes, by default file system metadata
KDDATA 19860 yes, by default kernel dynamic data
KSDATA 27394 yes, by default kernel static data

Total pages on system: 524288
Total pages included in dump: 50251

DEVICE OFFSET(kB) SIZE (kB) LOGICAL VOL. NAME
------------ ---------- ---------- ------------ -------------------------
31:0x016000 88928 1048576 64:0x000002 /dev/vg00/lvol2
31:0x04b000 1024 1048576 64:0x000009 /dev/vg00/lvol9
----------
2097152

swapinfo -t info

swapinfo -t
Kb Kb Kb PCT START/ Kb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 1048576 0 1048576 0% 0 - 1 /dev/vg00/lvol2
dev 1048576 0 1048576 0% 0 - 1 /dev/vg00/lvol9
reserve - 598464 -598464
memory 1569284 189820 1379464 12%
total 3666436 788284 2878152 22% - 0 -

Sridhar Bhaskarla
Honored Contributor

Re: Save System Crash Dump if needed - Fails

Hi Raj,

Your 'swapinfo' and 'crashconf' indicate that the logical volume lvol9 is getting configured correctly for both swap and dump. I believe lvol9 is getting added through your BDRA configuration (lvlnboot -v) as there is no corresponding entry for dump in /etc/fstab.

So, unless I look at your /etc/rc.log it will be hard to figure out the problem. Next time copy rc.log to somewhere before deleting it.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Raj Pejathaya
Occasional Advisor

Re: Save System Crash Dump if needed - Fails

Sri,
My lvlnboot -v command has the following output

lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t6d0 (0/0/2/0.6.0) -- Boot Disk
/dev/dsk/c4t11d0 (1/12/0/0.11.0)
/dev/dsk/c4t6d0 (1/12/0/0.6.0)
Boot: lvol1 on: /dev/dsk/c1t6d0
Root: lvol3 on: /dev/dsk/c1t6d0
Swap: lvol2 on: /dev/dsk/c1t6d0
Dump: lvol2 on: /dev/dsk/c1t6d0, 0
Dump: lvol9 on: /dev/dsk/c4t11d0, 1

lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vg02".
Sridhar Bhaskarla
Honored Contributor
Solution

Re: Save System Crash Dump if needed - Fails

Yep. Your lvlnboot output confirms my previous assumption.

I don't think there is anyway to find out why you saw those errors now as you zeroed out your rc.log file. See if you have rc.log.old file atleast and if there are any errors if this problem existed even before.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Raj Pejathaya
Occasional Advisor

Re: Save System Crash Dump if needed - Fails

Thanks for the info. I will look at my rc.log in the future for any errors.
Raj
Sundar_7
Honored Contributor

Re: Save System Crash Dump if needed - Fails

Raj,

you can try running the savecrash script from the command line to figure out any error messages

# /sbin/init.d/savecrash start

Post the output from the above command.

- Sundar
Learn What to do ,How to do and more importantly When to do ?
Randy Brown_1
Frequent Advisor

Re: Save System Crash Dump if needed - Fails

I am also seeing
Enable Auxilary Swap Space - Fail.
when I boot.

Here is what is in the rc.log file:

Enable auxiliary swap space
Output from "/sbin/rc1.d/S500swap_start start":
----------------------------
Enabling device paging on /dev/vg00/lvol9.
/usr/sbin/swapon: /dev/vg00/lvol9 is already enabled for paging.
Enabling device paging on /dev/vg00/lvol2.
Enabling device paging on /dev/vg00/lvol5.
Warning: swapon returned exit code: 1
"/sbin/rc1.d/S500swap_start start" FAILED

Here are the relevant swap entries in the /etc/fstab file as well:

/dev/vg00/lvol9 ... swap pri=0 0 0
/dev/vg00/lvol2 ... swap pri=1 0 0
/dev/vg00/lvol5 ... swap pri=1 0 0

Is the entry in fstab redundant to another operation, maybe?

Any help would greatly appreciated.

Thanks in advance.

Randy Brown_1
Frequent Advisor

Re: Save System Crash Dump if needed - Fails

Sorry, I forgot my system info.

This is a J5000 running HP-UX 11.i

Randy
Randy Brown_1
Frequent Advisor

Re: Save System Crash Dump if needed - Fails

Here is the swapinfo -t output too:

/dev/vg00/lvol5 ... swap pri=1 0 0
[clifford_root]$swapinfo -t
Kb Kb Kb PCT START/ Kb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 1024000 0 1024000 0% 0 - 1 /dev/vg00/lvol9
dev 1024000 0 1024000 0% 0 - 1 /dev/vg00/lvol2
dev 1024000 0 1024000 0% 0 - 1 /dev/vg00/lvol5
reserve - 195308 -195308
memory 1554092 310488 1243604 20%
total 4626092 505796 4120296 11% - 0 -

Randy