-
Notifications
You must be signed in to change notification settings - Fork 42
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
matrix-synapse doesn't start and crashes #420
Comments
Same problem, new log. https://paste.yunohost.org/asewoyamix It is always a bit of a problem that there is almost never anyone with any ideas to solve problems in the Yunohost surrounding, I mean I tried the easy stuff, I played with the permissions of the log... but is seems the error comes regardless of he permission setting for the file/folder. It's sad that Synapse server only worked for a few weeks and then after an update stopped working. |
Not logging to a file is my solution for now. use this config in /etc/matrix-synapse/log.yaml Edit: Changed both levels to ERROR, don't need that much logging to the journal at the moment. |
Hello, Can you share me the result of this command |
After the permission issues I played around with the permissions, I don't remember the permission when the crashes started. I tried some different combinations of user:group and some different permissions for the folder, the files... Now it is:
I think before it was |
Closing as it quite old and many change was made since this. Please reopen or create a new issue if the issue still appear. |
Describe the bug
matrix-synapse service keeps crashing since I updated it today.
Context
Steps to reproduce
matrix-synapse crashes with the log below and restarts, this happens since I updates all apps (synapse was updated) an hour ago.
Expected behavior
it used to run without any problem.
Logs
journalctl
Remark
I know this bug report is not very meaningful, sorry about that, not sure what else to write, please have a look in the log.
The text was updated successfully, but these errors were encountered: