1336: reviewboard 500 error
- Duplicate
- Review Board
luke****@gmai***** (Google Code) (Is this you? Claim this profile.) | |
Oct. 7, 2009 | |
What version are you running? What's the URL of the page containing the problem? What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What operating system are you using? What browser? Please provide any additional information below. Error: Publishing the draft has failed due to a server error: 500 Internal Server Error Please try again later. If this continues to happen, please report it to your administrator.
What triggered the error? Can you provide the log file? We need more information than "There was an error."
-
+ NeedInfo
Started seeing the same exact error today. What version are you running? 1.0 What's the URL of the page containing the problem? when publishing a comment (http://servername/r/702/#) then click OK What steps will reproduce the problem? 1. publish a comment 2. get the error listed 3. comment is added, but don't receive an e-mail What is the expected output? What do you see instead? expect to receive an e-mail, but don't. What operating system are you using? What browser? Linux 2.6.27-gentoo-r7 #1 SMP Thu Jan 8 15:53:49 EST 2009 i686 Intel(R) Xeon(R) CPU X7350 @ 2.93GHz GenuineIntel GNU/Linux Firefox and/or IE Please provide any additional information below. Error: Publishing the draft has failed due to a server error: 500 Internal Server Error Please try again later. If this continues to happen, please report it to your administrator. I tried setting Debug = True in settings_local.py and restarting apache, but no new messages seem to be logging.
-
+
1.0, or something newer? The newer versions log more information to the log files. Did you set DEBUG = True, or Debug = True? The latter will not work.
it's "DEBUG = True" i'm going to try and get the latest version installed tonight, i saw there is better logging as of 1.0.2. Is it possible to install 1.0.2 specifically rather than the latest?
1.0.2 was broken. 1.0.3.1 or higher is needed. There's really no reason not to use 1.0.4 though. It should be much more stable. You should have seen some actual debug output regardless on the 500 page though.
attached is the debug info. i am thinking the connection to the exchange server failed and that is the "connection refused"? I know IT did some security patching to exchange and the domain controllers over the weekend so that might be to blame. What do you think? Thanks
-
+
I am sure this is a problem with the connection to exchange: Sending Message... ERROR: Unable to connect to SMTP Host 'xyz.com': (111) Connection refused Unable to connect to SMTP Host 'xyz.com': (111) Connection refused
That certainly sounds like the problem. We should do a better job of not failing when sending an e-mail fails, but that's covered under another bug already.
-
- NeedInfo + Duplicate -
+ 872 - Provide better errors for mail notification failure