system crash out of vxsvc?

This issue has been solved. See solution.
dhofmeister's picture
dhofmeister
October 30th, 2009

i've got an hp-ux 11.23 itanium npar that's crashing repeatedly with the following (as reported by crashinfo).  vea version is 3.2.532 (old i know).  my questions are -- this is coming from vea, yes?  and will going to 5.0 help?  or is this actually a new/unknown problem?      - d  (oh -- the latest 4.1 vxfs patch is installed)

==============  EVENT  ============================
= Event #0 is CT_PANIC on CPU #4;
= p crash_event_t 0xe000000100007000
= p rpb_t 0xe000000100edca70
= Process at 0xe000000212fc4000, pid 3994, "vxsvc"
==============  EVENT  ============================
 

Filed under: , ,
0 votes
Marianne van den Berg 2's picture
Marianne van den Berg 2
3 weeks 4 days ago

We need to know SF version

We need to know SF version installed to search for known problems with that version.
Please post output of:

swlist -l product | egrep -i 'VRTS'

Maybe also a good idea to open a Support call?

0 votes
dhofmeister's picture
dhofmeister
3 weeks 4 days ago

VRTSalloc 4.1 

  VRTSalloc			4.1            VERITAS Volume Manager: VERITAS Intelligent Storage Provisioning 
  VRTSap			2.00.025.005   VERITAS Action Provider 
  VRTSddlpr			b4.1           VERITAS Device Discovery Layer Services Provider 
  VRTSfsman			4.1.001        VERITAS File System Manuals 
  VRTSfspro			4.1k           VERITAS File System Management Services Provider 
  VRTSob			3.2.532.0.100  VERITAS Enterprise Administrator Service 
  VRTSobgui			3.2.532.0.100  VERITAS Enterprise Administrator 
  VRTStep			1.20.028.007   VERITAS Task Exec Provider 
  VRTSvlic			3.02.006c.009  VERITAS License Utilities 
  VRTSvmdoc			4.1.010        VERITAS Volume Manager Documentation 
  VRTSvmpro			4.1.010        VERITAS Volume Manager Management Services Provider 
  VRTSvxfs			4.1.001        VERITAS File System 
  VRTSvxmsa			4.2.1.224      VxMS Application Deployment Package 
  VRTSvxvm			4.1.011        Base VERITAS Volume Manager 4.1 for HP-UX
0 votes
Marianne van den Berg 2's picture
Marianne van den Berg 2
3 weeks 4 days ago

How did you upgrade Storage

Solution

How did you upgrade Storage Foundation without upgrading VRTSob and VRTSobgui? The product installer will by default install/upgrade all packages.
You will have to upgrade these two packages.

0 votes
SOLUTION
dhofmeister's picture
dhofmeister
3 weeks 4 days ago

thank you! i inheirited this,

thank you!

i inheirited this, so i don't know how this got in this state.

afaik, this is no 4.1 patch for ob*.  so it looks like we're headed to 5.0.

0 votes
Marianne van den Berg 2's picture
Marianne van den Berg 2
3 weeks 4 days ago

The ob* packages would have

The ob* packages would have been part of the base 4.1 install media.
Before you upgrade to 5.0, do yourselve a favour and make use of the Veritas Installation Assessment Service: 
vias.symantec.com/vias/vias

The Data Collector option generates a detailed report that shows you whether your system is ready to install or upgrade the specified product.
The General Checklist displays a hardware and software checklist you can use to ensure that your system is ready to install or upgrade the specified product.

0 votes
Gaurav Sangamnerkar's picture
Gaurav Sangamnerkar
3 weeks 1 day ago

Hello, upgrading the depot

Hello,

upgrading the depot will be needed however If you check for release notes for SF 5.0, it doesn't mention anything about fixing any issue for vxsvc.

What I would suggest is to go for 5.0-MP1 with latest rolling patch for VEA...

As per veritas patch central site, latest VEA patch available for 5.0MP1 is RP1..... you can get that from here

https://vias.symantec.com/labs/vpcs/vpcs/patchinfo...

I hope this patch will have a readme, which will tell you about fixed issues with this patch...

this should help...

Gaurav

0 votes
avsrini's picture
avsrini
3 weeks 2 hours ago

Hi,    We only see the

Hi,
 
 We only see the partial output of crashinfo, but looks to be by vxsvc.
But would need to check the whole output to confirm if this is a known
or new issue. Would suggest better to open a support case with us,
and proceed further.

For time being you can stop vxsvc process thus system crash can be
prevented.

 # /sbin/init.d/isisd stop

Regards
Srini

0 votes