3 years 7 months ago - 3 years 7 months ago#399by Xavier
The problem remains with v0.7b0
As previously in v06b01, it always appears on the same node, the Node 02 (of 2), when the dBase is populated with several hours of recording.
Once it appears, I can:
- stop the server and restart,
- allow some new records,
- open the browser on the chart page
-> if I add to the chart view a sensor belonging to node 2 the error popup.
It looks like a corrupted DBase but no error appears in the logs.
If I clear the database, it solves the issue... but I loose my data and it's not the purpose
Couldn't find my way to add an attachement (does it work?). Anyway, here is a screenshot.
[img size=400]http://x.muller.free.fr/ScreenSHOT/easyiot v07b01 - bug on chart.png
Last Edit: 3 years 7 months ago by Xavier. Reason: Screenshot added
3 years 7 months ago - 3 years 7 months ago#400by Xavier
I'm currently investigating the sqlite database, using the SQLite Manager addon for FireFox.
The presumably faulty dBase weights 300kB.
- An integrity full check reports OK
- All tables seem conform to what I setup:
Addresses: holds 4 records N1S0,N1S1,N2S2,N2S3 (as N1S2,N1S3,N2S0 & N2S1 are not populated I don't record the NaNs)
domains: holds only MySensors as others are inactivated
properties: currently only holds Sensor.Humidity & Sensor.Temperature
raw_values: holds 7380 samples
sqlite_sequence: reports the correct size of the 4 previous tables
What can I check now?
- Do the records need to have sequencial timestamps? (it might crash if a race condition occurs) what SQL command should I use to test that?
Nota: The error message is the same when the server is down (which is not the case).
Last Edit: 3 years 7 months ago by Xavier. Reason: Cosmetics+Nota