Error Message

From /var/log/messages:

systemd: CmdServer.service: control process exited, code=exited status=1
systemd: Failed to start VCS Command Server.
systemd: Unit CmdServer.service entered failed state.
systemd: CmdServer.service failed.
 

A new attribute to control the start/stop of CmdServer was introduced in InfoScale 7.4.1 Patch 1200. The attribute is STARTCMDSERVER and exists in the /etc/sysconfig/vcs. When set to 0, it prevents the CmdServer from starting. More information here: Veritas InfoScale 7.4.1 Patch 1200 Release Notes - Linux

These messages are normal if you have set the STARTCMDSERVER attribute to 0 and can be ignored.

• If you don't need the CmdServer running, but don't want to see a failed SystemD state for CmdServer.service, you can "mask" the service. This will leave CmdServer disabled but prevent systemD from reporting it as failed.
  1. # systemctl mask CmdServer.service
      
• If you are using the Java GUI to manage your InfoScale cluster, then you need to start the CmdServer. You can configure the CmdServer to start by changing the value in /etc/sysconfi/vcs:
  1. Set the STARTCMDSERVER value from 0 to 1 in /etc/sysconfig/vcs
     • STARTCMDSERVER=1
  2. Start CmdServer
     • # systemctl start CmdServer.service

CmdServer will not start