Plugin container is writing data in wrong directory. These are files getting written to ${current working directory}/data, but if the PC was told to use a different data directory, that configuration is ignored. This is what I see: data/ |_rc/ |_10/ |_10125 |_10122 |_10111 This was a result of the agent perf stuff. We can't just say "data" with a relative path in the PC - the data directory is configurable. You have to get the data directory as configured in the plugin container. Somehow, this code in ConfigurationCheckExecutor (see below) has to get PluginContainerConfiguration.getDataDirectory() - the InventoryManager has this plugin configuration (as do all the PC managers), so somehow they need to get that data dir into here: --------- public static boolean persistConfigurationToFile(int resourceId, Configuration liveConfiguration, Log log) { boolean success = true; try { String pathname = "data/rc/" + String.valueOf(resourceId/1000); // Don't put too many files into one data dir File dataDir = new File(pathname); ... static private Configuration loadConfigurationFromFile(int resourceId) { String pathname = "data/rc/" + String.valueOf(resourceId/1000); // Don't put too many files into one data dir File dataDir = new File(pathname); ...
master commit ea1f3b883340dd4db2724f01e80484a497c4f048 Author: Jay Shaughnessy <jshaughn> Date: Mon Feb 3 12:29:48 2014 -0500 Change things around to us the proper data directory, as configured for the plugin container (via InventoryManager) Test Notes: Nothing to test here, as long as unit tests are passing and people no longer complain about the data directories showing up then all is good.
Bulk closing of 4.10 issues. If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.