Skip to content

Request for more logging on node reporting #1041

@skyler440

Description

@skyler440

I am dealing with identifying a potential bug, where the list of non-adjacent nodes gets "stuck" during a disconnect, and prevents us from being able to bring the connection back, which is negatively impacting our large ASL3 hub requiring frequent asterisk restarts to correct.

Even with the maximum debug, the only form of logging we get is the "playing remote-already.gsm" audio file. There is nothing logged about why it thinks this node is still connected, or which adjacent neighbor it might think its coming from.

This request is to increase the logging, in particular on this neighboring node list which is exchanged between different connected allstarlink nodes. If we had a way to report why the hub thinks these phantom nodes are still connected even though they are not, it would be very insightful.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions