Jump to content
RESET Forums (homeservershow.com)

ESXi 5.1 syslog errors on N54L


dougwoodrow
 Share

Recommended Posts

I installed the VMware ESXi 5.1 U2 Installable HP Customized ISO Image on a N54L microserver.

 

I'm able to install and run VMs on it with no apparent problems, but have noticed the following recurring entries in the /var/log/syslog.log file:

2014-11-15T04:08:56Z root: hp-ams-wd: hp-ams start...
2014-11-15T04:08:56Z root: hp-ams start service...
2014-11-15T04:08:56Z hpHelper[1976956]: hp-ams ver 10.0.0-18: System Product Name is ProLiant MicroServer.
2014-11-15T04:08:56Z hpHelper[1976956]: hp-ams ver 10.0.0-18: This program will only run on HP ProLiant Gen8 or newer platforms.
2014-11-15T04:09:08Z sfcbd[1976929]: -#- smx - 1976929 provider exiting due to a SIGSEGV signal
2014-11-15T04:09:46Z sfcbd[1976985]: -#- smx - 1976985 provider exiting due to a SIGSEGV signal
2014-11-15T04:10:01Z crond[2459]: crond: USER root pid 1977021 cmd /sbin/hostd-probe
2014-11-15T04:10:02Z syslog[1974975]: starting hostd probing.
2014-11-15T04:10:17Z syslog[1974975]: hostd probing is done.
2014-11-15T04:10:24Z sfcbd[1976998]: -#- smx - 1976998 provider exiting due to a SIGSEGV signal
2014-11-15T04:11:02Z sfcbd[1975040]: -#- smx - 1975040 provider exiting due to a SIGSEGV signal
2014-11-15T04:11:40Z sfcbd[1975079]: -#- smx - 1975079 provider exiting due to a SIGSEGV signal
2014-11-15T04:12:18Z sfcbd[1975092]: -#- smx - 1975092 provider exiting due to a SIGSEGV signal
2014-11-15T04:12:56Z sfcbd[1977177]: -#- smx - 1977177 provider exiting due to a SIGSEGV signal
2014-11-15T04:13:34Z sfcbd[1977191]: -#- smx - 1977191 provider exiting due to a SIGSEGV signal
2014-11-15T04:13:56Z root: hp-ams-wd: Detected one or more hpHelper process(es) have stopped running.  Restarting...
2014-11-15T04:13:56Z root: hp-ams stop service...
2014-11-15T04:14:02Z root: hp-ams-wd: hp-ams start...
2014-11-15T04:14:02Z root: hp-ams start service...
2014-11-15T04:14:02Z hpHelper[1977266]: hp-ams ver 10.0.0-18: System Product Name is ProLiant MicroServer.
2014-11-15T04:14:02Z hpHelper[1977266]: hp-ams ver 10.0.0-18: This program will only run on HP ProLiant Gen8 or newer platforms.

Can anyone advise how serious these messages are, and how to fix this?

Link to comment
Share on other sites

I think the ISO is for Gen 8 Microservers:

http://h17007.www1.hp.com/us/en/enterprise/servers/supportmatrix/vmware.aspx#.VGd5bPmvCaU

 

The Gen8 MS is the only MS listed in the compatibility guide:

http://www.vmware.com/resources/compatibility/search.php

 

You may want to run a standard version of esxi on the N54L. Make sure you have the latest BIOS on the N54L.

Link to comment
Share on other sites

Thanks schoondoggy, I feared that might be the case when I saw the Gen8 reference.

I was hoping I could just change the configuration somewhere to stop whatever is throwing those errors from running in the first place.

I wonder if I'll lose the P410 RAID controller status information on the vSphere Client if I change to the standard version of ESXi.  Is anyone else here running ESXi on a N54L with a P410 card?
 

P410Status.png

Link to comment
Share on other sites

Thanks schoondoggy, I feared that might be the case when I saw the Gen8 reference.

 

I was hoping I could just change the configuration somewhere to stop whatever is throwing those errors from running in the first place.

 

I wonder if I'll lose the P410 RAID controller status information on the vSphere Client if I change to the standard version of ESXi.  Is anyone else here running ESXi on a N54L with a P410 card?

 

 

 

Yes, I'm running ESXi 5.1 U2 on the N54L with the P410 Smart Array Controller.

 

I'm getting the same errors as you in the syslog.log, which I did not notice until you pointed it out...

I'm not sure what the implications are.

 

What I can tell you is that I'm running this version of ESXi for 5 months now without a problem. (prior to this I was running the HP 5.5 on my old N36L for a long time, but I don't know if I had these errors).

 

For the first 3-4 months I was running the N54L with an Adaptec RAID card. Then I replaced it with the P410 because I wanted to run Xpenology in a VM and could not map RDM with the Adaptec card. My first P410 was faulty and I had a lot of issues. It was then replaced by HP and I'm running this configuration (N54L + P410 + ESXi 5.1) without any problem.

So all in all I'm not sure if these errors have any implications because my system appear to be running fine.

 

Hope this helps.

Link to comment
Share on other sites

Thanks again schoondoggy and yud, you've given me plenty of things to research now :)

 

It looks like I definitely need to un-install the HP AMS package, and possibly ILO as well.

 

The /var/log/vmkernel.log file also contains lots of messages like the following:

cpu0:4365)User: 2744: wantCoreDump : sfcb-smx -enabled : 0

These messages appear to always coincide with the "smx - provider exiting due to a SIGSEGV signal" messages in the syslog log file.

 

I think I'll try starting with the standard vmWare ESXi build, then adding just some of the HP-specific VIBs from their offline bundle.
 

Edited by dougwoodrow
Link to comment
Share on other sites

  • 2 months later...

Has anyone tried the HP Customized 5.1 U3 ?

https://my.vmware.com/group/vmware/details?downloadGroup=HP-ESXI-5.1.0U3-GA&productId=285

 

According to the Support Matrix the Microserver G7 is not supported (or at least not listed)

http://h17007.www1.hp.com/us/en/enterprise/servers/supportmatrix/vmware.aspx#.VOANOy4Rpw0

 

But I was wondering if the errors posted by OP are still occurring.

Edited by yud
Link to comment
Share on other sites

  • 7 months later...

Has anyone tried the HP Customized 5.1 U3 ?

Hi yud,

 

finally got around to installing HP ESXi 5.1 Update3 :)

 

The agentless management service is still not supported on the N54L, but at least the new version does not keep trying (and filling up the log file):

 

2015-10-06T14:15:27Z root: init Running hp-ams.sh start
2015-10-06T14:15:28Z hpHelper[4086]: hp-ams ver 10.2.0-22: Running check for supported platform...
2015-10-06T14:15:28Z root: [hp-ams] HP Agentless Management Service is not supported on this platform.
I've actually upgraded my main ESXi box to a ProLiant ML10v2, and that is supported:

 

2015-10-06T16:30:55Z root: init Running hp-ams.sh start
2015-10-06T16:30:55Z hpHelper[3926]: hp-ams ver 10.2.0-22: Running check for supported platform...
2015-10-06T16:30:55Z root: hp-ams start service...
2015-10-06T16:30:55Z hpHelper[3931]: hp-ams ver 10.2.0-22: Supported platform detected.
2015-10-06T16:30:55Z hpHelper[3931]: hp-ams ver 10.2.0-22: Configuring hpHelper to log to VMware syslog....
2015-10-06T16:30:55Z hpHelper[3943]: hp-ams ver 10.2.0-22 is running...
2015-10-06T16:30:56Z hpHelper[3943]: hp-ams-snmp: Opened HP iLO /vmfs/devices/char/vmkdriver/hpilo-d0ccb15, fd = [7].
2015-10-06T16:30:57Z hpHelper[3943]: ---- hp-ams done with initialize...
2015-10-06T16:31:00Z root: hp-ams start watchdog...
PS It took me 15 minutes to post this, because I kept getting CAPTCHA requests after previewing my post, and then getting thrown back to the main forum menu. :(
Link to comment
Share on other sites

finally got around to installing HP ESXi 5.1 Update3 :)

 

The agentless management service is still not supported on the N54L, but at least the new version does not keep trying (and filling up the log file):

You should just use the standard VMware image and not the custom HP one for the N54L. The N54L design is more akin to a generic PC and you don't have the custom chipset + iLO that the Gen8 Microserver or large Proliants have. You don't need or want the HP customisations which are basically iLO, AMS, management utilities and drivers. Edited by GotNoTime
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...