How/What to collect with q4 when there is a symptom of hanging on CFS/VxFS/Process issue for HP-UX?

book

Article ID: 100004376

calendar_today

Updated On:

Description

Error Message

[ RELATED  SYMPTOM  ]
- System hung with SF/SFHA/SFCFS/SFORARAC
- Process hung on CFS/VXFS/VXVM
- VCS component Agents hung

Cause

- As q4 utility is the only way to look up the issued threads related to SF family package, it is required to collect either system dump or decent threads eligible for prompt analysis.

Resolution

What needs to get the thread list / process stack list when customer hit any hang symptom on CFS/VxFS/Process issue before forcing system dump?

 
[ Collecting evidence live ]
# q4 /stand/vmunix /dev/kmem
 
After q4 is started
 
Q4>load kthread_t from kthread_list max nkthread next kt_factp
Q4>trace -a -u pile > /tmp/thread.out
Q4>load proc_t from proc_list max nproc next p_factp
Q4> trace -a -u pile > /tmp/proc.out
 
Also the customer can repeat it against system dump file which is provided to Veritas Support Team.
 
 
[ Collecting evidence from the core ]
1.  Please go to the same dir where the system dump file which is provided to us.
2.  # q4 –p
 
After q4 is started
 
Q4>load kthread_t from kthread_list max nkthread next kt_factp
Q4>trace -a -u pile > /tmp/thread1.out
Q4>load proc_t from proc_list max nproc next p_factp
Q4> trace -a -u pile > /tmp/proc1.out
 
This will help Veritas Support Team to get the thread of the running system when issue happened & get the thread from core file.
 
 
#cd /tmp
# tar cvf evidence_case_number.tar thread.out thread1.out proc.out proc1.out

 

 

Issue/Introduction

When the processes running on CFS/VxFS/VxVM on the HP-UX systems see to getting hung or block due to some reason, what is required to collect for the sake of expediting analysis.

Powered by Wolken Software