LNT internal server error

Hi Chris, hi Daniel,

I see again internal server errors when visiting llvm.org/perf. I remember you have been restarting the service several times, but it seems it is happening again. Did you ever had time to investigate the issue? Is there something I can help with?


I poked it again. Chris, what’s the status of the patches to enable better logging in LNT?

  • Daniel


Any progress on the debugging side?



  • Daniel

I have pushed my commits.

Logging will be in /var/log/lnt/lnt.log. You will need to make that directory. If anyone knows how to make setuptools do that at install time, please send me hints.

I have been debugging an ISE here recently, it was caused by a segfault in httpd. In cases like that, OS crash logs have better data than the LNT log.

Hi Chris,

On a related note, have you seen my patch for not needing to submit by
default? Is that what you had in mind?


That is exactly what I had in mind. Thanks!


could you have a look into the new logs. I just got the following timeouts from the buildbots:


   File "/home/grosser/buildslave/pollyperf-O3-polly/lnt/lnt/util/ServerUtil.py", line 25, in submitFileToServer
     response = urllib2.urlopen(urllib2.Request(url, data))
   File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen
     return _opener.open(url, data, timeout)
   File "/usr/lib/python2.7/urllib2.py", line 401, in open
     response = self._open(req, data)
   File "/usr/lib/python2.7/urllib2.py", line 419, in _open
     '_open', req)
   File "/usr/lib/python2.7/urllib2.py", line 379, in _call_chain
     result = func(*args)
   File "/usr/lib/python2.7/urllib2.py", line 1211, in http_open
     return self.do_open(httplib.HTTPConnection, req)
   File "/usr/lib/python2.7/urllib2.py", line 1181, in do_open
     raise URLError(err)
urllib2.URLError: <urlopen error [Errno 104] Connection reset by peer>
program finished with exit code 1


Hi Tobi,

My bot also failed, but trying to svn checkout, maybe it was just a
temporary connection problem?


Hard to say if that was a server error or not. Might be worth checking the server logs, both for LNT and the syslog.

Looks like it happened at: Sun Mar 23 15:18:57 2014

And again internal server errors at llvm.org/perf.