crash of sage notebook server at login?
Hello, we have the problem, that our sage otebook server crashes from time to time. We use Version 6.3.
This happens at a time when about 10 or 12 students login at about the same time. When this happens, the webinterface (Apache virtual Host) shows "Service Temporarily unavailable" in the website. The complete server has to be rebooted.
Log file of the last crash is attached, the server was rebooted after the crash, which is also shown in the logfile. So the last error is, that a user cannot be found.
I tried to replicate the error. What I found is a weird behaviour of the login screen when given wrong usernames:
If the username is numeric: 12121312312 -> "Error: Username is not in the system " is shown in the login screen
If the username is alphanumeric and begins with a number: 534534534gfdgdfg -> "Error: Username is not in the system " is shown in the login screen
If the username is alphanumeric and begins with a char and is only 2 char long: bb or b3 -> "Error: Username is not in the system " is shown in the login screen
If the username is alphanumeric and begins with a char and is longer than 2 chars: gfdgdfg312312 -> I get a blank screen in the Browser (maybe ERROR 500?) and an entry in the log file,
And I think this may leed to a complete crash of the notebook server from time to time, too.
This posting shows the same problem: https://www.mail-archive.com/sage-dev...
Does anyone have a tip, solution or the same problem?
2014-10-23 12:07:32+0200 [-] WSGI application error
Traceback (most recent call last):
File "/opt/sage6.3/local/lib/python2.7/site-packages/Twisted-13.2.0-py2.7-linux-x86_64.egg/twisted/python/threadpool.py", line 212, in _worker
o = self.q.get()
File "/opt/sage6.3/local/lib/python2.7/site-packages/Twisted-13.2.0-py2.7-linux-x86_64.egg/twisted/python/context.py", line 118, in callWithContext
return self.currentContext().callWithContext(ctx, func, *args, **kw)
File "/opt/sage6.3/local/lib/python2.7/site-packages/Twisted-13.2.0-py2.7-linux-x86_64.egg/twisted/python/context.py", line 83, in callWithContext
self.contexts.pop()
File "/opt/sage6.3/local/lib/python2.7/site-packages/Twisted-13.2.0-py2.7-linux-x86_64.egg/twisted/web/wsgi.py", line 340, in run
self.started = True
--- <exception caught here> ---
File "/opt/sage6.3/local/lib/python2.7/site-packages/Twisted-13.2.0-py2.7-linux-x86_64.egg/twisted/web/wsgi.py", line 315, in run
appIterator = self.application(self.environ, self.startResponse)
File "/opt/sage6.3/local/lib/python2.7/site-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1836, in __call__
return self.wsgi_app(environ, start_response)
File "/opt/sage6.3/local/lib/python2.7/site-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1820, in wsgi_app
response = self.make_response(self.handle_exception(e))
File "/opt/sage6.3/local/lib/python2.7/site-packages/Flask-0.10.1-py2.7.egg/flask/app.py", line 1403, in handle_exception
reraise(exc_type, exc_value, tb)
File "/opt/sage6.3/local/lib/python2.7 ...
I posted a link to this question on [sage-notebook](https://groups.google.com/d/topic/sage-notebook/6kdImFgVMw8), hoping that will get some expert's attention.
I just can't replicate this behavior, especially with regard to the > 2 chars long bit. I just always get the same message.
hm, anyone other can replicate it? maybe it happens at opening worksheets and not right at the login?
The crashing almost certainly happens at opening worksheets, that has been my experience in the past. But again, you really seem to have plenty of RAM, so this surprises me.