![]() By my estimation there would have been less than 100 entries in the log as of yesterday. ![]() The previous log file I managed to save contained 199 entries. I ran a program manually, just to see if anything was actually being logged, and sure enough, there was a log entry, but only this one, most recent entry. I then tried to retrieve the logs through the API but this time there was nothing there either. This morning I went to check the log, as I have done on a more or less daily basis since I cleared the logs (on Jan 4) and received the “Nothing to display” message. I didn’t know whether or not this may simply have been related to something I did in the set-up phase (the problem was with a newly installed controller) so, after retrieving the log entries via the API (they were all there, just not displaying through the web interface), I cleared the logs (per advice in this thread) and all was well… for about another 8 days… Then, on the 17th day, I was unable to display any log entries through the web interface. I don’t think there’s anything else special about my configuration-no other sensors or anything like that.Īs I recall, everything worked as expected for about the first 16 days (based on the log entries that I have managed to save). I have six individual programs running on a seven day cycle, with a mix of sequential and non-sequential stations. I have a v3.0 DC controller configured with one expansion board, controlling 20 stations all up. Ten days ago I thought this thread had solved my problem, but now I seem to be back at square one. You can then delete just the individual daily files rather than the entire log history. On OS (and OSPi), you can use the web api to download all of the logs by typing “ into a web-browser (may need MD5 password hash if enabled) and take a look. To check, on OSPi, you can login to the Pi, change into the log directory and type “grep inf *” to see if any of your logs have this. I would be interested to know if this is the same issue as mentioned above and in #46873. Looking at the code, this could happen if you have a Flow Meter enabled and short duration/low flow runs (my station 4 is just a single dripper for < 2 minutes). Removing these lines resulted in successful logs being displayed for me in the UI. I think the “inf” could be the result of a divide by zero error and the log entries are rejected by the App and trigger the UI error message. If you have a flow meter enabled then the final field should be the flow rate associated with the station run. I took a look at the logs on my OSPi and found a few strange entries across the last 6 months of files:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |