What version are you running? 2.0.8 What's the URL of the page containing the problem? Editing review before sending: http://reviewboard/r/514/diff/# What steps will reproduce the problem? 1. View diff 2. Add comments 3. Press button 'Edit review' 4. Publish. What is the expected output? What do you see instead? Review should be published, instead it hangs with 'Loading' box (more than 60seconds). Review is published but emails are not sent. Sending email with comments to the review works fine. What operating system are you using? What browser? Reviewboard on ubuntu, client on windows 7x64 + firefox. Please provide any additional information below.
Lots of these in error.log: [Wed Oct 01 14:48:39.956329 2014] [core:notice] [pid 16466] AH00051: child pid 24587 exit signal Aborted (6), possible coredump in /etc/apache2 Fatal Python error: PyEval_AcquireThread: NULL new thread state [Wed Oct 01 15:55:03.790827 2014] [core:notice] [pid 16466] AH00051: child pid 24591 exit signal Aborted (6), possible coredump in /etc/apache2 [Wed Oct 01 14:00:29.236012 2014] [:error] [pid 24791] WARNING:py.warnings:/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.8-py2.7.egg/reviewboard/diffviewer/diffutils.py:81: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal [Wed Oct 01 14:00:29.247879 2014] [:error] [pid 24791] if data == "": [Wed Oct 01 14:00:29.247889 2014] [:error] [pid 24791] [Thu Oct 02 10:48:09.668388 2014] [:error] [pid 16477] WARNING:py.warnings:/usr/local/lib/python2.7/dist-packages/Django-1.6.7-py2.7.egg/django/db/models/fields/__init__.py:848: RuntimeWarning: DateTimeField Comment.timestamp received a naive datetime (2014-09-03 00:00:00) while time zone support is active. [Thu Oct 02 10:48:09.668413 2014] [:error] [pid 16477] RuntimeWarning) [Thu Oct 02 10:48:09.673447 2014] [:error] [pid 16477]
I think it may be a problem connecting smtp server. But even in such case 60s is way too much. Sending simple email should be completed in max 15 secs (or make it configurable) or dropped. Anyway I cannot reproduce it now - I'm not able to manipulate smtp server connectivity.