|
Post by abula on Jun 27, 2022 4:15:41 GMT
Hi, I'm fixing the subscription for events. Now, there's a new issue that I got login returned code 503 when using Listener as the below. I saw it Login returned code 201 before. How could I fix it? Thanks.
Redfish Event Listener v1.1.2
ServerIP:: https://10.110.85.1:8888
UserName:: admin
Attempt 1 of /redfish/v1/
Response Time for GET to /redfish/v1/: 0.028899751021526754 seconds.
Attempt 1 of /redfish/v1/SessionService/Sessions
Response Time for POST to /redfish/v1/SessionService/Sessions: 0.0019632489420473576 seconds.
Login returned code 503:
Unable to subscribe for events with https://10.110.85.1:8888
Traceback (most recent call last):
File "RedfishEventListener_v1.py", line 260, in <module>
my_ctx.login(auth=logintype.lower())
File "/home/alpha/.local/lib/python3.8/site-packages/redfish/rest/v1.py", line 952, in login
raise InvalidCredentialsError(delay)
redfish.rest.v1.InvalidCredentialsError: 0
|
|
|
Post by mraineri on Jun 27, 2022 12:47:54 GMT
Unfortunately that looks like a service-side issue. Since a 503 is being returned by the service, it looks like the service might be under load or performing other types of maintenance rather than bad credentials. The only choice at this point is to try again, and if it keeps persisting, you likely need to reboot the service. Ultimately these sort of stability issues need to be worked by the vendor and beyond retries/resets, there's not much else that can be done.
|
|
|
Post by abula on Jun 28, 2022 1:13:28 GMT
Got it! Thanks.
|
|
|
Post by abula on Jul 21, 2022 6:01:19 GMT
Hi, I think I can access the path of the service root for event subscription now, but I still can't subscribe successfully, what is the problem? I set the destination in SubscriptionDetails as 10.69.3.156:89Thanks. Redfish Event Listener v1.1.2
ServerIP:: https://10.110.85.2:8888
UserName:: admin
Attempt 1 of /redfish/v1/
Response Time for GET to /redfish/v1/: 0.027043939102441072 seconds.
Attempt 1 of /redfish/v1/SessionService/Sessions
Response Time for POST to /redfish/v1/SessionService/Sessions: 0.021905926056206226 seconds.
Login returned code 201: {"@odata.context":"/redfish/v1/$metadata#Session.Session","@odata.id":"/redfish/v1/SessionService/Sessions/04254222bf7e2d25","@odata.type":"#Session.v1_0_0.Session","Name":"User Session","Description":"User Session","UserName":"admin","Id":"04254222bf7e2d25"}
Attempt 1 of /redfish/v1/
Response Time for GET to /redfish/v1/: 0.001982518006116152 seconds.
Attempt 1 of /redfish/v1/EventService
Response Time for GET to /redfish/v1/EventService: 0.0021494608372449875 seconds.
Attempt 1 of /redfish/v1/EventService/Subscriptions
Response Time for POST to /redfish/v1/EventService/Subscriptions: 0.002413859125226736 seconds.
Unable to subscribe for events with https://10.110.85.2:8888
Traceback (most recent call last):
File "RedfishEventListener_v1.py", line 263, in <module>
response = redfish_utilities.create_event_subscription(my_ctx, config['destination'],
File "/home/alpha/.local/lib/python3.8/site-packages/redfish_utilities/event_service.py", line 212, in create_event_subscription
verify_response( response )
File "/home/alpha/.local/lib/python3.8/site-packages/redfish_utilities/messages.py", line 71, in verify_response
raise RedfishOperationFailedError( "Operation failed: HTTP {}\n{}".format( response.status, exception_string ) )
redfish_utilities.messages.RedfishOperationFailedError: Operation failed: HTTP 400
The property EventFormatType is not in the list of valid properties for the resource.
Unexpected field in json.
|
|
|
Post by mraineri on Jul 21, 2022 13:20:27 GMT
It looks like it doesn't support specifying the format type as part of the subscription. If you delete the "Format" line in your configuration file, the listener will not populate that info in the subscription request.
It might be good start with a very simply SubscriptionDetails section in your configuration file since that controls what properties go into the subscription. "Destination" is the only required property, and if that is successful, you can add other properties in SubscriptionDetails to specify additional information about the types of events you want to receive.
|
|
|
Post by abula on Jul 22, 2022 6:59:46 GMT
#The property Context is a required property and must be included in the request. So I set the configure file as below and got the same error message. what else can I try? Thanks.
[Information]
Updated = April 24, 2017
Description = Redfish Event Listener Tool
[SystemInformation]
ListenerIP = 0.0.0.0
ListenerPort = 89
UseSSL = off
[CertificateDetails]
certfile = cert.pem
keyfile = server.key
[SubscriptionDetails]
Destination =http://10.69.3.156:89 Context= "Public"
[ServerInformation]
ServerIPs = ["https://10.110.85.2:8888"]
UserNames = ["admin"]
|
|
|
Post by mraineri on Jul 22, 2022 13:22:35 GMT
Can you try removing the double quotes around Public? On non-array config values, having double quotes will insert them into the string itself.
I don't think it should necessarily matter though since it's still a valid string for the property. If that doesn't solve the issue, I can start adding trace options to the tool to help look at this further.
|
|
|
Post by abula on Jul 25, 2022 3:05:54 GMT
Yes, I can successfully subscribe after removing the double quotes around Public. Thanks for your help.
|
|