Don’t whack a dead horse.

[matcornic]

A lot of errors when setting the refresh parameter of a connector to 1s.

[INTOOLS] [DEBUG] 2015/12/02 15:07:38 utils.go:48: no such id: 4cb814b0193274334090a856bad1f04c9ad433aa5664a01768e0c587162bd27d
[INTOOLS] [WARN]  2015/12/02 15:07:38 connectors.service.go:154: Unable to parse stdout from container 4cb814b0193
[INTOOLS] [WARN]  2015/12/02 15:07:38 connectors.service.go:155: invalid character 'o' in literal null (expecting 'u')
[INTOOLS] [DEBUG] 2015/12/02 15:07:38 utils.go:48: no such id: 4cb814b0193274334090a856bad1f04c9ad433aa5664a01768e0c587162bd27d
...
[INTOOLS] [ERROR] 2015/12/02 15:07:39 connectors.service.go:96: Cannot inpect container 9bdf3002cd8
[INTOOLS] [ERROR] 2015/12/02 15:07:39 connectors.service.go:97: no such id: 9bdf3002cd8a7c47cd747285489c4027871439f63fe24ebc6244f78dd8144a59
...
[INTOOLS] [ERROR] 2015/12/02 15:07:41 connectors.service.go:81: Cannot start container 56716c8520d
[INTOOLS] [ERROR] 2015/12/02 15:07:41 connectors.service.go:82: 500 Internal Server Error: Cannot start container 56716c8520d2d4a1afc0361114e080518b634a83e5ee812332de1b54775be756: Container is marked for removal and cannot be started.

Apparently, for the same connector, when a container is launched while another is already running, result fails.
One solution could be launching a new container only when no container is running on the same connector.