Toby, can you confirm that this is an ops server issue, not a code issue? 2011-07-21 02:41:46,600 ERROR [syncserver] b37eb7dde1ab77f229150b6d13391be4 2011-07-21 02:41:46,601 ERROR [syncserver] Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/services/util.py", line 499, in __call__ return self.app(environ, start_response) File "/usr/lib/python2.6/site-packages/paste/translogger.py", line 68, in __call__ return self.application(environ, replacement_start_response) File "/usr/lib/python2.6/site-packages/webob/dec.py", line 147, in __call__ resp = self.call_func(req, *args, **self.kwargs) File "/usr/lib/python2.6/site-packages/webob/dec.py", line 208, in call_func return self.func(req, *args, **kwargs) File "/usr/lib/python2.6/site-packages/services/baseapp.py", line 161, in __notified response = func(self, request) File "/usr/lib/python2.6/site-packages/services/baseapp.py", line 222, in __call__ result = function(request, **params) File "/usr/lib/python2.6/site-packages/syncsreg/controller.py", line 119, in generate_password_reset user, password) File "/usr/lib/python2.6/site-packages/services/util.py", line 291, in send_email server.sendmail(sender, [rcpt], msg.as_string()) File "/usr/lib64/python2.6/smtplib.py", line 703, in sendmail (code,resp)=self.rcpt(each, rcpt_options) File "/usr/lib64/python2.6/smtplib.py", line 458, in rcpt return self.getreply() File "/usr/lib64/python2.6/smtplib.py", line 337, in getreply line = self.file.readline() File "/usr/lib64/python2.6/socket.py", line 404, in readline data = self._sock.recv(self._rbufsize) timeout: timed out
This is happening deep within the socket communication layer, so it's likely to be a network problem. The thing that confuses me is that this should produce a dinosaur screen, and for the number of these that appear in the log, I'd have expected someone to report it. It's certainly not happening consistently, because I can't replicate it.
At this point, I'm guessing we're not seeing these any more and it was likely a network issue. Please reopen if we need to dig deeper.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.