02-01-2014 08:53 AM
I have upgraded a solaris9 machine from vxvm 4 to 5.1sp1. I followed the recommendations to install the VRSTobgui compents for VEA, since it's no longer packaged with 5.1. /etc/init.d/isisd does not start on machine boot. When I start it manually, I get a "Error reading registry" I notice that the server no longer has the VRTSobc directory in /opt. There is a VRTSob however. This machine previously had Cluster server running on it, I removed it before I upgraded the Volume Manager. Volume Manger is function perfectly, just trying to get the VEAgui by x-window to work again.
thanks
02-01-2014 09:33 AM
This the error when I start vxsvc
psVxVM Provider initialization warning: Configuration daemon can't speak protocol version
02-01-2014 10:00 PM
Hi,
did you got the VRTSob upgraded as well ?
Check out below technote, you can check the versions of software described in technote below
http://www.symantec.com/docs/TECH153663
G
02-02-2014 03:20 AM
So have you installed VEA available by following link
at http://www.symantec.com/operations-manager/tools-resources
Also I think you need VRTSsfmh installed as I believe this replaces some of the components that feed into the VRTSob service like for example:
VRTSaa - Veritas Enterprise Administrator action agent which in 5.1 is consolidated into VRTSsfmh.
Mike
02-02-2014 07:12 AM
Yes, it is updated, here is the output:
root@atloradb2:/# > pkginfo -l VRTSob |grep PSTAMP
PSTAMP: 5.1.100.000-5.1SP1-2010-04-17-VEA-3.4.289.0
02-02-2014 07:20 AM
Looks like it is installed, here is the output:
root@atloradb2:/# > pkginfo -l VRTSobgui
PKGINST: VRTSobgui
NAME: Veritas Enterprise Administrator by Symantec
CATEGORY: application
ARCH: sparc
VERSION: 3.4.30.0
BASEDIR: /opt/VRTSob
VENDOR: Symantec Corporation
DESC: Enterprise Administrator, Binaries
PSTAMP: VEA-3.4.30.0-August 8, 2012
INSTDATE: Jan 29 2014 21:40
EMAIL: support@veritas.com
STATUS: completely installed
FILES: 947 installed pathnames
6 shared pathnames
126 directories
98 executables
322484 blocks used (approx)
Is this one the wrong version?
root@atloradb2:/# > pkginfo -l VRTSsfmh
PKGINST: VRTSsfmh
NAME: Veritas Operations Manager Managed Host by Symantec
CATEGORY: application
ARCH: sparc
VERSION: 3.1.429.0
BASEDIR: /
VENDOR: Symantec Corporation
DESC: Veritas Operations Manager Managed Host
PSTAMP: VRTSsfmh-3.1.429.0-Wed Sep 22 21:26:45 2010
INSTDATE: Jan 29 2014 18:54
EMAIL: support@veritas.com
STATUS: completely installed
FILES: 2059 installed pathnames
8 shared pathnames
269 directories
1079 executables
163001 blocks used (approx)
02-02-2014 07:35 AM
Yes VRTSobgui is installed as well as VRTSsfmh.
02-03-2014 08:11 AM
So I did a remove and re-added the patch from the TECH153663, even though my system was indicating SP1 on the pkginfo . My situation is slightly modified however. I can connect to the VEA from another machine running VEA using X-windows. However I still have the issue where I cannot see Controllers, Disk Groups, Disks, or Enclosures, errors that are indicated in TECH153663. However, as I said, the pkginfo is showing the correct version. Anyone have any ideas ? Also why the system running 5.1 wont open an X-window directly. I know X-windows is working as I can run other X-window applications from same machine.
Thanks
Ed
02-03-2014 09:40 AM
Here is the startup log for isisd. (attached)
02-19-2014 12:51 AM
What happens if you run below command
/etc/init.d/vxpal.StorageAgent start
Also, do you have VRTSvmpro package installed ?
G