Hi all,
I have a strange problem with a big ProviewR system (around 4500 data points). The log file fills up the hard disk within 46 days.
A look at the log file shows up to 40 entries in a millisecond. An “activeListRemove error” always follows an “activeListInsert error.” The event number ‘7’ indicates that this is the “mh_eEvent_Return” event type. Since the error messages are generated by the rt_emon process, this must be a problem with alarm management (configuration error?). The `activeEventInsert` function is defined in the file `rt_emon.c` and is used only there — though by different functions. In the function definition, you can see that the function does not expect an `mh_eEvent_Return`. For every unexpected event type, the function outputs a corresponding error message.
So far, I haven't been able to figure out why the unwanted mh_eEvent_Return events are showing up here in the first place, nor where the large number of simultaneous inserts/removes might be coming from.
Has anyone ever seen something similar, or do you have any suggestions on how I could go about tackling this problem?
/Martin
