The "internal error" indicates some logical error that the library
doesn't know how to handle.  Given its coming from
ipmi_monitoring_sensor_readings_by_record_id and it occurs when you run
the program back to back, I would bet there is some internal IPMI issue
on your system.  Perhaps its a new error code or something like that
that I do not handle gracefully correctly.

To try and debug, could you set the flag "IPMI_MONITORING_FLAGS_DEBUG |
IPMI_MONITORING_FLAGS_DEBUG_IPMI_PACKETS" when calling
ipmimonitoring_init() in the example code.  Hopefully that'll be enough
to figure out the issue.

Al

On Mon, 2017-07-17 at 13:03 -0700, Sohan Chowdary Kollu wrote:
> Hi,
> 
> I am executing the ipmimonitoring-sensors.c example provided in the
> freeipmi library. It throws internal error sometimes. Issue is
> reproducible when i execute the program back to back couple of times.
> I need to wait approximately 30 sec or more after the last execution
> for the program to run properly. 
> 
> 
> This is the error ipmi_monitoring_sensor_readings_by_record_id:
> internal error
> 
> 
> 
> I ran some of the commands on terminal back to back , including
> ipmi-sensors with group option, ipmimonitoring etc. None of them thew
> any errors. Error occurs only when i am use the API.
> 
> 
> Has anyone faced this issue before? If yes, can you tell me how to
> avoid it
> 
> 
> 
>  
> Thanks,
> Sohan
> _______________________________________________
> Freeipmi-devel mailing list
> Freeipmi-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/freeipmi-devel

-- 
Albert Chu
ch...@llnl.gov
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory



_______________________________________________
Freeipmi-devel mailing list
Freeipmi-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/freeipmi-devel

Reply via email to