On an Ubuntu 4.6.3 setup using Gerrit 2.6.1, I successfully installed the its-base plugin. However, when I tried deploying the its-jira plugin version 2.13 via SSH, a PluginStallException occurred. The error details weren’t accessible due to internal restrictions, and I haven’t found any similar reports. Any guidance or troubleshooting tips would be greatly appreciated.
I encountered a similar issue when trying to install a plugin on an older Gerrit setup. What worked for me was revisiting the installation logs and ensuring that every configuration step was performed as required. Sometimes, the PluginStallException hides an underlying conflict between the plugin and Gerrit’s version; in my case, double-checking the versions and ensuring compatibility helped resolve the unexpected stalling. In addition, I found that cleaning any temporary files or caches before reinstalling the plugin contributed to a smooth installation process.
hey i got a simlar issue earlier. check if your plugin and gerrit version are matching; sometimes its just a config mixup. re-setting those helped me a lot. hope u fix it quickly
After encountering a similar problem, I found that an examination of both the plugin documentation and the system logs helped me uncover underlying issues that weren’t immediately obvious. In my experience, the PluginStallException in environments like this can sometimes be traced to mismatches between library dependencies or legacy configuration settings lingering from previous installs. A systematic check of the operating system’s library versions and ensuring that all environmental variables were correctly set proved beneficial. This thorough device-level review enabled me to pinpoint and resolve compatibility conflicts effectively.
When I ran across a PluginStallException, it turned out that the root cause wasn’t immediately apparent. For me, the troubleshooting process revealed that not only was there a subtle incompatibility between certain library versions, but an update to the JVM on the system was clashing with Gerrit’s handling of plugins. I eventually found that aligning all environment-specific parameters—such as system libraries and runtime aspects—helped mitigate the conflict. Revisiting internal configurations and ensuring consistent dependencies was key to resolving the issue.