MSA 2050 \ timed out after: 300 seconds. Interrupted system call
Hello!
config check
config check
=========================
STORAGE: BER-RC-MSA2050: DOTHILL
=========================
TCP connection to "10.244.208.137" on port "5989" is ok
TCP connection to "10.244.208.137" on port "443" is ok
TCP connection to "10.244.208.138" on port "5989" is ok
TCP connection to "10.244.208.138" on port "443" is ok
/usr/bin/wbemcli -noverify -nl ei https://stor2rrd:XXXXX@10.244.208.137:5989/root/dhs:cim_computersystem
/usr/bin/wbemcli -noverify -nl ei https://stor2rrd:XXXXX@10.244.208.138:5989/root/dhs:cim_computersystem
/usr/bin/wbemcli -noverify -nl ei https://stor2rrd:XXXXX@10.244.208.137:5989/root/hpq:cim_computersystem
SMI-S API is ok, going to test Web-browser interface (WBE) through https
/usr/bin/perl /home/stor2rrd/stor2rrd/bin/dothill_apitest.pl stor2rrd XXXXX 10.244.208.137 https
WBE via https is ok
connection ok
tail /home/stor2rrd/stor2rrd/logs/error.log-BER-RC-MSA2050
Fri Dec 3 07:34:26 2021: Fri Dec 3 07:34:26 2021 command: /usr/bin/wbemcli -nl -t -noverify ei 'https://stor2rrd:XXXXX@10.244.208.138:5989/root/hpq:CIM_BlockStorageStatisticalData' timed out after: 300 seconds /home/stor2rrd/stor2rrd/bin/dothillperf.pl:2608 : Interrupted system call
Fri Dec 3 07:39:26 2021: Fri Dec 3 07:39:26 2021 command: /usr/bin/wbemcli -nl -t -noverify ei 'https://stor2rrd:XXXXX@10.244.208.138:5989/root/hpq:CIM_BlockStorageStatisticalData' timed out after: 300 seconds /home/stor2rrd/stor2rrd/bin/dothillperf.pl:2608 : Interrupted system call
Comments
-
I have configured 7 such storage systems in the same way, but there are problems here
-
Hi,run this, how long it takes? It will be printed at the end, supply password when you are askedtime /usr/bin/wbemcli -nl -t -noverify ei 'https://stor2rrd@10.244.208.138:5989/root/hpq:CIM_BlockStorageStatisticalData'
-
it's funny, but[stor2rrd@ekb-stor2rrd root]$ time /usr/bin/wbemcli -nl -t -noverify ei 'https://stor2rrd@10.244.208.138:5989/root/hpq:CIM_BlockStorageStatisticalData'Enter password:** /usr/bin/wbemcli: Http Exception: Server returned nothing (no headers, no data)*real 12m32.974suser 0m0.067ssys 0m0.097s
-
after 12 minutes it returned nothing?what is your storage firmware? older one?What about other 6 storage devices, same issue? same firmware?
-
target storage have FW VL100P001\VLS100R03-02 (older than the others)
others storages have different version - VL270P003, VL270P002, VL270P004
maybe there is a known problem with this firmware?
-
I suppose the other storage devices work, right?It looks like firmware issue, we have already seen that for older firmwares, upgrade or log a call with HPE ...
-
yes, other devices work fine.
I'll try to schedule an upgrade.
Thanks! -
I updated FW and nothing has changed (I re-added MSA to stor2rrd with completely clear all data of this storage)
Howdy, Stranger!
Categories
- 1.6K All Categories
- 48 XORMON NG
- 25 XORMON
- 153 LPAR2RRD
- 13 VMware
- 16 IBM i
- 2 oVirt / RHV
- 4 MS Windows and Hyper-V
- Solaris / OracleVM
- XenServer / Citrix
- Nutanix
- 7 Database
- 2 Cloud
- 10 Kubernetes / OpenShift / Docker
- 124 STOR2RRD
- 19 SAN
- 7 LAN
- 17 IBM
- 3 EMC
- 12 Hitachi
- 5 NetApp
- 15 HPE
- Lenovo
- 1 Huawei
- 2 Dell
- Fujitsu
- 2 DataCore
- INFINIDAT
- 3 Pure Storage
- Oracle