Open HPI is an open source implementation of the SA Forum's Hardware Platform Interface (HPI). HPI provides an abstracted interface to managing computer hardware, typically for chassis and rack based servers
0
stars
1
forks
source link
Sometimes, oa_soap plugin tries to connect to 0.0.0.0 #2524
Looks like in some rare conditions we are setting the IP address of the OA as 0.0.0.0 without checking. This leads to following error
Nov 14 17:45:05 dl380g8 openhpid: ssl: oh_ssl.c:527: Socket connect failed with error: Connection refused
Nov 14 17:45:05 dl380g8 openhpid: oa_soap: oa_soap_callsupport.c:647: oh_ssl_connect() failed
Nov 14 17:45:05 dl380g8 openhpid: oa_soap: oa_soap_callsupport.c:836: failed to communicate with OA during login
Nov 14 17:45:05 dl380g8 openhpid: oa_soap: oa_soap_callsupport.c:537: OA login failed for server 0.0.0.0:443
Nov 14 17:45:10 dl380g8 openhpid: oa_soap: oa_soap_event.c:317: soap_open for oa->event_con2 failed#012
This message repeats every 5 seconds. There are two things that could be done.
When setting the variable make a check if it is 0.0.0.0 and do not set it if it is so. Try to recover there.
Where this error occurs, if the server is 0.0.0.0 handle it.
This one is not easy to reproduce. Had two enclosures in the conf file. Did an OA switchover on both the enclosures which lead to this error.
Looks like in some rare conditions we are setting the IP address of the OA as 0.0.0.0 without checking. This leads to following error Nov 14 17:45:05 dl380g8 openhpid: ssl: oh_ssl.c:527: Socket connect failed with error: Connection refused Nov 14 17:45:05 dl380g8 openhpid: oa_soap: oa_soap_callsupport.c:647: oh_ssl_connect() failed Nov 14 17:45:05 dl380g8 openhpid: oa_soap: oa_soap_callsupport.c:836: failed to communicate with OA during login Nov 14 17:45:05 dl380g8 openhpid: oa_soap: oa_soap_callsupport.c:537: OA login failed for server 0.0.0.0:443 Nov 14 17:45:10 dl380g8 openhpid: oa_soap: oa_soap_event.c:317: soap_open for oa->event_con2 failed#012
This message repeats every 5 seconds. There are two things that could be done.
This one is not easy to reproduce. Had two enclosures in the conf file. Did an OA switchover on both the enclosures which lead to this error.
Reported by: dr_mohan