William Stein a écrit : >> I'm not sure why, but the storage abstraction broke my multiple boxes >> acting as compute nodes via NFS and server_pool. If I run the >> notebook with a localhost login server_pool=['sa...@localhost'], then >> it works. If I don't, server_pool=['sa...@node1'], then it appears >> that the server opens a connection to the compute nodes but those >> never return any values. Is there some new folder that I should be >> exporting to get this to work? Is the issue possibly with NFS? >> >> I realize that I'm stretching the bounds of what server_pool is >> supposed to do, but ideas would be appreciated. > > As a test, can you make it so node1's /tmp is an NFS mounted version > of /tmp on localhost? If you can't do that, I can give you further > instructions to change the sage notebook so it uses a directory > different from /tmp for computation. > > -- William >
Is it not a simple problem of rights ? I have quite the same configuration as yours: I had to make the "home" directory group writeable (sage* are in the same group). Other possibility: what happens when your sage main user (the one which runs the notebook) do a ssh to sa...@node1 ? If there is even only one problem with one user (like requesting y/n confirmation) you will get the error you are talking about, I think. t. > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
<<attachment: tdumont.vcf>>
