Error Message

From the "/var/adm/messages" file, you may see similar messages relating to vxloggerd:
 

# grep "vxloggerd" /var/adm/messages
Apr 12 18:17:30 t72-01 genunix: [ID 603404 kern.notice] NOTICE: core_log: vxloggerd[50630] core dumped: /var/cores/core.global.0.vxloggerd
Apr 12 18:38:58 t72-01 genunix: [ID 603404 kern.notice] NOTICE: core_log: vxloggerd[55732] core dumped: /var/cores/core.global.0.vxloggerd
Apr 12 18:42:54 t72-01 genunix: [ID 603404 kern.notice] NOTICE: core_log: vxloggerd[22768] core dumped: /var/cores/core.global.0.vxloggerd

 

Note: mem_debug was enabled on vxloggerd prior to the core file being generated.

The following stack is observed when analyzing the vxlogger core dump file with mdb:

# mdb ./vxloggerd ./core.global.0.vxloggerd_libumem
vxloggerd:core> ::walk thread | ::findstack -v
libc.so.1`set_one_tzname+0x4c(0, 0, 1, ffe4020c, 1bfc00, ff144000)
libc.so.1`set_tzname+0x34(fed4f830, fee103cc, 970a0, ff14f22c, b22c, b000)
libc.so.1`set_zone_default_context+0x60(0, 0, ff144000, 337fd0, b228, b000)
libc.so.1`ltzset_u+0x90(6204b3f6, 1, 0, ff14b284, fed60a40, ff144000)
libc.so.1`localtime_int+0x38(b000, 2208, 2000, fee10300, 6204b3f6, ff144000)
vollogger_process_dump_file+0xfc(175e, fed4ff48, 33a0b8, 0, 72430, fed4fecc)
vollogger_write_thr+0x80(2f, 6de22, fed4ff49, b7400, fed4ff48, 97400)
libc.so.1`_lwp_start(0, 0, 0, 0, 0, 0)
 

vxloggerd dumps core due to memory corruption caused by excessive FMR logging on Solaris 11.4 sparc.

This issue has been reported on InfoScale 7.4.1 and may also occur on InfoScale 7.4.2 and 8.0.This issue is currently under investigation by Veritas Technologies LLC. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software.

However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.


Note: Customers experiencing this issue are encouraged to contact Veritas Technical Support as data is still being collected to assist in resolving this issue.

Once the fix has been confirmed, it will be included in a future patch/update release for InfoScale 8.0.
 

The Veritas Volume Manager (VxVM) Fast mirror resync (FMR) feature allows fast resync of a detached plex, wherein the regions of the volume which are modified/dirtied after a plex is detached are persistently tracked in a bitmap and only those regions are copied/resynced during the plex attach.
 
Workaround:

For now the workaround of disabling FMR logging will avoid the issue.

Disabling FMR logging won't affect the functionality of VxVM or FMR (snapshots, etc), it just means that entries related to FMR won't be seen in the /var/adm/vx/logger.txt files.
 

FMR logging can be disabled using the following command:

# vxtune vol_log_category fmr,vvr,ted,smartio,cvm

 

The vxloggerd daemon is intermittently core dumping on Solaris 11.4 sparc using InfoScale 7.4.1, 7.4.2 and 8.0

Veritas Volume Replicator (VVR) Adaptive synchronous replication uses VxLogger to log the alerts messages for different conditions. These alerts are logged in the system log file and the /etc/vx/log/vxloggerd.log file. These alerts are also sent to the configured users as email notifications.
Note: The email notifications are processed by the vxloggerd daemon. To receive alerts through email, you must ensure that the vxloggerd daemon is running. If you erroneously stop this daemon, it does not start automatically, and must be started manually.

JIRA: STESC-6996