Thanks! It is back up, although it is still very slow. I'm guessing that it has a heavy load already.
--Bill On Oct 20, 10:09 am, Jason Grout <[email protected]> wrote: > On 10/20/11 9:01 AM, MichTex wrote: > > > I've been trying to login to sagenb this morning. It took over a > > minute for the server to respond when I first went to the login page. > > After another long wait, it finally logged in. Then when I clicked on > > the link to the worksheet that I wanted, there was a third long wait, > > which finally produced a 503 error. Now all attempts to reach the > > server simply produce the 'Service Temporarily Unavailable' message. I > > know that traffic on sagenb has greatly increased in the last few > > weeks, so perhaps the poor machine is maxed out in some way. > > This is in the error log: > > /sagenb/sage_install/sage-4.7.1/local/lib/libpython2.6.so.1.0(PyEval_CallOb > jectWithKeywords+0x56)[0x7fe74a7474f6] > /sagenb/sage_install/sage-4.7.1/local/lib/libpython2.6.so.1.0[0x7fe74a7813c d] > /lib/libpthread.so.0[0x7fe74a4563f7] > /lib/libc.so.6(clone+0x6d)[0x7fe749b3dbbd] > > ------------------------------------------------------------------------ > Unhandled SIGSEGV: A segmentation fault occurred in Sage. > This probably occurred because a *compiled* component of Sage has a bug > in it and is not properly wrapped with sig_on(), sig_off(). You might > want to run Sage under gdb with 'sage -gdb' to debug this. > Sage will now terminate. > ------------------------------------------------------------------------ > Segmentation fault > > (full error log athttp://pastebin.com/FQzxqsZg) > > I'm restarting the server, as it says it is stopped currently. > > Thanks, > > Jason -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
