short question, opening dm page results in “unable to open errors”
50 05/15/13 19:37:37.660 luup_log:17: dataMine: Trying 2:/tmp/log/cmh/noLog/dataMine/4 Temperature Area - CurrentTemperature [R2263].txt <0x2e3ec680>
50 05/15/13 19:37:37.661 luup_log:17: dataMine: 2:Unable to open file for read - /tmp/log/cmh/noLog/dataMine/4 Temperature Area - CurrentTemperature [R2263].txt <0x2e3ec680>
50 05/15/13 19:37:40.668 luup_log:17: dataMine: Trying 2:/tmp/log/cmh/noLog/dataMine/8 Temperature - Kitchen - CurrentTemperature [R2263].txt <0x2e3ec680>
50 05/15/13 19:37:40.669 luup_log:17: dataMine: 2:Unable to open file for read - /tmp/log/cmh/noLog/dataMine/8 Temperature - Kitchen - CurrentTemperature [R2263].txt <0x2e3ec680>
50 05/15/13 19:37:40.686 luup_log:17: dataMine: Trying 2:/tmp/log/cmh/noLog/dataMine/4 Temperature Area - CurrentTemperature [R2263].txt <0x2e3ec680>
50 05/15/13 19:37:40.687 luup_log:17: dataMine: 2:Unable to open file for read - /tmp/log/cmh/noLog/dataMine/4 Temperature Area - CurrentTemperature [R2263].txt <0x2e3ec680>
the folder holds the files but the number on the end is different.
example
dm searches for /tmp/log/cmh/noLog/dataMine/8 Temperature - Kitchen - CurrentTemperature [R2263].txt
the files on the usb are:
root@MiOS:/tmp/log/cmh/noLog/dataMine# ls -al 8*
-rw-r--r-- 1 root root 13 Jan 1 2000 8 Temperature - Kitchen - CurrentTemperature [R1565].txt
-rw-r--r-- 1 root root 378 May 15 19:00 8 Temperature - Kitchen - CurrentTemperature [R2262].txt
anything to worry ?
P.S. i have not yet upgraded your newest version (its the standard production version of dm)
PP.S. everything seems working allright
Sorry for the slow response - I’ve been away for work >:(
Can you click on the “debug” link in the plugin and I’ll take a look. I’m worried your USB has switched into “read-only” mode!
The numbers on the end of files are associated with weeks - so a new file is created every week. The error states that DM can’t open the file now, so probably new data isn’t being written. Linux has a “useful” feature where if there are errors in the USB, it can put the drive into read-only mode, and it can be difficult to get it out of this mode.
Unfortunately, I think that Vera restarts, and maybe even Luup restarts, can cause this as it would cause the USB to be reset without closing properly (like taking a USB stick out of your PC without properly releasing it - it works most of the time, but you might find data gets lost very occasionally!).
This can be seen in the debug log as it’s printed in the mount command output, and the easiest way to see this is to click the debug link. If you want to post it here I’ll take a look…
Thanks. The problem seems to have stopped now, so it’s difficult to see. However, I’m not sure if the problem like I mentioned can occur on ext file systems, so this may not be the problem (I’m not sure). Or, it may be that it can occur on ext, but the journalling may mean that it recovers itself, where a FAT system may not…
Based on the message you sent though, some data will have been lost. It probably doesn’t matter too much, but I’d keep an eye on it. If this occurs when you have the GUI open, it will show a red icon in the status bar in the top left.
i can trigger it at any time …
simply select the temperature data channels … click Draw and zoom out 2 or 3 times
oh maybe its a “old” refordset which does not exist because i did re-add the temperture sensor.
but that wont explain the error on the area temperature (data comes from the weather plugin)
the error always comes (does not matter what data drawn) if the file is before “R2264”
maybe that is the week where i moved datamine to shared USB storage with vera logs …
i did a backup to /tmp before the vera did format the USB,
which was kind of stupid, because the vera did reboot after the format so everything in /tmp (including my “backup”) went to nirvana.
in short, i dont have any “old” data but dm seems to have the information somehow that the date does exists …
