"vxfen.service start operation timed out. Terminating" appears when vxfen attempts to start after a system reboot
Article ID: 100042554
Updated On:
Description
Error Message
Mar 21 18:49:58 host02 systemd: vxfen.service start operation timed out. Terminating.
Mar 21 18:49:58 host02 systemd: Failed to start VERITAS I/O Fencing (VxFEN).
Mar 21 18:49:58 host02 systemd: Unit vxfen.service entered failed state.
Mar 21 18:49:58 host02 systemd: vxfen.service failed.
Cause
The unit service file may take more time than the default timeout value to stop or start the service. In this scenario, the service goes into the 'failed' state.
Resolution
Add a custom timeout value to the unit service file. The TimeoutSec parameter lets us configure the amount of time, in seconds, that the system must wait before it reports that the start or stop operation of a service has failed.
# vi /usr/lib/systemd/system/vxfen.service
[Unit]
Description=VERITAS I/O Fencing (VxFEN)
SourcePath=/opt/VRTSvcs/vxfen/bin/vxfen
After=multi-user.target graphical.target syslog.target veki.service llt.service gab.service
Conflicts=shutdown.target reboot.target
[Service]
Type=forking
Restart=no
...
...
TimeoutSec=300
[Install]
WantedBy=multi-user.target graphical.target
# systemctl --system daemon-reload
# systemctl start vxfen
Issue/Introduction
vxfen service does not start after a system reboot on RHEL (Red Hat Enterprise Linux) 7.x
Was this article helpful?
Yes
No
Powered by
