-
Notifications
You must be signed in to change notification settings - Fork 22
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
PBSS + v1.3.6/v1.3.7 OOM, please keep v1.3.5 version #132
Comments
If you capture relevant metrics information, please collect it and feedback it to the BSC team |
AFIK, v1.3.7 does not have any memory related changes, no idea why v1.3.7 has the OOM issue while v1.3.6 not. |
According to feedback from a community user, he experienced an OOM after running the pbss node for two days and could no longer start it. The same problem also occurred after I upgraded to 1.3.7, but the running time was different. It seemed that there was no specific pattern. Positioning The problem may be more troublesome |
This is the stdout information of restart after oom
|
Other users have reported that version 1.3.6 has the same problem and they may need to use version 1.3.5. |
@du5 which snapshot do you use? Do you do any operations before panic happens, such as restart geth? |
The version I found the problem with is https://snapshots.48.club/geth.pbss.34712063.tar.zst, geth was launched without any warning, without any Panic error, it ended directly, based on these symptoms I identified it as "oom". When "oom" occurs and you start again, there will be a panic log. What I did after that was to re-unzip and synchronize using v1.3.6, which worked for me, and it has been working normally until now. But I observed that v1.3.6 also had users reporting this problem, and it was solved in v1.3.5. This problem will occur with snapshots built using BSCTeam or 48Club. It seems that the snapshot itself is not damaged. btw, the geth.pbss.34712063.tar.zst snapshot has been deleted, but the latest snapshot is obtained after synchronizing this snapshot. |
I find this issue has completed, so what's the version we should use with PBSS? The README still display we need use v1.3.5 |
the latest v1.3.7 is ok to run PBSS, but may have some issue with some snapshot provided by 48Club, due to the --pruneancient compatible issue. |
Due to a series of problems caused by pruneancient, we have decided not to use this tag in the future. There are many problems with the future of bsc-geth. Turning this tag on in version 1.3.x will not prune the database, and the database size continues to grow. I have multiple nodes where pruneancient is also turned on. The minimum database size is 1.1tb and the maximum is 1.9tb. I think there is a problem with the pruneancient function logic and it is not a problem with the snapshot. Regarding the conflict between pbss and pruneancient, I still recommend using version v1.3.5 |
I use v1.3.5 version bsc-geth and this snapshot "https://snapshots.48.club/geth.pbss.35485953.tar.zst", still oom. and restart the process report "panic: runtime error: invalid memory address or nil pointer dereference": goroutine 1 [running]: github.com/ethereum/go-ethereum/core/rawdb.(*ResettableFreezer).AncientRange(0xcfe340?, {0x28e1341?, 0xc017550b68?}, 0xc017550c68?, 0x248a500?, 0xc01872a420?) /home/runner/work/bsc/bsc/core/rawdb/freezer_resettable.go:125 +0x5c github.com/ethereum/go-ethereum/core/rawdb.ReadStateHistoryMetaList(...) /home/runner/work/bsc/bsc/core/rawdb/accessors_state.go:180 github.com/ethereum/go-ethereum/trie/triedb/pathdb.checkHistories(0x0, 0x13206fae5cdc8042?, 0xbd42451522faaccd?, 0xc01349d750) /home/runner/work/bsc/bsc/trie/triedb/pathdb/history.go:548 +0x85 github.com/ethereum/go-ethereum/trie/triedb/pathdb.(*Database).Recoverable(0xc0113eb450, {0xa3, 0x1a, 0x76, 0xb8, 0x13, 0xe6, 0x1d, 0x22, 0x42, ...}) /home/runner/work/bsc/bsc/trie/triedb/pathdb/database.go:363 +0x205 github.com/ethereum/go-ethereum/trie.(*Database).Recoverable(0x7faef645daa8?, {0xa3, 0x1a, 0x76, 0xb8, 0x13, 0xe6, 0x1d, 0x22, 0x42, ...}) /home/runner/work/bsc/bsc/trie/database.go:320 +0x45 github.com/ethereum/go-ethereum/core.NewBlockChain({0x33a14d8?, 0xc0134763c0}, 0x0?, 0x0?, 0x0?, {0x338fdc0?, 0xc00127f100?}, {{0x0, 0x0}, 0x0, ...}, ...) /home/runner/work/bsc/bsc/core/blockchain.go:403 +0x14b0 github.com/ethereum/go-ethereum/eth.New(0xc0010520e0, 0xc0014b1000) /home/runner/work/bsc/bsc/eth/backend.go:252 +0x170f github.com/ethereum/go-ethereum/cmd/utils.RegisterEthService(0x0?, 0xc0014b1000) /home/runner/work/bsc/bsc/cmd/utils/flags.go:2156 +0x167 main.makeFullNode(0xc001c3fbf0?) /home/runner/work/bsc/bsc/cmd/geth/config.go:175 +0x255 main.geth(0xc001a21340) /home/runner/work/bsc/bsc/cmd/geth/main.go:341 +0xf3 github.com/urfave/cli/v2.(*Command).Run(0xc001aac000, 0xc001a21340, {0xc000134000, 0x12, 0x12}) /home/runner/go/pkg/mod/github.com/urfave/cli/v2@v2.25.7/command.go:274 +0x9eb github.com/urfave/cli/v2.(*App).RunContext(0xc0013a0f00, {0x3379910?, 0xc000130010}, {0xc000134000, 0x12, 0x12}) /home/runner/go/pkg/mod/github.com/urfave/cli/v2@v2.25.7/app.go:332 +0x616 github.com/urfave/cli/v2.(*App).Run(...) /home/runner/go/pkg/mod/github.com/urfave/cli/v2@v2.25.7/app.go:309 main.main() /home/runner/work/bsc/bsc/cmd/geth/main.go:284 +0x47so I think we should not use the snapshot with pbss flag. |
@xux1217 If the database is damaged, downgrading cannot repair it at this time. You need to download it again. Downgrading must be done before the database is damaged. |
I am sure that I first download the snapshot, and then just use the v1.3.5 bsc-geth to start, not downgrade action. my start cmd: and the config.yaml:
|
i have the same issue, fresh download with 1.3.5 |
PBSS + v1.3.6/v1.3.7 OOM, please keep v1.3.5 version
Due to the update of bnb-chain/bsc#2155 code, v1.3.8 cannot start this snapshot, please wait for the new snapshot to be released
The text was updated successfully, but these errors were encountered: