When you start the probo-db service and there's no database connection, then it logs that it couldn't connect but then continues to run. However, it won't be able to consume data because that isn't started unless there's a db connection.
If the connection later begins to work (say postgres was done momentarily on startup) then it will seem as the probo-db is working becase the api calls will work but it still won't be consuming new data.
The probo-db service should simply fail if there's a db connection issue on startup. That way it will be known if it's not consuming data.