Stuck in 403 state for logins

[bluecmd]

For some reason the exporter is now not able to talk to my V7000 G2 enclosure.

Likely this will be solved by a restart, and maybe this was caused by some brute force protection?

Nov 12 00:10:18 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:10:18 Error: Response code was 500, expected 200
Nov 12 00:10:18 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:10:18 Probe of "https://tera.xxx:7443" failed, took 0.496 seconds
Nov 12 00:10:23 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:10:23 Error: Response code was 500, expected 200
Nov 12 00:10:23 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:10:23 Probe of "https://tera.xxx:7443" failed, took 0.465 seconds
Nov 12 00:10:28 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:10:28 Error: Response code was 500, expected 200
Nov 12 00:10:28 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:10:28 Probe of "https://tera.xxx:7443" failed, took 0.464 seconds
Nov 12 00:10:33 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:10:33 Error: Response code was 500, expected 200
Nov 12 00:10:33 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:10:33 Probe of "https://tera.xxx:7443" failed, took 0.465 seconds
Nov 12 00:10:38 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:10:38 Error: Response code was 500, expected 200
Nov 12 00:10:38 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:10:38 Probe of "https://tera.xxx:7443" failed, took 0.467 seconds
Nov 12 00:10:43 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:10:43 Probe request rejected; error is: Login code was 403, expected 200
Nov 12 00:10:48 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:10:48 Probe request rejected; error is: Login code was 403, expected 200
Nov 12 00:10:53 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:10:53 Probe request rejected; error is: Login code was 403, expected 200
Nov 12 00:10:58 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:10:58 Probe request rejected; error is: Login code was 403, expected 200
Nov 12 00:11:03 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:11:03 Probe request rejected; error is: Login code was 403, expected 200
Nov 12 00:11:08 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:11:08 Probe request rejected; error is: Login code was 403, expected 200
Nov 12 00:11:13 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:11:13 Probe request rejected; error is: Login code was 403, expected 200
Nov 12 00:11:18 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:11:18 Probe request rejected; error is: Login code was 403, expected 200
Nov 12 00:11:23 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:11:23 Probe request rejected; error is: Login code was 403, expected 200
Nov 12 00:11:28 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:11:28 Probe request rejected; error is: Login code was 403, expected 200
Nov 12 00:11:33 debian spectrum_virtualize_exporter[126738]: 2020/11/12 00:11:33 Probe request rejected; error is: Login code was 403, expected 200

[matejzero]

Are you able to connect via cURL?
The 500 response codes are weird. can you add more debug to see which request returns 500?

Have a look at chsessionpolicy and lssessionpolicy commands.

I just found out your exporter while looking for something to monitor my Storwize and SVC storages. Will have a look at it tomorrow.

[bluecmd]

Hi! Thanks @matejzero, I was not aware of those commands.

I was not able to connect to the API using curl, I added new users and even superuser was denied access.
A restart of both controllers solved the issue for me.

If it happens next time I will check the commands and add the output here.

[olemyk]

FYI. those command chsessionspolicy is for Unified system, not the SpecV software.
Unified is/was a fileheader that runs GPFS with protocols, SMB,NFS, Object. that system is not sold anymore.