Want to take part in these discussions? Sign in if you have an account, or apply for one below
Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.
I was getting
Connection Interrupted The document contains no data. The network link was interrupted while negotiating a connection. Please try again.
So I restarted the web server (‘hard’ restart). Now it's back.
Thanks! Relief. It was cold turkey.
Now that we have restarted, something is amiss with (I think) the CSS.
Whenever I load a page that (I think) is not in my browser's cache, my browser (Firefox 3.0 for Ubuntu) no longer colours links appropriately as visited. This only applies to links affected by CSS markup (existingWikiWord, etc), the few links that are not marked up at all (mostly in contents listings) are fine. (Note that colours are specified by the CSS for these; they are just not in any special class.) For the few pages in which visited links are coloured differently (I assume because they're in my browser's cache, the page has not changed, and it is not asking for the CSS to be reloaded, although that seems like incorrect behaviour), editing the page will cause the bug.
There was a CSS update in the last batch, but I've not yet looked at it to see what the changes were. It's possible that this has changed things that ought not to have been changed.
On the crash, I'm a bit at a loss as to what caused it. My current hypothesis is that it was pure bad luck: the nlab processes were writing to the log files at the same time as the log files were being rotated and the nlab didn't like having them changed under it. My evidence for this is that it seems that the crash happened in between the log rotation and the only error message that I can find is about passenger trying to unlock a resource that was locked by something else. (This really shouldn't have caused a crash, though).
The proper solution is that I finally get round to installing a few automatic monitoring programs that keep an eye on things and try to restart programs when they aren't running. Just when I thought I could get back into the lab to do some mathematics as well ...
As a reminder, though: it's not just Toby and me that can restart the lab. Anyone who has any access whatsoever to the server can do the restart commands.
Re CSS:
My hypothesis in #3 is quite wrong, which I realised just before I lost my Internet connection a couple of days ago.
The offending line is not in the CSS files but in the individual pages' CSS commands.
In the <style type="text/css"> command, a new line has been added:
a:visited.existingWikiWord {
color: #005c19;
}
This line colours visited links within the web green. It affects every web, in a way vaguely consistent that web's colour scheme. (However, the offending colour is not quite the same colour as unvisited links within the web, just close enough to be confusing.)
This line appears when the cached file on the Instiki server either does not exist or is overwritten because the page has been edited. (It has nothing to do with my browser's local cache.)
Maybe this should go on another thread. It seemed to happen at the same time as the crash, but probably they are not connected.
It's not related to the crash but to an update that happened that day. There've been a few updates to the CSS recently. Maybe it's time we sorted out the CSS once and for all!
The "stylesheet tweaks" seem to come last in the list and therefore ought to override everything (assuming I've understood how CSS works correctly) so we should be able to fix things like this ourselves.
1 to 8 of 8