-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
matrix-synapse down and users can not connected #4086
Comments
Hard to say what is causing this without more data on the contents of the http pokes from the client. Are you using Riot? We'll soon have official python 3 packages which should solve this problem for you. In the interim it is also possible to run synapse from source under a py3 virtualenv as per https://github.com/matrix-org/synapse#id11 |
yes
Do it is already stable today for production use? |
Packages will be at week, moth or later? (I need to know this for understand my steps - wait or start from source.) |
server (py2.7) crash again at night:
It is very bad situation - service is very unstable :-( |
As I understand in log not contain full back trace for understand witch code insert utf8 in log function, which crashes after that? |
I also seem to be seeing the Note the black lines in the scrollbar (each one is an instance of that error) seems to be happening a lot more often recently. Doesn't seem related to updating to 0.33.7rc2 as it didn't start happening much until the 2018-10-23 16:48:57. |
|
Let's not assume that all instances of this message have the same cause. @progserega as you note part of the problem here is that it's hard to tell where the bad data is being logged. Running synapse in the foreground rather than via synctl, and setting the |
I start synapse in foreground in screen as: |
@progserega any progress here? It may well be that |
Hmm! But I found UnicodeDecodeError in logs:
|
And again in other log-file:
|
And again one error with such num lines in backtrace (I do not past it here). |
ok great, this sounds like #4160 which is already on our radar. |
(though that doesn't really explain why your whole synapse was falling over) |
@richvdh I think he's saying the problem of it going down is fixed (or at least hasn't happened recently) so this issue can be closed in favor of the other one.
|
@aaronraimist yeah but the mystery of why it hangs when it is not run in a console remains. |
I sink it is not good solution. This is a hack.
Can you tell me - why python not show full backtrace in log in first my message at this issue? |
No, no idea. |
This bug is fixed now? |
This is #4160, which is fixed by #4176, which will be fixed in the next version of synapse. |
Resolving in favour of #4240 which summarises the issue more succinctly |
1 Matrix-synapse down and not proccess request to him.
2. Logs show error and no more record.
3. Clients can not connect to server.
Version information
Matrix set from debian oficial repo.
$ curl -v https://matrix.org/_matrix/client/versions 2>&1 | grep "Server:"
Server: nginx/1.10.3
-->
The text was updated successfully, but these errors were encountered: