No error, as such, was seen. However, the vxdclid daemon was found to have core dumped. Running the core dump debugger revealed the following stack:
$ gdb ./vxdclid ./core*0
(gdb) set solib-search-path ./
Core was generated by `/opt/VRTSsfmh/bin/vxdclid'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fc61884391c in __strlen_evex () from /usr/lib64/libc.so.6
Thread 1 (Thread 0x7fc616a31700 (LWP 20667)):
#0 0x00007fc61884391c in __strlen_evex () from /usr/lib64/libc.so.6
#1 0x00007fc6187ef29d in vfprintf () from /usr/lib64/libc.so.6
#2 0x00007fc618815aa4 in vsnprintf () from /usr/lib64/libc.so.6
#3 0x00007fc6187f5a13 in snprintf () from /usr/lib64/libc.so.6
#4 0x00007fc617080952 in doVmNotify (a=0x0)
at vxbridge/common/vxlist_sf_notify.c:687
#5 0x00007fc618b661ca in start_thread () from /usr/lib64/libpthread.so.0
#6 0x00007fc6187c08d3 in clone () from /usr/lib64/libc.so.6
A VIOM plug-in issue was determined to be the cause, i.e. part of VIOM software that communicates with Volume Manager
A new plug-in has been provided – please refer to Arctera Support for the fix