System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Instant capacity error message: The following low-level WBEM error occurred: Empty HTTP response mes

kenken_3
Regular Advisor

Instant capacity error message: The following low-level WBEM error occurred: Empty HTTP response mes

Hi,

I have one rp8440 server and there are a few Vpars in the npar. One of my server keeps getting error messages in the syslog "icapd: ERROR: The following low-level error occurred:ERROR: The following low-level WBEM error occurred: Empty HTTP response message"

I checked through the web and it is said it is a known problem "ERROR: The following low-level WBEM error occurred: Locking or unlocking the target failed.


This is due to contention for system resources from the various partitions in the complex. If these messages are received, retry the Instant Capacity operation."

Does that mean I can ignore this error message? Anyone else encountered the same problem before?

thanks,
ken

wang & wang
4 REPLIES

Re: Instant capacity error message: The following low-level WBEM error occurred: Empty HTTP response mes

well are icapd and cimserver running?

Does icapstatus return with no errors and an indication that it has collected data from all partitions?

HTH

Duncan

HTH

Duncan
kenken_3
Regular Advisor

Re: Instant capacity error message: The following low-level WBEM error occurred: Empty HTTP response mes

# icapstatus
Software version: B.08.01
System ID: hostname
Serial number: Serialno
Product number: A9958A
Unique ID: Z3e13728eab003ffd
System contact e-mail: Not set
From e-mail: Set to the default ('adm')
Asset reporting: on
Temporary capacity warning period: 15 days
Exception status: No exception

Local Virtual Partition Status
------------------------------
Total number of assigned cores: 2
Number of active assigned cores: 2
Number of inactive assigned cores: 0
Additional cores that can be assigned with current usage rights: 0
Number of cores that could be assigned with additional usage rights: 2
Number of cores that can be assigned with temporary capacity: 0
Number of cores currently unavailable for assignment: 0

Local nPartition Status
-----------------------
Total number of configured cores: 16
Number of Intended Active cores: 16
Number of active cores: 14
Number of inactive cores: 2

Instant Capacity Resource Summary
---------------------------------
Number of cells without usage rights: 0
Number of inactive cells: 0
Amount of memory without usage rights: 0.0 GB
Amount of inactive memory: 0.0 GB
Number of cores without usage rights: 0
Number of inactive cores: 2
Number of cores that must be deactivated (insufficient usage rights): 0
Temporary capacity available: 0 days, 0 hours, 0 minutes

Allocation of Instant Capacity Resources among the nPartitions
--------------------------------------------------------------
Intended Actual
nPar Total Active Active =======Inactive======= Runs
ID Cores Cores Cores Cores Memory Cells iCAP nPar Name
==== ===== ======== ====== ====================== ==== ======================
0 16 16 14 2 0.0 GB 0 Yes Partition 0... (local)
1 16 16 16 0 0.0 GB 0 Yes Partition 1 - UX
N/A 0 N/A N/A N/A 0.0 GB 0 N/A Unassigned Cells


Both icapd and cimserver are running and I don't find any strange message when running icapstatus.
wang & wang

Re: Instant capacity error message: The following low-level WBEM error occurred: Empty HTTP response mes

then I think you can ignore the error...

Duncan

HTH

Duncan

Re: Instant capacity error message: The following low-level WBEM error occurred: Empty HTTP response mes

oh... one strange thing:

Local nPartition Status
-----------------------
Total number of configured cores: 16
Number of Intended Active cores: 16 <<==
Number of active cores: 14
Number of inactive cores: 2

For some reason the system wants those 2 iCAP cores you have to be activated although you don't have the rights to activate them... not sure why - you should probably look through /var/adm/icap.log and see if you can figure out why...

anyway to bring the system back into compliance you should really run:

icapmodify -s 14 "Bring back into compliance:"

And obviously run this command on nPar 0


After that you should see:

Local nPartition Status
-----------------------
Total number of configured cores: 16
Number of Intended Active cores: 14 <===
Number of active cores: 14
Number of inactive cores: 2

(I also won't comment on why you seem to have your system hostname set to "hostname"!)

HTH

Duncan

HTH

Duncan