-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Twisted log output is discarded #7464
Comments
are you sure? how did you start synapse? |
|
Trying to reproduce this locally, I receive the desired output:
You wouldn't happen to have the |
Grepping for stdio in /etc/matrix-synapse produces no results. I've tried with both the logging config supplied with the Debian package and the one generated by synapse itself with the --generate-config switch. The log file does not get the error either. |
do you have |
Nope, no daemonize set either. If I do set no_redirect_stdio to true, then the database error is printed directly to stderr and appears on the terminal. So twisted is eating stderr as it should, but then it just ends up going nowhere. I've yet to figure out what causes it to disappear. |
@DataBeaver: is this still a problem? is the error appearing in the logfile? somewhat related: #4641 |
Yes, this still occurs with Synapse 1.20.1. Version of twisted is 18.9.0 if that matters. It would be acceptable if the error was only in the log and not the terminal I tried to start synapse from, but it doesn't go into the log either. |
weird. can you share your log config? |
also, can you share anything you do see in your logs? |
https://gist.github.com/DataBeaver/443bccea5e10fb99792b2c05e27c9081
|
Well, that should work. Can you try two things for me:
|
Neither of those things, separately or together, causes anything new to appear in the log. |
it seems like |
Description
If the database parameters are incorrect such that synapse can't connect to postgresql, it will exit without printing any kind of error message. The log shows "setting up" as the last line.
Steps to reproduce
I would expect to see some kind of error message pointing me at the database configuration, not a silent exit.
Version information
Synapse 1.12.4, installed from Debian's (unstable/sid) repository.
The text was updated successfully, but these errors were encountered: