Error message is seen for Apache resource when zone is in transient state
If the Apache resource is probed when the zone is getting started, the following error message is logged:
Argument "VCS ERROR V-16-1-10600 Cannot connect to VCS engine\n"
isn't numeric in numeric ge (>=) at /opt/VRTSvcs/bin/Apache/Apache.pm
line 452.
VCS ERROR V-16-1-10600 Cannot connect to VCS engine
LogInt(halog call failed):TAG:E:20314 <Apache::ArgsValid> SecondLevel
MonitorTimeOut must be less than MonitorTimeOut.
Workaround: You can ignore this message. When the zone is started completely, the
halog command does not fail and Apache agent monitor runs successfully.
Related information