To resolve this issue, HP Support has provided an updated
hp-ams VIB to stop the excessive logging to the
hpHelper.log file.
For more information, see
HP Proliant Gen8 Servers - ESXi 5: The /var/log/hpHelper.log File Can Grow Very Large and Fill the ESXi 5 RAMDisk.
You can download ESXi offline bundles from HP Support. For more information, see the
HP Support Center.
Note: The preceding links were correct as of June 3, 2014. If you find a link is broken, provide feedback and a VMware employee will update the link. Alternatively, remove the
hpHelper.log file. This prevents the ILO4 management agent reporting on VMkernel or operating system health.
Caution: Remove the
hpHelper.log file only if it is not in use.
To remove the
hpHelper.log file:
- Log in to the ESXi host as the root user.
- Stop the HP Helper management agent by running the command:
/etc/init.d/hp-ams.sh stop
- To remove the hpHelper.log file, run the command:
rm /var/log/hpHelper.log
- To restart the HP Helper management agent, run this command (optional):
/etc/init.d/hp-ams.sh start
Note: If the updated hp-ams VIB is not applied, restarting the HP Helper management agent may cause the symptoms to reappear.
- In the event of a host reboot, run the command:
chkconfig hp-ams.sh off
This command prevents the hp-ams service from starting after a server reboot.
Alternatively, reboot the ESXi host to clear the log files.