Comment 1 for bug 1644186

What this means is that you are not running mitaka code everywhere. At least one service was upgraded to newton (where version 15 was introduced), it updated its service record, and then may or may not have been downgraded back. At that point, if you stop all the mitaka services, you end up with the newest service in the deployment at 15, which may then start doing things assuming no version 9 services will ever come back, which is why the version 9 services refuse to start.

So, if I were you, I would try tweaking the service records (in the services table) back to version 9 and then start all your services again (ensuring they are all on mitaka) and hope for the best. That, or upgrade to newton.