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 just had to restart the webserver on the nlab. Hopefully it was fast enough that no-one noticed.
Something big just hit us. I'm not sure what it was yet; it might just have been a huge spike in activity since we're getting linked a lot from mathoverflow, but it might have been something else. Whatever it was, it got us up to our soft memory limit and a soft reset of Instiki didn't help. I think that the reason that the soft reset didn't help was that we needed to flush the queue of pending requests for the Instiki process - the soft reset doesn't do that but restarting apache does.
Ideally, if we're getting more traffic then the answer is to allow more concurrent processes. However, as we managed to reach our soft limit then something is still ballooning up the memory load. I need to track this down and get Jacques to fix it. In the meantime, those with access to the server and the ability to restart things, be alert (your country needs lerts).
Remember: soft reset is the "touch" command, hard reset is the "restart" command. Try the soft one first. If it doesn't help, do the hard reset.
Can you see which pages were being requested?
from that we could deduce if this is due to the nLab being linked to elsewhere.
I need to dig down a bit, but it seems to have been a multiple request on the 'list' pages (list all pages, all authors, etc). What makes me a little suspicious is that the IPs don't resolve to hostnames.
If you're interested in what links to the n-lab then that's easy enough to find out. I believe that there's some way of making Google tell you that.
@ Urs
One should be able to get this sort of information out of the logs by looking at the Referer [sic] headings.
1 to 5 of 5