Skip to content

Nodes change to wating for network and back to standby randomly #983

@ostrs1

Description

@ostrs1
What is the issue?

🔴 2 nodes randomly go to wating for network and than back to standby after few seconds 🔴

What impact does the issue have?

🔴 not sure what it breaks but i suspect it takes me out of selection to be active and who knows what other issues arise from this 🔴

How to reproduce the issue?

🔴
Explain in as much detail as possible to help reproduce the bug:

i have telegram bot listener on state changes, it sends me message when it changes to waiting for the network daily    
i receive this message on both nodes , but different times
Here is a sample of the logg, same logg every time it fails:
[2025-06-19T07:01:08.274] [ERROR] main - invoke-exit: removed from standby list exitCleanly
[2025-06-19T07:01:08.274] [ERROR] main - validator removed from standby list
[2025-06-19T07:01:08.274] [ERROR] main - Error: Artificially induced error to get a call stack
    at getCallstack (/usr/src/app/node_modules/@shardeum-foundation/core/dist/utils/getCallstack.js:4:15)
    at attemptJoining (/usr/src/app/node_modules/@shardeum-foundation/core/dist/p2p/Self.js:345:117)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

🔴

What other resources can you share regarding this issue?

🔴 hardware on each node: 16 cpu, 50gb ram, 250gb nvme , 300meg network 🔴

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions