The title may not reflect what's actually occurring here, so feel free to change it. I've seen this behavior crop up once or twice now, once in 1.2.4 and now recently on 1.2.6 (with recent boost updates from 1.2.x branch). It's very infrequent, and I have very little idea of how to troubleshoot it or resolve it, but I wanted to make sure you were aware that it has occurred.
Here is some output I'm seeing in the boost.log which is of concern:
ERROR: unknown DS name '1569353360'
ERROR: unknown DS name '1569353358'
2019/09/24 13:45:10 - SYSTEM BOOST STATS: Time:38.3000 RRDUpdates:198246
ERROR: Not enough arguments
ERROR: Not enough arguments
ERROR: Not enough arguments
ERROR: Not enough arguments
ERROR: Not enough arguments
ERROR: Not enough arguments
ERROR: Not enough arguments
ERROR: opening '1569354366:3185:3185': No such file or directory
ERROR: opening '1569354366:0.00:0.00:0.35:0.02': No such file or directory
ERROR: opening '1569354366:0.00:0.00:0.00:0.00': No such file or directory
ERROR: opening '1569354366:0.00:0.00:0.00:0.00': No such file or directory
ERROR: opening '1569354366:0.00:0.00:0.32:0.00': No such file or directory
ERROR: opening '1569354366:0.00:0.00:0.00:0.00': No such file or directory
ERROR: opening '1569354366:0.00:0.00:0.00:0.00': No such file or directory
ERROR: opening '1569354366:0.00:0.00:0.00:0.00': No such file or directory
ERROR: opening '1569354366:0.00:0.00:0.05:0.00': No such file or directory
ERROR: opening '1569354366:0:16:0:8:0:1154386:0:0:0:0:24:0:0:0:30:0': No such file or directory
ERROR: opening '1569354366:67:0:1169973:1029509:1016:1015:1058477:970532:95907:96125': No such file or directory
ERROR: opening '1569354366:0:0:0:0:0:0:259:702:0:0:0:0:0:6899:0:0:0:0:0:0:1016:0:0:0:0': No such file or directory
ERROR: opening '1569354366:30460:898:2:24083:0:26333:2641:1977': No such file or directory
2019/09/24 14:01:08 - SYSTEM BOOST STATS: Time:39.0000 RRDUpdates:195759
This is just a snippet from one bad boost run that's occurred since 9/22. But that run itself had lots of OK messages, it just got tripped up towards the end.
The title may not reflect what's actually occurring here, so feel free to change it. I've seen this behavior crop up once or twice now, once in 1.2.4 and now recently on 1.2.6 (with recent boost updates from 1.2.x branch). It's very infrequent, and I have very little idea of how to troubleshoot it or resolve it, but I wanted to make sure you were aware that it has occurred.
Here is some output I'm seeing in the boost.log which is of concern:
This is just a snippet from one bad boost run that's occurred since 9/22. But that run itself had lots of OK messages, it just got tripped up towards the end.