Landscape client failing due to it's own locks

Looks like while the package reporter is listing the packages, the package changer fails to run due to a lock.

It never recovers, and is left dangling in the Landscape server. Been 2 hours and nothing happens.

Any ideas?

image

image

After much troubleshooting I understood that the packages were still syncing from the machine being registered, and this takes quite a bit of time, resulting in the conflict.