I think this was caused by the migration not being performed on a ZenJMX upgrade. ZenJMX was rewritten in the 2.3 release and if you do not properly upgrade it (ie. running 'zenoss restart' instead of 'zenoss start' after the upgrade (yes there's a bug)), there may be an issue with the migration script for the ZenJMX upgrade.
Thanks, Matt Ray Zenoss Community Manager community.zenoss.com [email protected] _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
