If this issue occurs, /var/svc/log/system-vxvm-vxvm-configure:default.log indicates that a script or command located in the / directory has been executed.
example:
ABC Script ran!!
/lib/svc/method/vxvm-configure[241]: abc.sh: not found
/lib/svc/method/vxvm-configure[242]: abc.sh: not found
/lib/svc/method/vxvm-configure[243]: abc.sh: not found
/lib/svc/method/vxvm-configure[244]: app/: cannot execute
In this example, abc.sh is located in the / directory and just echoes "ABC script ran !!". vxvm-configure launched abc.sh.
This is due to the following lines in the /lib/svc/method/vxvm-configure file.
5 lines from line 241:
241 /*
242 * The VRTS_vxvm_link.so library has changed to 64-bit from 32-bit
243 * between Solaris 11.3 and Solaris 11.4. Thus copy the appropriate
244 * library based on the appropriate version
245 */
5 lines from line 263:
263 /*
264 * The VRTS_vxvm_link.so library has changed to 64-bit from 32-bit
265 * between Solaris 11.3 and Solaris 11.4. Thus copy the appropriate
266 * library based on the appropriate version
267 */
"/*" tris to run any files on / directory.
This issue will not occur if the vxvm-configure file does not have lines that match the above.
Workaround1:
Move your script or command file from the / directory to another path, or place a dummy file named aaa in the / directory. This will prevent the harm caused by this problem.
Workaround2:
The issue can be fixed by editing /lib/svc/method/vxvm-configure file as follows.
5 lines from line 241:
241 #
242 # The VRTS_vxvm_link.so library has changed to 64-bit from 32-bit
243 # between Solaris 11.3 and Solaris 11.4. Thus copy the appropriate
244 # library based on the appropriate version
245 #
5 lines from line 263:
263 #
264 # The VRTS_vxvm_link.so library has changed to 64-bit from 32-bit
265 # between Solaris 11.3 and Solaris 11.4. Thus copy the appropriate
266 # library based on the appropriate version
267 #
As script modifications can cause serious other problems, it is not recommended and supported.
The operation should be done carefully and at your own risk.
Both workarounds are temporary solutions until the issue get fixed.
This article applies to following product versions.
Veritas InfoScale Foundation 7.4.2 ( Solaris 11)
Veritas InfoScale Storage 7.4.2 ( Solaris 11)
Veritas InfoScale Enterprise 7.4.2 ( Solaris 11)
Earlier versions with updates(HotFix/Patch) including fixes for the following bug
(3968334) Solaris 11.4: Appropriate library VRTS_vxvm_link.so is not copied on the system after OS upgrade.