-
-
Notifications
You must be signed in to change notification settings - Fork 539
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash after upgrading from 6.0.4 to 6.2.0 #1364
Comments
As discussed on today's dev call, it might make sense to not generate a crash log in the case of "FATAL: binlog meta file /var/lib/manticore/binlog/binlog.meta is v.13, binary is v.14; recovery requires previous binary version" and perhaps some other cases when the FATAL error message is sufficient to understand the context. |
the FATAL message on reading empty binlog file with the old format fixed at 828d139 And daemon now could start with the binlog of old format if the binlog empty or has only empty ADD_CACHE operation. |
However there are still crash or deadlocks after FATAL message of the wrong binlog. These are not related to the binlog itself but could happen at the any stage of daemon startup from any Die or FATAL message and should be fixed by investigate and cleanup startup \ shutdown sequence of daemon |
created manticoresoftware/dev/issues/557 for general investigation and refactor of Die or FATAL daemon termination |
Test of the latest dev package on Debian Bookworm - all OK.
|
If you do this (i.e. upgrade an empty Manticore instance from 6.0.4 to 6.2.0):
in Debian Bookworm you'll get the following in the searchd log:
Same with
systemctl stop / start
instead ofrestart
.The task is to fix the crash. There's another issue about why the binlog files are left after a clean shutdown.
The text was updated successfully, but these errors were encountered: