akoopal asked if this is something that can be monitored by bigbrother. can it?

is this something that is part of T90569 then?

The webservice itself is monitored via the .bigbrotherrc, but it looks to be only looking for the proces. If the webservice is running but unresponsive it doesn't seem to be detected.

That is correct, bigbrother checks that the job is running (and therefore the process is alive), but doesn't know what it is supposed to be doing and cannot check that.

< akoopal> hi, getting timeouts again on erwin85's tools
< akoopal> in the log I see:
< akoopal> 2015-03-05 17:05:40: (server.c.1352) [note] sockets enabled again
< akoopal> 2015-03-05 17:05:40: (server.c.1398) [note] sockets disabled, connection limit reached

@Erwin you are the Erwin of erwin85's tools, right? The Mediawiki user page seemed to confirm that. Added you here.

This almost unfailingly happens when the average time it takes to answer a request gets long enough that average hit rates fill up the default number of allowed connections for a tool. If you determine that the requests are unavoidably long, we can increase that limit as the traffic justifies.

All tools are tools that do some larger queries, but as far as I can see, only order of couple of seconds, not more. I have not gone over all queries to see if they can be more efficient, but knowing Erwin that has been looked at. So if we can (again) tune up this tool, would be appreciated, also by the users of the tools.

I'll be looking at the tool's log to determine the actual load and increase the limit to cover it with some elbow room.

Well, it was just down for 2 days until I restarted it (warned by supernino on IRC).