Content pfp
Content
@
0 reply
0 recast
0 reaction

Sanjay pfp
Sanjay
@sanjay
We've released 1.11.1. @wazzymandias.eth made it so that hubs will now automatically use snapshot sync to catch up if they are too many messages behind. Note that this will reset the db, if you're running a replicator you can disable this to be safe, by setting `CATCHUP_SYNC_WITH_SNAPSHOT=false` in your .env file
6 replies
2 recasts
11 reactions

patxol πŸ”· anser.social  pfp
patxol πŸ”· anser.social
@patxol.eth
I am now regretting the upgrade. Getting the following error
1 reply
0 recast
0 reaction

Wasif Iqbal pfp
Wasif Iqbal
@wazzymandias.eth
Can you try upgrade to 1.11.2?
1 reply
0 recast
0 reaction

patxol πŸ”· anser.social  pfp
patxol πŸ”· anser.social
@patxol.eth
Hubble upgrade did it all the way to 1.11.2
1 reply
0 recast
0 reaction

Wasif Iqbal pfp
Wasif Iqbal
@wazzymandias.eth
are you on mainnet? it shouldn't be returning that error if you can send me your configuration and the full logs i can dig into it
1 reply
0 recast
0 reaction

patxol πŸ”· anser.social  pfp
patxol πŸ”· anser.social
@patxol.eth
I don’t have access to my hub right now but will DC you all the info ! Thx for your help ! 100 $DEGEN
1 reply
0 recast
0 reaction

Wasif Iqbal pfp
Wasif Iqbal
@wazzymandias.eth
No worries, appreciate your report I pushed up a fix so hopefully you don't run into this error again. Please let us know in the thread if you're still running into issues.
1 reply
0 recast
0 reaction

patxol πŸ”· anser.social  pfp
patxol πŸ”· anser.social
@patxol.eth
Looks like it started working around 3:20 CET. I restarted the hub and now it is synching again getting a snapshot. Will keep you posted !
0 reply
0 recast
1 reaction