Closed verymilan closed 2 years ago
Update:
I now have tried to logout the affected user. I also noticed that at the same time, the crashloop had stopped, but also any logoutput (warning level) had stopped. The bridge responded to clean-rooms
which previously did not work due to the frequent restarts. Signald also was quite quiet.
Sadly the symptom was not fixed tho, signal->matrix still was broken.
After a restart of the bridge into debug mode, sending from Matrix triggered (successful) log being written, the other way did not make it write any log.
I then restarted SignalD again just for fun. Now a new user is broken, and the error is different:
mausignald.errors.ResponseError: NoSuchAccountError: account not found
Note that this is not the same user as the one i had logged out due to the original error.
Update: Somehow i didnt receive or accidently deleted the Github notification for the latest release. I have updated and this crashloop vanished as well. Fixing one-way delivery also required another signald restart. So this might have been related to #215 somehow. By the way, on logout, i've got a sqlite3 error, but i am using postgres and it still logged me out successfully.. .
Hi there, yesterday a Debian Bullseye was rebooted after updates. Since then, our instance of mautrix-signal is no longer working properly:
Messages only coming from Matrix get sent, and the bridge keeps crashing (aslong as not entirely shutdown by systemd). It seems to be at one specific user althrough i am not shure if this is due to their starting letter of the username.
Signal traceback:
signald also throws errors:
I suppose the cause is simply the crash itself, similar to what Postgres says:
LOG: could not receive data from client: Connection reset by peer
Looking at the Postgres-log, i have noticed that Synapse tried to add the signalbot user on each startup of the bridge, causing a duplicate key error, but i suppose that's normal?
However, right now i am not sure how to proceed with my issue and it's confusing users, because they wouldn't receive errors but also no answers from Signal users. :(