WARN hashstore mismatched log tail

One more question, what this mean and how to fix?

2026-03-05T00:05:15+03:00 WARN hashstore mismatched log tail {"process": "storagenode", "satellite": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "store": "s1", "id": 2433, "path": "config/storage/hashstore/12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs/s1/81/log-0000000000000981-00005058", "table": [{"Key":"WLWJCVYFAOQNB24SPXY5R2NXDR7Y74SP5IRDLKXQ3DMY7FTV47FQ","Offset":6959808,"Log":2433,"Length":2319872,"Created":20476,"Expires":41136},{"Key":"H7SZP3CQXMYW6N7KQKKJA5KF3NWN4ELNZJ5BPN7XM6PBE62MKD2A","Offset":2319936,"Log":2433,"Length":2319872,"Created":20476,"Expires":41136},{"Key":"LQVHN26REMAPH5DJHHQHQCF5X64NABEVC5ZEFZI52JG53A2SMHHQ","Offset":0,"Log":2433,"Length":2319872,"Created":20476,"Expires":41136},{"Key":"AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA","Offset":0,"Log":0,"Length":0,"Created":0,"Expires":0},{"Key":"AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA","Offset":0,"Log":0,"Length":0,"Created":0,"Expires":0}], "log": [{"Key":"WLWJCVYFAOQNB24SPXY5R2NXDR7Y74SP5IRDLKXQ3DMY7FTV47FQ","Offset":6959808,"Log":2433,"Length":2319872,"Created":20476,"Expires":41136},{"Key":"2PYBIOF4HSRAAEQKFQ6UVQGPYM7AS4P4BTGM23KV6D2TSRCQ4LWQ","Offset":4639872,"Log":2433,"Length":2319872,"Created":20476,"Expires":41136},{"Key":"H7SZP3CQXMYW6N7KQKKJA5KF3NWN4ELNZJ5BPN7XM6PBE62MKD2A","Offset":2319936,"Log":2433,"Length":2319872,"Created":20476,"Expires":41136},{"Key":"LQVHN26REMAPH5DJHHQHQCF5X64NABEVC5ZEFZI52JG53A2SMHHQ","Offset":0,"Log":2433,"Length":2319872,"Created":20476,"Expires":41136},{"Key":"AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA","Offset":0,"Log":0,"Length":0,"Created":0,"Expires":0}]}

PS: Will answer on my own question: warnings gone after second restart, clean start in the logs. So i think second restart not needed, it (if any) was fixed on first start after update.

Yes, the restart was not needed, this issue should be fixed on start (there is fsck for hashstore, so it checked, printed and fixed this minor issue).

Same here.
After the “Mismatched log tail” error and accordingly with “storagenode.exe” on Windows, it stops the service, restarts but the error appears again and it´s looping!
After the second service restart, again…and there´s no third as the third Windows service action is “Take no action”.

This is a warning, not error. It shouldn’t stop the service.
Could you please search for the FATAL or Unrecoverable error in your logs?

For some reason it´s working now :face_with_raised_eyebrow:

Of course it should. There is a hashstore fsck, which is started on restart, it should check and fix issues.