disasteraverted's profile - activity

If I run this manually, it works. i.e. cd /usr/local/sage; ./sage; then enter the appropriate notebook () command. If I use the ~sageuser/.sage/init.sage file to start the notebook with the same command it doesn't work. Must be some permissions minutia. Thanks for the ideas.

Yes, I did a "make testlong" and got only a few errors (according to the power user here they are inconsequential)... a few tests timed out: sage0.py, expect.py, psage.py. These also failed: trace.py, sagedoc.py. Thanks, Nick

Thanks ccanonc, However, I don't think it's an issue, I think the error message is a misnomer. There is only one twistd process, and if I kill that I can't use the web interface. sageuser 8226 8197 4 07:40 ? 00:00:02 python /usr/local/sage-4.5.2/local/bin/twistd --pidfile=nbfiles. ...

I upgraded last week from v4.3 to v4.5.2 using the fantastic "sage -upgrade" command. The build and testing seem to work great, and everything starts up as normal. I log into the notebook, open a saved worksheet and everything seems fine. However, when I got to "evaluate" nothing happens at the browser level. Doing the same expression from the sage command line works fine.

Looking at the console, I see:

2010-08-30 10:24:21-0700 [HTTPChannel,49,127.0.0.1] got EOF subprocess must have crashed...
2010-08-30 10:24:21-0700 [HTTPChannel,49,127.0.0.1]
2010-08-30 10:24:21-0700 [HTTPChannel,49,127.0.0.1] import os;os.chdir("/tmp/tmp_ECyTK");
2010-08-30 10:24:21-0700 [HTTPChannel,49,127.0.0.1] execfile("_sage_input_2.py")
2010-08-30 10:24:21-0700 [HTTPChannel,49,127.0.0.1] The notebook files are stored in: nbfiles.sagenb
2010-08-30 10:24:21-0700 [HTTPChannel,49,127.0.0.1] Another Sage Notebook server is running, PID 2517.
2010-08-30 10:24:21-0700 [HTTPChannel,49,127.0.0.1]
2010-08-30 10:24:21-0700 [HTTPChannel,49,127.0.0.1] Please either stop the old server or run the new server in a different directory.

Based on this I did some sluthing, and found that once I click on a worksheet (or create a new one), a new python process is spawned. However, that process dies almost immediately, complaining about another notebook server running... however, the notebook server running is the one I'm using, so not like I can stop it.

Is there any way to add logging/debugging to the spawned python process? Any ideas on where to go from here? I'm really stuck.

Thanks!

Nick