Arvados

When something goes wrong installing and starting services within arvbox (for example after running `arvbox reboot dev` or `arvbox reboot test`), arvbox makes no indication that there is a problem, it just keeps retrying the service repeatedly forever.

The result as a user is that it is very hard to tell the difference between arvbox taking a long time and arvbox being hopelessly stuck.

I suggest some retry counting on services, such that they can only fail consecutively n times (perhaps 3) before arvbox gives up and stops trying altogether.