[ofiwg] how to react to error log messages

Hefty, Sean sean.hefty at intel.com
Tue Mar 24 17:08:55 PDT 2015

I don't think there's any expectation that an app should do anything with the log messages, beyond use them to either debug their app or report an issue.

This sounds like a problem with the sockets provider.  Either it needs to output more information, so that the developer can figure out what is going wrong, or it should suppress the error unless logging is turned on.

In your case, are you seeing a list of fi_info responses? 

> -----Original Message-----
> From: ofiwg-bounces at lists.openfabrics.org [mailto:ofiwg-
> bounces at lists.openfabrics.org] On Behalf Of Sung-Eun Choi
> Sent: Tuesday, March 24, 2015 5:02 PM
> To: ofiwg at lists.openfabrics.org
> Subject: [ofiwg] how to react to error log messages
> Here's a situation I ran into.  All my program does is call
> fi_getinfo() with some hints.  I get 3 of these log messages:
> 	libfabric:sockets: Failed to connect udp socket
> fi_getinfo() returns without error.
> My question is, what am I supposed to do with these log messages?
> Should I be reacting to them?  If so, I don't really see how.  Or
> perhaps it would become more obvious once I tried to do something
> real and I would get other failures.
> -- Sung
> _______________________________________________
> ofiwg mailing list
> ofiwg at lists.openfabrics.org
> http://lists.openfabrics.org/mailman/listinfo/ofiwg

More information about the ofiwg mailing list