Closed ghost closed 5 years ago
I was unable to reproduce the described behavior and it is related to a rogue logging statement that passes more params than what the statement allows. That said, after some additional sidebar conversation with @mnzone-dev this is apparently encountered when there are some missing acc checkpoints. Recalculating the checkpoints is all that is required but, unfortunately, the code that was forked had an offset issue that needed to be fixed first.
Run with reindexmoneysupply
and reindexaccumulators
one time (this may take a few minutes) and see if the issue is fixed.
Here's another build that will not cause the application to exit for a badly formatted string. When running this, please monitor your log file as it should show the culprit.
Spot on! With build 74 I'm no longer seeing the daemon crash. I can share with you the debug.log if it's helpful. Thank you
I'm seeing these messages show up in the shell when the daemon is running in the background:
root@v01:~# libertyd
Liberty server starting
root@v01:~# too many conversion specifiers in format string: %s'
too many conversion specifiers in format string: %s
too many conversion specifiers in format string: %s'
too many conversion specifiers in format string: %s
too many conversion specifiers in format string: %s'
too many conversion specifiers in format string: %s
too many conversion specifiers in format string: %s'
too many conversion specifiers in format string: %s
Build 5.1.1
will have fixes for the incorrectly formatted strings.
Haven't heard any complaints on this since the 5.1.1
release so I'm closing it.
Describe the issue
Linux 5.0.72 wallet failing to start with error:
Can you reliably reproduce the issue?
No, but I have one MN where I'm seeing this error on every start now.
Expected behavior
Wallet starts and syncs
Actual behavior
Wallet starts and after a few seconds the daemon stops
What version of Liberty Coin are you using?
Official 5.0.72, upgraded from official 5.0.58
Machine specs:
Any extra information that might be useful in the debugging process.
debug.log contents: