Same here, it started happening after upgrading from 5.5 to 5.6 and the DB migration had completed.
I had to reboot the appliance to resolve, twice now.
Same here, it started happening after upgrading from 5.5 to 5.6 and the DB migration had completed.
I had to reboot the appliance to resolve, twice now.