My students reported this same thing over the weekend as they were
trying to do a project on sagenb.org. This morning I'm experiencing
the same problem, and it seems another class is, too:
http://groups.google.com/group/sage-support/browse_frm/thread/51d5129903cc4671
Did some recent change cause these processes to be created more often
than they used to be? Or are we just having a confluence of heavy
use?
Nathan
PS: Thanks again for a nice, responsive email list and community.
On Feb 28, 11:17 pm, William Stein <[email protected]> wrote:
> On Sun, Feb 28, 2010 at 9:05 AM, Minh Nguyen <[email protected]> wrote:
> > Hi Bjarke,
>
> > On Mon, Mar 1, 2010 at 4:02 AM, Bjarke Hammersholt Roune
> > <[email protected]> wrote:
>
> > <SNIP>
>
> >> mvngu in the sage-devel IRC channel wrote:
>
> > Here is the relevant IRC log:
>
> > 08:45 < SageWWW> I typed this into a Sage worksheet:
> > 08:45 < SageWWW> a = 5
> > 08:45 < SageWWW> a
> > 08:45 < SageWWW> usinghttp://www.sagenb.org/home/
> > 08:46 < SageWWW> The output is just a small green rectangle that
> > disappears in a few seconds
> > 08:46 < SageWWW> Typing just "1+1" does the same thing
> > 08:47 < SageWWW> I'm on Firefox 3.5.8
> > 08:47 < SageWWW> any ideas about how I can get this working?
> > 08:47 < mvngu> SageWWW: Do you want to print the value of "a"?
> > 08:48 < SageWWW> yep
> > 08:48 < SageWWW> or get it to display anything at all
> > 08:49 < SageWWW> e.g. I would expect writing just 1+1 and then
> > clicking evaluate would result in the integer 2 being displayed.
> > 08:51 < SageWWW> but for me it displays a green rectangle which then
> > disappears and that's it.
> > 08:52 < mvngu> SageWWW: I'm getting the same issue with the online
> > Sage notebook interface. I also tried using "print a", but to no
> > effect. Could report this matter to the sage-support mailing list?
> > 08:52 < mvngu> *Could you...
> > 08:56 < SageWWW> OK
>
> This is caused by:
>
> sagen...@boxen:~$ sage
> -bash: fork: Resource temporarily unavailable
> sagen...@boxen:~$
>
> I limit the number of sagenbws (sage notebook worksheet) processes
> that can be created in order to avoid forkbombs (which can trivially
> bring down a server).
>
> Anyway, I killed all running sagenbws processes, and now things work
> fine again on sagenb.org. Thanks again for reporting this issue.
>
> -- William
>
> There are (way) too many sagenbws processes, evidently.
--
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
