--from not respected post abnormal restart

[jun0tpyrc]

let's say specifying 38200000 and indexed some blocks

[ 4][t 6][2024-06-25 01:37:11.480331842][EventProcessor.cpp:138][!jetton_wallet_detector]       Event: O9Va5oASa8M1vxVbQOombqnJsPfbUrrN83KIQpzBOkI=
[ 4][t 6][2024-06-25 01:37:11.480345057][EventProcessor.cpp:138][!jetton_wallet_detector]       Event: naoZXe3ImW5vNWwRCzZLwvs3H+//7JPHQeIHz56Uun0=
[ 4][t 6][2024-06-25 01:37:11.480361491][EventProcessor.cpp:138][!jetton_wallet_detector]       Event: yEDcvyphTsVy7ptEKQTHZm62+qKzlnGai0J0uHKqYYM=
[ 4][t 6][2024-06-25 01:37:11.480373049][EventProcessor.cpp:138][!jetton_wallet_detector]       Event: TBfPHcrF1sZTfUwbYiMl7XOYAKGh9PFAmQmEsnDOpd8=
[ 4][t 6][2024-06-25 01:37:11.480381686][EventProcessor.cpp:138][!jetton_wallet_detector]       Event: NqjwnMflMbsBJ1Y4NR94C3mZ1j3+lKAyPJLlHIVRxks=
[pid 11] [time 1719279431] Signal: 11
------- Stack Backtrace -------
ton-index-postgres(+0x35b042)[0x5a7e11d38042]
ton-index-postgres(+0x35b355)[0x5a7e11d38355]
ton-index-postgres(+0x35ae9f)[0x5a7e11d37e9f]
/lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x77effc08f520]
ton-index-postgres(+0x363d58)[0x5a7e11d40d58]
ton-index-postgres(+0x364045)[0x5a7e11d41045]
ton-index-postgres(+0x328fa5)[0x5a7e11d05fa5]
ton-index-postgres(+0x331d29)[0x5a7e11d0ed29]
ton-index-postgres(+0x3348a6)[0x5a7e11d118a6]
ton-index-postgres(+0x33741b)[0x5a7e11d1441b]
ton-index-postgres(+0x339c55)[0x5a7e11d16c55]
ton-index-postgres(+0x398ab6)[0x5a7e11d75ab6]
ton-index-postgres(+0x398cfd)[0x5a7e11d75cfd]
ton-index-postgres(+0x3a98c3)[0x5a7e11d868c3]
ton-index-postgres(+0x39c6bf)[0x5a7e11d796bf]
ton-index-postgres(+0x2a1b8a)[0x5a7e11c7eb8a]
/lib/x86_64-linux-gnu/libc.so.6(+0x94ac3)[0x77effc0e1ac3]

after hitting this abnormal restart, it will not respect the last ones and go from very low seqno (which may not exist for non-archive node nor wanted )

[jun0tpyrc]

this occur occasionally , but if reboot index-worker one or few times ,it works again

[dungeon-master-666]

Thanks for reporting! We've made some improvements, and this bug should be fixed in the latest commit of the master branch. Feel free to reopen the issue if you still encounter it.