[38368423]

I have sent the faulty event file to your email address info@rapidscada.org with the subject “Event marker not found.” This issue not only causes the event file to become corrupted but also affects the files in the min, hour, and cur directories.

[38368423]

This scenario is easy to reproduce. The reproduction conditions are as follows:

1、You have a large amount of data that needs to be read and recorded.

2、You configure alarms for these data channels.

3、Frequent power outages and restarts occur.

[38368423]

This issue is quite serious as it has caused the data files and event files to become unreadable. Is there a timeline for the fix?

[38368423]

It is installed on an Ubuntu system. Personally, I find event loss acceptable, but I cannot accept file corruption. The problem now is that after corruption occurs, no more events are generated, and there is no automatic recovery mechanism.

[38368423]

My device operates in an environment prone to power outages. What solutions are available?

[38368423]

yes，file is corrupted，Why do files often get corrupted, and how can this be avoided?

[38368423]

length of string is great than 24

[38368423]

Do you have any suggestions for extending MQTT driver support for strings

[38368423]

How can I implement it? Can you give me a demonstration

[38368423]

yes, I have.

[38368423]

hi,

Error cs1503:Parameter 2: cannot convert from “SCADA. Agent. Serviceapp” to “SCADA. Agent. Connector. Agentsvcref. Serviceapp”

Error cs1503: parameter 2: cannot convert from “SCADA. Agent. Relpath” to “SCADA. Agent. Connector. Agentsvcref. Relpath”

and so on

[Author]

Posts