Got this fixed on my system by rename the original init script and then running the update/upgrade again.
Got this fixed on my system by rename the original init script and then running the update/upgrade again.