Mikhail Korobov

Yeah. Even worse, even if you kill them and restart manually they are not picked up by haproxy because haproxy docker container doesn't detect new ip addresses of linked containers;...

Are you thinking about a builtin watchdog process?

There is 'timeout' feature, but it works only if rendering yields to the event loop, which is not the case when we hit some qt bug.

It could be tricky because we're running several QWebViews in a same event loop => all concurrent renders happen in a single thread; there may be some tasks launched by...

So, a watchdog process? Also, it seems these checks can be implemented in haproxy itself (it can run external scripts), but I haven't checked the details.

@Glennvd no updates, sorry.

Also, there are tokens like ``

What is your docker-compose version?

I think docker-compose version is a problem: aquarium uses a more recent docker-compose.yml file format introduced in docker-compose 1.6 (see https://github.com/docker/compose/blob/master/CHANGELOG.md#160-2016-01-15). We should document minimum version though. Upgrading docker-compose should...

Try enabling DEBUG log level in Scrapy, it may give additional information.