Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

v4.5.2 Upgrade Breaks Notebook, "got EOF subprocess must have crashed..."

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