"Unit <service> entered failed state" is reported for vcsmm and vxfs_replication on RHEL 7

book

Article ID: 100032309

calendar_today

Updated On:

Description

Reported during vcsmm init:

Apr  5 16:13:59 server1 vcsmm: Starting VCSMM:
Apr  5 16:13:59 server1 vcsmm: This script is not allowed to start VCSMM. VCSMM_START is not 1
Apr  5 16:13:59 server1 systemd: vcsmm.service: control process exited, code=exited status=2
Apr  5 16:13:59 server1 systemd: Failed to start SYSV: Veritas Membership Manager.
Apr  5 16:13:59 server1 systemd: Unit vcsmm.service entered failed state.
Apr  5 16:13:59 server1 systemd: vcsmm.service failed.

Reported during vxfs_replication init:

Apr  5 11:16:28 server1 vxfs_replication: Starting replication daemon disabled
Apr  5 11:16:28 server1 systemd: vxfs_replication.service: control process exited, code=exited status=2
Apr  5 11:16:28 server1 systemd: Failed to start LSB: VxFS replication scheduler and daemon.
Apr  5 11:16:28 server1 systemd: Unit vxfs_replication.service entered failed state.
Apr  5 11:16:28 server1 systemd: vxfs_replication.service failed.

Cause

InfoScale Enterprise 7 installs the VRTSdbac package. This contains the vcsmm services, and creates the vxfs_replication service. By default, both service will not be enabled. The error message has no impact on product functionality.

These init scripts will exit with a status of 2:
  • /etc/init.d/vcsmm
  • /etc/init.d/vxfs_replication

Red Hat Enterprise Linux (RHEL) 7 systemd interprets the exit status 2 as a service fault. It logs it as an error in the syslog.

Resolution

Those errors can be prevented by disabling the services using following commands:

# chkconfig vcsmm off

# chkconfig vxfs_replication off

 

Issue/Introduction

The Red Hat Enterprise Linux (RHEL) 7 syslog records an error stating "Unit <service> entered failed state" for vcsmm and vxfs_replication.

Powered by Wolken Software