Skip to content
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

Message "storm" between two signal-cli systems #777

Closed
Jirka75 opened this issue Oct 15, 2021 · 2 comments
Closed

Message "storm" between two signal-cli systems #777

Jirka75 opened this issue Oct 15, 2021 · 2 comments
Labels

Comments

@Jirka75
Copy link

Jirka75 commented Oct 15, 2021

Two users without smart phones. Each user has a computer containing signal-cli daemon and Signal desktop client. Communication with "smartphone users" works without a problem. Both Lubuntu based systems (NB - 20.04 and PC - 18.04) with signal-cli 0.9.0 and signal desktop 5.18.1.

Sending one or two messages from each side between this two computers leads to a traffic storm of (in this instance) about 80 messages per second for as long as BOTH signal-cli daemons are running, or "relay server" terminates connection due to too many messages.

Tested also without --ignore-attachments switch, messages sent from signal desktop or via "signal-cli --dbus send -m", tested even with closed signal desktop applications. Tested also with signal-cli running as a user service. All leads to this issue of infinite cycle of messages.
Attached logs from either side of communication. "Storm" stopped by terminating signal-cli daemon on PC side (other side would work too) and then started again:

cycle_signalPC1_send_an.txt

cycle_signalNB_recieve_an.txt

@AsamK AsamK closed this as completed in 5648714 Oct 15, 2021
@AsamK
Copy link
Owner

AsamK commented Oct 15, 2021

Thanks for the report, I think I found the issue.
Can you retry with the latest master if it resolves the issue?
You can get a prebuilt version here, once the build is done: https://github.com/AsamK/signal-cli/actions/runs/1346975707

@AsamK AsamK added the bug label Oct 15, 2021
@Jirka75
Copy link
Author

Jirka75 commented Oct 16, 2021

This is great, it looks like the issue is no more. Infinite message cycle will not develop even if just one side is replaced with the new version (signal-cli-archive-16). Both sides with the new version work great too. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants