Skip to content

chan_voter: Doesn't detect loss of master client when it is the only client #856

@ve7fet

Description

@ve7fet

The "master" client is the master timing source for an instance. If it isn't available, then nothing else matters.

In a configuration where we have a master client and >1 "other" clients, and the master client disappears, we detect that and throw a warning: VOTER lost master timing source!!". We should probably do something else to shut the channel down, but that is a different issue.

In a configuration where we only have a master client configured, and that client goes away (ie network disconnected), chan_voter does not detect that anything is wrong. There are timeout checks, but it appears that we never get to that part of the code.

It appears that as long as there is data coming in the UDP port from multiple clients, we continue to iterate on the voter_reader loop, and can detect the loss of the master client.

However, if the master client is the only client sending data, and it stops, we aren't handling that case, since there are no more packets to process.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingcode qualityImprovments around code quality without functional changes

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions