You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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
The text was updated successfully, but these errors were encountered: