I finally solved the issue by traking the taskID 30170 in the ambari DB. I found that there is an inconsistancy due to the DB crash. The tables "execution_command" and "host_role_command" were those containing the reference to this taskID while the table "task" has no reference to it. These twotables were those i repaired after the DB crashed. After cleaning up these tables i was able to restart all services. But to avoid any other related problem that could occur later, i restored an older ambari DB as @Artem Ervits suggested. Now all services are running fine. Thank you all for your help.
... View more
