Vmware 7.0.3 event every 5 minutes

[Hadin]

Hello,

We have Proliant DL360 Gen11 (GreenLake CompOpsManagment subscription and installed updates: Gen11 Patch 2024.04.00.02 + SPP 2024.04.00.00 (Jul 23, 2024))

Vmware 7.0.3 is installed on the server (custom image from HPE ESXi-7.0.3-23794027-HPE -703.0.0.11.6.0.5-May2024) standalone (no vCenter)

After installing Vmware, the following event is created in the ESXi Host Client monitoring events every 5 minutes:

"User root@127.0.0.1 logged out (login time: Friday, 06 September, 2024 12:10:20 PM, number of API invocations: 7, user agent: pyvmomi Python/3.8.18 (VMkernel; 7.0.3; x86_64))"

hostd.log:

2024-09-06T12:05:08.055Z info hostd[2099573] [Originator@6876 sub=Default opID=esxcli-25-8f2b] Accepted password for user root from 127.0.0.1
2024-09-06T12:05:08.055Z warning hostd[2099573] [Originator@6876 sub=Vimsvc opID=esxcli-25-8f2b] Refresh function is not configured.User data can't be added to scheduler.User name: root
2024-09-06T12:05:08.056Z info hostd[2099573] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=esxcli-25-8f2b] Event 21747 : User root@127.0.0.1 logged in as pyvmomi Python/3.8.18 (VMkernel; 7.0.3; x86_64)
2024-09-06T12:05:08.084Z info hostd[2099469] [Originator@6876 sub=Solo.VmwareCLI opID=esxcli-25-8f31 user=root] Dispatch get
2024-09-06T12:05:08.084Z info hostd[2099469] [Originator@6876 sub=Solo.VmwareCLI opID=esxcli-25-8f31 user=root] Dispatch get done
2024-09-06T12:05:08.085Z info hostd[2102402] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=esxcli-25-8f32 user=root] Event 21748 : User root@127.0.0.1 logged out (login time: Friday, 06 September, 2024 12:05:08 PM, number of API invocations: 7, user agent: pyvmomi Python/3.8.18 (VMkernel; 7.0.3; x86_64))

syslog.log:

2024-09-06T12:05:00.542Z crond[2098053]: USER root pid 9488955 cmd /bin/hostd-probe.sh ++group=host/vim/vmvisor/hostd-probe/stats/sh

As an experiment, I tried a clean installation on Proliant DL360 Gen10, events also appear in the ESXi Host Client monitoring.

Any ideas ? 

Thanks.

Iurii.

[shiva_jr]

Hi @Hadin ,
     This might to resolved on the 7.0 U3 Oct 26 2021 vSphere 7.0 U3 Build 18644231. Please refer this Advisory.

This is the workaround:  ->

To identify the PID for the vnicen.sh script
ps -c | grep vnic

Example
ps -c |grep vnic
527045 527045 sh /bin/sh /etc/init.d/vnicen.sh start
529575 529575 grep grep vnic
Use PID of the vnicen.sh to stop the vnicen.sh script
Kill [PID of vnicen.sh]
Example
kill 527045
To ensure that the vnicen.sh script does not restart after a reboot
chkconfig vnicen.sh off
To confirm this setting
chkconfig --list | grep vnicen
vnicen.sh off

Regards,
Shiva_JR
Please mark as 'Accepted solution' and give 'Kudos' if my post worked.

[Rajaram02]

Hi Hadin,

Fixed an issue where Multiple HOST REST login/logout events happen in iLO when iSUT is running in service mode 
https://support.hpe.com/hpesc/public/docDisplay?docId=sd00001033en_us&docLocale=en_US&page=s_fixes.html

Workaround
• De-Register the SUT utility:
# sut -deregister

• Uninstall the SUT component:
# esxcli software component remove –n sutComponent

There was a fix included in iSUT v2.9.1
 https://support.hpe.com/hpesc/public/docDisplay?docId=sd00001033en_us&docLocale=en_US&page=s_fixes.html
Fixed an issue where Multiple HOST REST login/logout events happen in iLO when iSUT is running in service mode.

[Hadin]

Hi @shiva_jr 

Thanks for the answer, I saw this topic, my situation is a little different:

As I wrote, the latest custom version of esxi has already been installed and in the situation indicated in the link in syslog.log there is a characteristic entry that I do not have:

root: vusb:
root: VIRTUAL NIC:NO VUSB0 AVAILABLE
root: Call wait loop
root: Virtual NIC: in wait loop

In any case, I followed the steps indicated in the solution and unfortunately it did not help.

[Hadin]

Hi @Rajaram02 

thanks for the answer, the link you provided talks about the old version of isut and, as far as I understand, about multiple inputs/outputs in the ILO logs. It also says that this problem was fixed in version 2.9.1, but we have a much newer version installed:

Integrated Smart Update Tools version 5.1.0.

UPD:

I noticed the launch timing of isut was 5 minutes (this is exactly the period when events appear in the logs). After that, I stopped the isut service and the events stopped appearing. Since the problem is related to isut, please advise:

1. Is this behavior normal and I don’t have to worry about 300 events per day or log overflow for some time (taking into account that I will connect this server and several more to vCenter) or for some other reason?

2. If this behavior is not normal, then it seems to me that there are the following options:

- Wait for an update to fix this problem or try installing the previous version
- Switch isut to OnDemand mode
- Change poll timing
- Remove isut

I assume that the option of changing the pool interval will be the most suitable, since in other cases it either remains as is or I lose functionality and automation.

P.S. Thanks a lot for the tip from isut.

[Rajaram02]

Please log case with HPE Hardware team to check this.

[Hadin]

The case was created, waiting an answer from support. As fast as will be an answer i will post in topic, maybe this informaition wiil be usefull for some one also.

Thank you for help!

[Hadin]

Support answer:

"Problem Resolution: Vmware event every 5 minutes shows that this is software issue rather than HW issue. Kindly ask you to resolve Vmware problem directly with the customer of provide actin plan for HW related activities"

It appears that generating an event in VMware Host Client for isut requests is normal behavior.

Thanks everyone for your help!