no VOLUME has been found
Hello,
Error started after yum update.
v2.10
./load.sh
Tue Dec 12 10:26:06 2017: EMC-VNX-5400-1: Problem with configuration load, no VOLUME has been found, is there really exist one? : /home/lpar2rrd/stor2rrd/data/EMC-VNX-5400-1/config.html bin/LoadDataModule.pm:19975
In web console:
Tue Dec 12 10:30:02 2017
Cannot use the security file. Check the -secfilepath option.
Cannot use the security file. Check the -secfilepath option.
Cannot use the security file. Check the -secfilepath option.
An error occurred while decrypting the security file. The security file might be corrupted.Run -removeusersecurity to destroy the existing security file, then run -addusersecurity to create a new security file. Alternately, you may use the -secfilepath option.
Error started after yum update.
v2.10
./load.sh
Tue Dec 12 10:26:06 2017: EMC-VNX-5400-1: Problem with configuration load, no VOLUME has been found, is there really exist one? : /home/lpar2rrd/stor2rrd/data/EMC-VNX-5400-1/config.html bin/LoadDataModule.pm:19975
In web console:
Tue Dec 12 10:30:02 2017
Cannot use the security file. Check the -secfilepath option.
Cannot use the security file. Check the -secfilepath option.
Cannot use the security file. Check the -secfilepath option.
An error occurred while decrypting the security file. The security file might be corrupted.Run -removeusersecurity to destroy the existing security file, then run -addusersecurity to create a new security file. Alternately, you may use the -secfilepath option.
Comments
-
hi,
I suppose this is failing right?
use lpar2rrd user on the Virtual Appliance
# su - stor2rrd
$ /opt/Navisphere/bin/naviseccli -h <storage controller IP/hostname> getcontrol -all
System Fault LED: OFF
Statistics Logging: ON
if so the recreate it as per error advice
$ /opt/Navisphere/bin/naviseccli -removeusersecurity
$ /opt/Navisphere/bin/naviseccli -addusersecurity -scope 1 -password XXXXXXXXXXX -user stor2rrd
-
Thank you Pavel,
I understand that this is not a stor2rrd problem, but I do not know how to solve it.
[lpar2rrd@srv stor2rrd]$ /opt/Navisphere/bin/naviseccli -h 192.168.0.4 getcontrol -all
Cannot use the security file. Check the -secfilepath option.
Cannot use the security file. Check the -secfilepath option.
Cannot use the security file. Check the -secfilepath option.
An error occurred while decrypting the security file. The security file might be corrupted.Run -removeusersecurity to destroy the existing security file, then run -addusersecurity to create a new security file. Alternately, you may use the -secfilepath option.
[lpar2rrd@srv stor2rrd]$ /opt/Navisphere/bin/naviseccli -removeusersecurity
Cannot use the security file. Check the -secfilepath option.
Cannot use the security file. Check the -secfilepath option.
[lpar2rrd@srv stor2rrd]$ /opt/Navisphere/bin/naviseccli -removeusersecurity
Cannot use the security file. Check the -secfilepath option.
Cannot use the security file. Check the -secfilepath option.
Security file not found. Already removed or check -secfilepath option.
[lpar2rrd@srv stor2rrd]$ /opt/Navisphere/bin/naviseccli -addusersecurity -scope 1 -password ХХХХХХХХ -user stor2rrd
Cannot use the security file. Check the -secfilepath option.
Cannot use the security file. Check the -secfilepath option.
-
file rights issue?
ls -l /home/stor2rrd/Secured*
-rw-rw-r-- 1 stor2rrd stor2rrd 304 Aug 15 2016 /home/stor2rrd/SecuredCLISecurityFile.xml
-rw-rw-r-- 1 stor2rrd stor2rrd 48 Aug 15 2016 /home/stor2rrd/SecuredCLIXMLEncrypted.key
-
I copied SecuredCLISecurityFile.xml and SecuredCLIXMLEncrypted.key from /home/lpar2rrd/ to /home/stor2rrd/stor2rrd/
[lpar2rrd@srv stor2rrd]$ ls -l /home/stor2rrd/stor2rrd/Secured*
-rw-rw-r-- 1 lpar2rrd lpar2rrd 304 Dec 12 11:41 /home/stor2rrd/stor2rrd/SecuredCLISecurityFile.xml
-rw-rw-r-- 1 lpar2rrd lpar2rrd 48 Dec 12 11:41 /home/stor2rrd/stor2rrd/SecuredCLIXMLEncrypted.key
But error is the same.
-
it does not help.
I would move them somewhere out and would try to reinitiate it
replace XXX by your password
$ /opt/Navisphere/bin/naviseccli -addusersecurity -scope 1 -password XXXXXXXXXXX -user stor2rrd
-
[lpar2rrd@srv stor2rrd]$ uemcli -d 192.168.0.4 -u Local/sysadmin -p "ХХХХХХХХ" /user/account show./bin/config_check.sh
Storage system address: 192.168.0.4
Storage system port: 443
HTTPS connection
Remote certificate:
Issuer: CN=192.168.0.4,CN=SPA,OU=CLARiiON
Subject: CN=192.168.0.4,CN=SPA,OU=CLARiiON
Valid from: 2013-11-13 12:57:25 Z
Valid to: 2018-11-12 12:57:25 Z
Serial: de00003d
Id: 3600000153
Would you like to:
[1] Accept the certificate for this session
[2] Reject the certificate
[3] Accept and store
Please input your selection (The default selection is [1]): 3
Operation failed. Error code: 0x100000a
The system was unable to connect to the storage server. (Error Code:0x100000a)
-
Of course I changed the password.
-
you use medium security, then issue some cmd and select [3] like in this example:
/usr/bin/uemcli -d 192.168.1.179 -u stor2rrd -p Test2test_ -noHeader /sys/general show -detail
Remote certificate:
Issuer: CN=EMC-Unity
Subject: CN=EMC-Unity
Valid from: 2016-07-15 09:54:57 Z
Valid to: 2019-07-15 09:54:57 Z
Serial: 0094aea927526b466e
Id: 2595584890
Would you like to:
[1] Accept the certificate for this session
[2] Reject the certificate
[3] Accept and store
--> select 3
-
New appliance install:
[root@srv ~]# umask 022
[root@srv ~]# rpm -i UnisphereCLI-Linux-64-x86-en_US-4.2.1.1.2069-1.x86_64.rpm
Run the script /opt/emc/uemcli/bin/setlevel.sh (low|medium|l|m) to set the security level before you proceed.
==============================================================
USAGE:setlevel.sh (low|medium|l|m)
The setlevel.sh script is used to set the certificate verification level
to low or medium.
choices are low or medium.
DEFAULT = medium
For more information about the certificate verification process please refer
to the User's Manual.
execute command /opt/emc/uemcli/bin/setlevel.sh (low|medium|l|m)
The tool will guide you through the steps to set the security level.
==============================================================
[root@srv ~]# /opt/emc/uemcli/bin/setlevel.sh medium
Setting medium verifying level.....
Verification level has been set SUCESSFULLY!!!
[root@srv ~]# su - lpar2rrd
Last login: Wed Dec 13 10:19:57 CET 2017
[lpar2rrd@srv ~]$ uemcli -d 10.0.0.23 -u Local/sysadmin -p "ХХХХХХХХ" /user/account shows
Storage system address: 10.0.0.23
Storage system port: 443
HTTPS connection
Remote certificate:
Issuer: CN=10.0.0.23,CN=SPA,OU=CLARiiON
Subject: CN=10.0.0.23,CN=SPA,OU=CLARiiON
Valid from: 2017-10-11 11:10:01 Z
Valid to: 2022-10-10 11:10:01 Z
Serial: 6a000046
Id: 1500000927
Would you like to:
[1] Accept the certificate for this session
[2] Reject the certificate
[3] Accept and store
Please input your selection (The default selection is [1]): 3
Operation failed. Error code: 0x100000a
The system was unable to connect to the storage server. (Error Code:0x100000a)
[lpar2rrd@srv ~]$
-
is low level working at least?
/opt/emc/uemcli/bin/setlevel.sh low
uemcli -d 10.0.0.23 -u Local/sysadmin -p "ХХХХХХХХ" /user/account shows
-
[root@srv ~]# /opt/emc/uemcli/bin/setlevel.sh low
Setting low verifying level.....
Verification level has been set SUCESSFULLY!!!
[root@srv ~]# su - lpar2rrd
Last login: Wed Dec 13 11:55:14 CET 2017 on pts/0
[lpar2rrd@srv ~]$ uemcli -d 192.168.0.122 -u Local/sysadmin -p "ХХХХХХХ" /user/account shows
Storage system address: 192.168.0.122
Storage system port: 443
HTTPS connection
Operation failed. Error code: 0x100000a
The system was unable to connect to the storage server. (Error Code:0x100000a)
[lpar2rrd@srv ~]$
-
Should not be user rather "admin" than "sysadmin"?
is connection ok?perl /home/stor2rrd/stor2rrd/bin/conntest.pl 192.168.0.122 443
-
Of course sysadmin, I check connection over web console, login and password is correct.
[lpar2rrd@srv ~]$ uemcli -d 192.168.0.122 -u Local/sysadmin -p "ххххх" /user/account shows
Storage system address: 192.168.0.122
Storage system port: 443
HTTPS connection
Operation failed. Error code: 0x100000a
The system was unable to connect to the storage server. (Error Code:0x100000a)
[lpar2rrd@srv ~]$ perl /home/stor2rrd/stor2rrd/bin/conntest.pl 192.168.0.122 443
Connection to "192.168.0.122" on port "443" is ok
-
hmm, looks like you need to get support from EMC, we cannot do more when EMC API cannot connect EMC storage.
Just assure you use right uemcli version (use the latest one) and it is all we can advice.
Pls log a call with EMC.
-
Some strange thing happens. In the first posts I can see, that you use EMC-VNX-5400 and naviseccli.
But in the middle of the discussion you have switched somehow to uemcli, which is used for EMC VNXe, AFAIK.
Howdy, Stranger!
Categories
- 1.6K All Categories
- 41 XORMON NG
- 25 XORMON
- 149 LPAR2RRD
- 13 VMware
- 16 IBM i
- 2 oVirt / RHV
- 4 MS Windows and Hyper-V
- Solaris / OracleVM
- XenServer / Citrix
- Nutanix
- 6 Database
- 2 Cloud
- 10 Kubernetes / OpenShift / Docker
- 122 STOR2RRD
- 19 SAN
- 7 LAN
- 17 IBM
- 3 EMC
- 12 Hitachi
- 5 NetApp
- 15 HPE
- Lenovo
- 1 Huawei
- 1 Dell
- Fujitsu
- 2 DataCore
- INFINIDAT
- 3 Pure Storage
- Oracle