Not signed in

Want to take part in these discussions? Sign in if you have an account, or apply for one below

• Username
• Password
• Remember me

• Sign in using OpenID
• Remember me

• Forgot your password?
• Apply for membership

2-category 2-category-theory abelian-categories adjoint algebra algebraic algebraic-geometry algebraic-topology analysis analytic-geometry arithmetic arithmetic-geometry book bundles calculus categorical categories category category-theory chern-weil-theory cohesion cohesive-homotopy-type-theory cohomology colimits combinatorics complex complex-geometry computable-mathematics computer-science constructive cosmology deformation-theory descent diagrams differential differential-cohomology differential-equations differential-geometry digraphs duality elliptic-cohomology enriched fibration foundation foundations functional-analysis functor gauge-theory gebra geometric-quantization geometry graph graphs gravity grothendieck group group-theory harmonic-analysis higher higher-algebra higher-category-theory higher-differential-geometry higher-geometry higher-lie-theory higher-topos-theory homological homological-algebra homotopy homotopy-theory homotopy-type-theory index-theory integration integration-theory k-theory lie-theory limits linear linear-algebra locale localization logic mathematics measure-theory modal modal-logic model model-category-theory monad monads monoidal monoidal-category-theory morphism motives motivic-cohomology nforum nlab noncommutative noncommutative-geometry number-theory of operads operator operator-algebra order-theory pages pasting philosophy physics pro-object probability probability-theory quantization quantum quantum-field quantum-field-theory quantum-mechanics quantum-physics quantum-theory question representation representation-theory riemannian-geometry scheme schemes set set-theory sheaf sheaves simplicial space spin-geometry stable-homotopy-theory stack string string-theory superalgebra supergeometry svg symplectic-geometry synthetic-differential-geometry terminology theory topology topos topos-theory tqft type type-theory universal variational-calculus

1. • CommentRowNumber1.
   • CommentAuthorTobyBartels
   • CommentTimeNov 23rd 2009
   • PermaLink
   Author: TobyBartels
   Format: MarkdownThe Ruby on Rails app underlying the Lab seems to have gone down about 15–30 minutes ago, and it's too big for me to handle. But I've written Andrew about it.

   The Ruby on Rails app underlying the Lab seems to have gone down about 15–30 minutes ago, and it's too big for me to handle. But I've written Andrew about it.

2. • CommentRowNumber2.
   • CommentAuthorTobyBartels
   • CommentTimeNov 23rd 2009
   • PermaLink
   Author: TobyBartels
   Format: MarkdownIt's back; hoorah for Andrew!

   It's back; hoorah for Andrew!

3. • CommentRowNumber3.
   • CommentAuthorAndrew Stacey
   • CommentTimeNov 23rd 2009
   • PermaLink
   Author: Andrew Stacey
   Format: MarkdownFixed. This crash was due to a slight difference between the nlab version of instiki and the official version. It's very minor, but caused a conflict in the latest update that the automatic updater couldn't resolve. I'll see what methods we can put in place to prevent this in future. Options are: 1. Only do updates when someone who can deal with such things is online. 2. Provide an automatic checker so that if there are conflicts, the update isn't done. 3. Provide an easy rollback script so that if there are conflicts, a labelf with enough access can easily roll back the update until someone who can deal with such things can check it. I don't like option 1 as these things should be rare but there are frequent updates so this feels like cutting ones arm off because one sometimes gets a torn fingernail. Option 2 is my preferred option, but I don't yet know if it's possible (haven't looked, though). Option 3 would be the easiest as it just involves writing some instructions. For non-technically minded people, the only thing you need to worry about is what the crash _looked like_. It was a great big multi-coloured page with lots of technical code on it with a big header saying "Ruby on Rails application cannot be started". If you get that again, save the page and email it to me. For lab elves, an error like this means that the main pieces of the infrastructure are working. To see anything complicated means that apache is working, to see an error message giving details of why the application could not be started means that ruby-on-rails _itself_ is working. These are the two pieces covered by the "hard" and "soft" restarts respectively, so that's why they didn't work in this instance.

   Fixed.

   This crash was due to a slight difference between the nlab version of instiki and the official version. It's very minor, but caused a conflict in the latest update that the automatic updater couldn't resolve. I'll see what methods we can put in place to prevent this in future. Options are:

   1. Only do updates when someone who can deal with such things is online.
   2. Provide an automatic checker so that if there are conflicts, the update isn't done.
   3. Provide an easy rollback script so that if there are conflicts, a labelf with enough access can easily roll back the update until someone who can deal with such things can check it.

   I don't like option 1 as these things should be rare but there are frequent updates so this feels like cutting ones arm off because one sometimes gets a torn fingernail. Option 2 is my preferred option, but I don't yet know if it's possible (haven't looked, though). Option 3 would be the easiest as it just involves writing some instructions.

   For non-technically minded people, the only thing you need to worry about is what the crash looked like. It was a great big multi-coloured page with lots of technical code on it with a big header saying "Ruby on Rails application cannot be started". If you get that again, save the page and email it to me.

   For lab elves, an error like this means that the main pieces of the infrastructure are working. To see anything complicated means that apache is working, to see an error message giving details of why the application could not be started means that ruby-on-rails itself is working. These are the two pieces covered by the "hard" and "soft" restarts respectively, so that's why they didn't work in this instance.

4. • CommentRowNumber4.
   • CommentAuthorTobyBartels
   • CommentTimeNov 23rd 2009
   • PermaLink
   Author: TobyBartels
   Format: MarkdownYeah, (2) seems ideal, but (3) would still be good if (2) doesn't work (or takes a long time to get to work).

   Yeah, (2) seems ideal, but (3) would still be good if (2) doesn't work (or takes a long time to get to work).