Community
Participate
Working Groups
Hi, I've reported this a couple of times before and the issue is still not solved. Please, could you look into it again? I have a multi-user installation, so my plugins are installed in a shared (read-only!!!!) location (bundle-pool) and are managed in so called profiles; I use p2 agent for installation and not the self hosted p2 update mechanism! The latest helios maintenance release still gives me that error when I "Test Connection" (on-demand IAC activation is enabled) from the preferecnce page. IWAT0284E The Agent Controller is not available on host localhost. Make sure that: * for localhost, the Internal Agent Controller is supported on your local platform. * the Agent Controller is installed. * the Agent Controller is configured to communicate with your machine. * you have the correct host name and port number for the Agent Controller. See the workspace Error Log or Agent Controller serviceconfig.log for any additional information. org.eclipse.hyades.internal.execution.local.control.AgentControllerUnavailableException So after that I was walking into the plugin folder and down to where the agent controller had actually been installed and tried to execute the AC which led to an error saying the AC was not configured. Ok, so I configured it (as root) and then tried to execute it as normal user which finally succeeded - hurrah. However, the point still is that the IAC does not work in a multi-user environment !!! As it seems, the IAC is not using a user specific configuration. Have I provided enough information? bye Mich;
Hi, Can you please provide more details about how you complete the p2 agent installation? Are you setting the org.eclipse.update.install.feature property? Thanks
Hi Joel, yes that property is set true, however it's defined in configuration/config.ini rather than installation.ini as you said in Bug 242621 #18. Does this make a difference? bye Mich;
Hi Mich, Using this option in the installer.properties allowed for it to install the features which help resolve the installed plug-ins. This may still cause the issue described in bug 311387.
Hi Joel, what I wanted to say is that I have set this property in the configuration file config.ini of the p2 agent. Although set, it's still not working for me :-( (In reply to comment #3) > Hi Mich, > > Using this option in the installer.properties allowed for it to install the > features which help resolve the installed plug-ins. This may still cause the > issue described in bug 311387.
Hi Mich, The option needs to be set in the installer.properties used with the p2 installer before installing your shared install instead of the p2 agent. Can you please provide the steps you use to complete your installation? This will help with reproducing the problem. Thanks
Created attachment 179439 [details] my p2 agent configuration file
Hi Joel, I'm not using the p2 installer but rather the p2 agent. I think the main difference is that the latter simply has a UI. In the p2 agent application I define profiles with the profile location somewhere in /usr/local/.... and a common bundle pool in a different location somewhere in /var/..... Both locations are readonly for normal users. The user I run the p2 agent has write permission in the affore-mentioned folders.
Hi Joel, I just thought about the problem again and I think we're on the wrong track here. I'd say the installation in its own right is fine. As I said earlier, when I start the AC from command line (after manual configuration that is) the agent works nicely, even as user without write permission. So, the AC installation is correct. Now, the problem in my eyes is, that the IAC mechanism should recognize that the "central" AC is in a readonly location and thus decide to create its own configuration (according to the settings in the preference page) in a user or workspace specific location. IMHO, this raises the question how the AC is launched rather than installed ... right? bye Mich;
Hi, Sorry, I was confusing the p2 installer and p2 agent. The IAC stores the configuration in the workspace. You can verify the configuration file, serviceconfig.xml, is generated in workspace/.metadata/.plugins/org.eclipse.tptp.platform.iac.administrator/config. When the IAC launches it will use this configuration. I am unsure of what to unzip/install into the install folder and bundle pool folder. Can you please suggest what I should install so that I can setup a similar configuration? Thanks
Created attachment 179712 [details] iac configuration from [workspace]/.metadata/...
(In reply to comment #9) > Hi, > > Sorry, I was confusing the p2 installer and p2 agent. > > The IAC stores the configuration in the workspace. You can verify the > configuration file, serviceconfig.xml, is generated in > workspace/.metadata/.plugins/org.eclipse.tptp.platform.iac.administrator/config. > When the IAC launches it will use this configuration. the file is there, I just verified (see attachment) > > I am unsure of what to unzip/install into the install folder and bundle pool > folder. Can you please suggest what I should install so that I can setup a > similar configuration? First install for instance org.eclipse.platform.ide (this gives you a basic runtime) In the second run you can install multiple bundles at once, but for the iac it should suffice to just pull in org.eclipse.tptp.trace.runtime.feature.group > > Thanks
Using a Windows system I completed the following install, which I believe should be similar to your configuration. 1. Download and extract the p2 installer and p2 agent, e.g. C:\installer, C:\agent. 2. Modify the p2 installer.properties with the following properties: eclipse.p2.rootId=org.eclipse.platform.ide eclipse.p2.installLocation=<point to an install folder, e.g. C:\install> eclipse.p2.agentLocation=<point to the agent install location, e.g. C:\agent> eclipse.p2.bundleLocation=<point to bundle pool install location, e.g. C:\bundle_pool> org.eclipse.update.install.features=true 3. Verified that the bundle pool contains the features and plugins directories, and there are no features/plugins in the install folder. 4. Using Help -> Install New Software, install TPTP Trace Runtime from the Helios update site and restart the workbench. Verified the features/plugins are installed in the bundle pool location. 5. Open the Profile Launch Configuration and click Test Connection. An Agent Controller unavailable exception is displayed similar to what is described in the bug description. In the Window -> Show Views menu, open the error log and received two error messages ("IAC could not be started due to invalid configuration file." and "Execution framework configuration file is invalid. This could be caused by the execution plugin checked out in your workspace." Using an Eclipse Runtime launch workbench to start a Profiling session does not have an error. I installed a debug plug-in into the bundle pool workbench to check if there are plug-ins to configure but there were no plug-ins returned for configuration (I believe this would be the same as bug 311387). Does this setup seem similar to your configuration? Do you receive the same errors in the error log?
(In reply to comment #12) > Using a Windows system I completed the following install, which I believe should > be similar to your configuration. > > 1. Download and extract the p2 installer and p2 agent, e.g. C:\installer, > C:\agent. > 2. Modify the p2 installer.properties with the following properties: > eclipse.p2.rootId=org.eclipse.platform.ide > eclipse.p2.installLocation=<point to an install folder, e.g. C:\install> > eclipse.p2.agentLocation=<point to the agent install location, e.g. C:\agent> > eclipse.p2.bundleLocation=<point to bundle pool install location, e.g. > C:\bundle_pool> > org.eclipse.update.install.features=true > 3. Verified that the bundle pool contains the features and plugins directories, > and there are no features/plugins in the install folder. > 4. Using Help -> Install New Software, install TPTP Trace Runtime from the > Helios update site and restart the workbench. Verified the features/plugins are > installed in the bundle pool location. > 5. Open the Profile Launch Configuration and click Test Connection. An Agent > Controller unavailable exception is displayed similar to what is described in > the bug description. In the Window -> Show Views menu, open the error log and > received two error messages ("IAC could not be started due to invalid > configuration file." and "Execution framework configuration file is invalid. > This could be caused by the execution plugin checked out in your workspace." > > Using an Eclipse Runtime launch workbench to start a Profiling session does not > have an error. > > I installed a debug plug-in into the bundle pool workbench to check if there are > plug-ins to configure but there were no plug-ins returned for configuration (I > believe this would be the same as bug 311387). > > Does this setup seem similar to your configuration? Do you receive the same > errors in the error log? Hi Joel, I haven't used the p2 installer but it looks like the result is the same. The error messages also seem to be what I get when testing the connection. Unfortunately, I don't understand the rest of your message :-(
Since you are getting the same errors reported as my configuration, this could be caused by bug 311387. Could you please respond to John's posting in bug 311387 comment 2? Thanks
In comment 12, the steps explain how to reproduce the problem and the possible connection to the installation scenario. Were you able to resolve the issue? Do you have an update to provide on bug 311387?
(In reply to comment #15) > In comment 12, the steps explain how to reproduce the problem and the possible > connection to the installation scenario. > > Were you able to resolve the issue? Do you have an update to provide on bug > 311387? First question, no! Second, I don't know what I should tell them at bug 311387. I haven't been pursuing the issue any further, because I have since given up on TPTP Trace.
You can add information in bug 311387 about the reason for using bundle pools instead of the p2 installation method. The standalone Agent Controller could be used as an alternative.
This appears to be a result of the bundles not being provided for configuration when installing using bundle pools. *** This bug has been marked as a duplicate of bug 311387 ***
(In reply to comment #18) > This appears to be a result of the bundles not being provided for configuration > when installing using bundle pools. > > *** This bug has been marked as a duplicate of bug 311387 *** Funny, how can this bug be a duplicate of another resolved bug, but the error still exists? Even with the latest maintenance build from http://download.eclipse.org/releases/maintenance it still exists - for the case that I have a read-only plugin installation path (shared installation).
I have re-opened bug 311387 for the bundles not being returned. If the problem persists when the bundles are returned by p2, this bug could be used for any TPTP specific changes. *** This bug has been marked as a duplicate of bug 311387 ***
