philrosenberg
commented
3 years ago Comparing the two flux loggers, the one that stopped logging had its data tidied into a folder with name format YYYY-MM and the one that kept running did not have its data tidied in this way.
Spoke to Barbara - the flux towers have a script called tidydata which is run by the logging software at midnight. This is in the /home/bin dirctory. This tidies the data into the directory structure mentioned above.
It seems that when it does this the last file of the day disappears and cannot be opened for appending by the logging software - this is indicated in the log file at /var/usbstorage/logger.log
Instead of recovering, the software just seems to die.
On Flux Tower 1, somebody forgot to add the execute permissions to the scripts in the /var/bin directory. Hence the tidydata script was not running and the instrument was logging fine across midnight.
Fixed the problem by moving /home/bin/tidydata to tidydata,orig and replacing it with an empty file that just has a comment in saying that there was a problem.
I have made the scripts on logger 1 executable and done the same thing on there.
Left the flux instruments running over the weekend. When I came back one stopped logging with the last file written being withignthe last hour before midnight. The logging software starts a new data file every hour, so I'm assuming midnight is relevant.