komanek
Enthusiast
Enthusiast

syslog errors after upgrade to 5i

Hello,

I have 4x ibm x3650m2 running esx 4.1u2 (not esxi) + netapp filer as remote storage. vCenter already upgraded tp 5.0u1. I upgraded first of my hosts to esxi 5.0u1, trying to learn from this before upgrading the other hosts too. But there are some errors in syslog which I do not observe in the old esx 4.1 environment.

1. some failures on the local server drive (mirror of two scsi disks), cca every 5 minutes:

<181>2012-05-15T20:13:29.932Z esx1-mng.natur.cuni.cz vmkernel: cpu1:2049)ScsiDeviceIO: 2322: Cmd(0x4124006f1000) 0x12, CmdSN 0x4af9 from world 0 to dev "naa.600508e000000000b20c65deec451409" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2. http service error, regularily every 5 minutes:
<166>2012-05-15T20:14:21.147Z esx1-mng.natur.cuni.cz Hostd: [FFD6AAC0 info 'Vmomi'] Activation [N5Vmomi10ActivationE:0x34bcf138] : Invoke done [waitForUpdates] on [vmodl.query.PropertyCollector:ha-property-collector]
<166>2012-05-15T20:14:21.147Z esx1-mng.natur.cuni.cz Hostd: [FFD6AAC0 info 'Vmomi'] Throw vmodl.fault.RequestCanceled
<166>2012-05-15T20:14:21.147Z esx1-mng.natur.cuni.cz Hostd: [FFD6AAC0 info 'Vmomi'] Result:
<166>2012-05-15T20:14:21.147Z esx1-mng.natur.cuni.cz Hostd: --> (vmodl.fault.RequestCanceled) {
<166>2012-05-15T20:14:21.147Z esx1-mng.natur.cuni.cz Hostd: -->    dynamicType = <unset>,
<166>2012-05-15T20:14:21.147Z esx1-mng.natur.cuni.cz Hostd: -->    faultCause = (vmodl.MethodFault) null,
<166>2012-05-15T20:14:21.147Z esx1-mng.natur.cuni.cz Hostd: -->    msg = "",
<166>2012-05-15T20:14:21.147Z esx1-mng.natur.cuni.cz Hostd: --> }
<166>2012-05-15T20:14:21.148Z esx1-mng.natur.cuni.cz Hostd: [3520EB90 error 'SoapAdapter.HTTPService'] HTTP Transaction failed on stream TCP(local=127.0.0.1:0, peer=127.0.0.1:57993) with error N7Vmacore15SystemExceptionE(Connection reset by peer)

3. no idea what it could be:

<166>2012-05-15T20:24:47.871Z esx1-mng.natur.cuni.cz Vpxa: [34FDAB90 info 'Default' opID=HB-host-9@216-d885556c-54] [VpxLRO] -- BEGIN session[52698378-bfc7-eaa9-5c9d-b6c4d486251f]52cfdd80-c0e6-5018-ac15-046666a9cf8c --  -- vpxapi.VpxaService.retrieveChanges -- 52698378-bfc7-eaa9-5c9d-b6c4d486251f

<166>2012-05-15T20:24:47.935Z esx1-mng.natur.cuni.cz Hostd: [34E81B90 error 'Default' opID=HB-host-9@216-d885556c-54] Unable to parse MaxRam value:

<166>2012-05-15T20:24:47.936Z esx1-mng.natur.cuni.cz Hostd: [34E81B90 error 'Default' opID=HB-host-9@216-d885556c-54] Unable to parse MaxRamPerCpu value:

<166>2012-05-15T20:24:47.936Z esx1-mng.natur.cuni.cz Hostd: [34E81B90 error 'Default' opID=HB-host-9@216-d885556c-54] Unable to parse MinRamPerCpu value:

<166>2012-05-15T20:24:47.938Z esx1-mng.natur.cuni.cz Vpxa: [34FDAB90 info 'Default' opID=HB-host-9@216-d885556c-54] [VpxLRO] -- FINISH session[52698378-bfc7-eaa9-5c9d-b6c4d486251f]52cfdd80-c0e6-5018-ac15-046666a9cf8c --  -- vpxapi.VpxaService.retrieveChanges -- 52698378-bfc7-eaa9-5c9d-b6c4d486251f

From the subjective point of view, the server is working, virtual machines run on it with no visible problem, vmotion is working, no errors or warnings in vcenter GUI client regarding this host.

Is it safe to continue with the upgrades or is it something serious ?

Thanks,

David

13 Replies
komanek
Enthusiast
Enthusiast

It seems I am the only one experiencing this kind of errors. After upgrading all four hosts these errors are present on all of them.

0 Kudos
firestartah
Virtuoso
Virtuoso

Have you checked that the ESXi firewall isn't blocking some of the ports you're using? Also are you using host profiles?

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful". Gregg http://thesaffageek.co.uk
0 Kudos
firestartah
Virtuoso
Virtuoso

Hi

I was looking up your error:

[3520EB90 error 'SoapAdapter.HTTPService'] HTTP Transaction failed on stream TCP(local=127.0.0.1:0, peer=127.0.0.1:57993) with error N7Vmacore15SystemExceptionE(Connection reset by peer)
If you found this or other information useful, please consider awarding points for "Correct" or "Helpful". Gregg http://thesaffageek.co.uk
0 Kudos
komanek
Enthusiast
Enthusiast

Thanks,

I have nothing special running on the hosts, the firewall is on, but it is in thsame state as when it was on ESX 4.1, withe one exception: I allowed outgoing syslog traffic to remote syslog server, but it has no influnce on my problem as I already tested.

I already read the KB article you mention, but it seems to me the error message is slightly different. But if it still can be safely ignored, I will be happy, but I am not sure.

David

0 Kudos
KawasakiVM
Contributor
Contributor

my SUT`s also had same message repeating,  Did you find the cause of this and a possible solution?

Thanks !

John

0 Kudos
komanek
Enthusiast
Enthusiast

No, I started to ignore it until 5.0U2 or something similar. I see the same on another cluster which consists of newly installed ESXi hosts (no upgrades, clean new hardware). So I let this thread unanswered in case somebody comes up with a solution or some patch will resolve this silently 🙂

0 Kudos
HenS
Contributor
Contributor

Hi,

We are seeing the same messages (fully patched esxi 5.0 (build 768111).

Did you ever get this solved ?

Regards,

Hen

0 Kudos
komanek
Enthusiast
Enthusiast

Hello,

no, it is still the same (I am now on build 821926 since the last week updates). I was not able to find anything what really does not work with respect to this. The only warning I have in vpx client is about the LDAP component, which is expected because my server is not part of a windows domain. But I don't thing LDAP should generate SOAP requests, so seems unlikely for me to be corellated with.

David

0 Kudos
wayne7215
Contributor
Contributor

We had the same error with 5.0 and right now also in 5.1  799733 :smileylaugh:

10-10-2012 15:26:55 Local4.Info esx2 2012-10-10T13:26:55.222Z ESX2.x.ads Hostd: [22781B90 error 'Default' opID=HB-host-4623@589-7a8e9152-a7] Unable to parse MinRamPerCpu value:
10-10-2012 15:26:55 Local4.Info esx2 2012-10-10T13:26:55.222Z ESX2.x.ads Hostd: [22781B90 error 'Default' opID=HB-host-4623@589-7a8e9152-a7] Unable to parse MaxRamPerCpu value:
10-10-2012 15:26:55 Local4.Info esx2 2012-10-10T13:26:55.222Z ESX2.x.ads Hostd: [22781B90 error 'Default' opID=HB-host-4623@589-7a8e9152-a7] Unable to parse MaxRam value:

0 Kudos
JMSAdmin
Contributor
Contributor

I have the same errors on all of my host logs, ESXi5.0 821926.  Any resolution?

0 Kudos
JMSAdmin
Contributor
Contributor

Not sure if you have resolved your issue, but I opened a case with support today and below is the response:

>> This is a known cosmetic issue and can be safely  ignored as there is no underlying issue with the license being used, it could be resolved in the next release update. <<

Thanks!

komanek
Enthusiast
Enthusiast

Thank you. So I am closing this as a log files garbage diluting the real messages 🙂

0 Kudos
wayne7215
Contributor
Contributor

Almost 1 year later, we are on build 1021289 and the "cosmetic error" is still there :smileysilly: