I'm trying to upgrade the Nexus installation from 3.12.x to the latest 3.15.2, which would seem like an easy task.
I have followed the upgrade guide:
Updated the nexus.rc file
Updated the nexus.vmoptions file
To match the previous version.
However the nexus run command is giving me all kinds of Exceptions which is making this very difficult:
ERROR [FelixStartLevel] *SYSTEM org.sonatype.nexus.repository.manager.internal.RepositoryManagerImpl - Failed transition: NEW -> STARTED
java.lang.IllegalStateException: Missing recipe: apt-hosted
at com.google.common.base.Preconditions.checkState(Preconditions.java:585)
at org.sonatype.nexus.repository.manager.internal.RepositoryManagerImpl.recipe(RepositoryManagerImpl.java:155)
at org.sonatype.nexus.repository.manager.internal.RepositoryManagerImpl.newRepository(RepositoryManagerImpl.java:173)
at org.sonatype.nexus.repository.manager.internal.RepositoryManagerImpl.restoreRepositories(RepositoryManagerImpl.java:264)
at org.sonatype.nexus.repository.manager.internal.RepositoryManagerImpl.doStart(RepositoryManagerImpl.java:246)
at org.sonatype.nexus.common.stateguard.StateGuardLifecycleSupport.start(StateGuardLifecycleSupport.java:67)
at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
at org.sonatype.nexus.common.stateguard.StateGuard$TransitionImpl.run(StateGuard.java:193)
at org.sonatype.nexus.common.stateguard.TransitionsInterceptor.invoke(TransitionsInterceptor.java:56)
at org.sonatype.nexus.extender.NexusLifecycleManager.startComponent(NexusLifecycleManager.java:168)
at org.sonatype.nexus.extender.NexusLifecycleManager.to(NexusLifecycleManager.java:100)
at org.sonatype.nexus.extender.NexusContextListener.frameworkEvent(NexusContextListener.java:195)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1429)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
at java.lang.Thread.run(Thread.java:748)
The system is running CentOS, but i am not sure why it's trying to use apt.
Whenever i'm pointing the data-directory to a empty dir, nexus run will successfully complete and works as expected, but obviously all the users/repositories are lost.
Does anyone have an idea?
it looks like the plugin nexus-repository-apt isn't installed on your version. make sure to install https://github.com/sonatype-nexus-community/nexus-repository-apt. The steps to install this plugin are writen into the readme of the plugin.
I think after that then nexus will work again :)
Update 2019: Sonatype included apt repository type since Nexus release: 3.17.0
no manual installation of the plugin anymore. works out of the box.
Related
I have downloaded the fix pack from below URL.
https://www-945.ibm.com/support/fixcentral/swg/downloadFixes?parent=ibm%2FWebSphere%E2%88%8Fuct=ibm/WebSphere/WebSphere+Application+Server&release=All&platform=All&function=fixId&fixids=8.5.5-WS-WAS-FP013-part3,8.5.5-WS-WAS-FP013-part2,8.5.5-WS-WAS-FP013-part1%E2%88%88cludeRequisites=1%E2%88%88cludeSupersedes=0&downloadMethod=http&login=true
Upgrade Version - From WebSphere 8.5.5.0 to 8.5.5.13
While running the imcl command i have faced below error. Can someone please suggest what could cause this isssue?
# ./imcl install com.ibm.websphere.BASE.v85_8.5.5013.20180112_1418 -repositories /data/repo/repository.config -installationDirectory /appl/IBM/WebSphere/AppServer/ -acceptLicense -showProgress
25% 50% 75% 100%
------------------|------------------|------------------|------------------|
............................................................................
ERROR: Failed to find required installation files.
CRIMA1161E ERROR: Failed to find required installation files.
Explanation: Installation Manager did not find required installation files from the repository. An issue has occurred with the package that cannot be resolved by Installation Manager.
User Action: If the repository files were transferred from a different location before the installation, verify that the files were not altered during the transfer operation. Copy the repository files to a different location and install from that location. If the repository files were not transferred note the package name and version number and contact customer support.
ERROR: 'plug-in com.ibm.was.detect.offering.update.v85_8.5.0.20120308_0100' not found in /data/repo.
ERROR: 'plug-in com.ibm.was.detect.backlevel.jdk.ifix_8.0.2.20120308_0004' not found in /data/repo.
ERROR: 'plug-in com.ibm.was.determine.job.type_8.5.0.20120326_1010' not found in /data/repo.
Looks like you have old repositories enabled in Installation Manager preferences, for which the installation files are missing.
Try below steps to resolve this issue:
If you can enable GUI, Open IM, go to File > preferences >
Repositories. Do a test connection for all enabled repositories and
uncheck/disable repositories that are not working/you no longer
read.
If you cannot enable GUI, there are 2 options
Modify com.ibm.cic.agent.core.prefs file in order to enable/disable repositories (default location in linux:
/var/ibm/InstallationManager/.settings/com.ibm.cic.agent.core.prefs)
Enable/Disable repositories using 'imcl -c' command line https://www.ibm.com/support/knowledgecenter/SSDV2W_1.8.5/com.ibm.cic.agent.console.doc/topics/t_console_pref_repository.html#remove_rep
Once old repositories for which installation files are missing are disabled, try installing the fixpack again.
I have connected my Android application with firebase-database by putting this dependency (kapt 'com.google.firebase:firebase-database:16.0.1:15.0.0') but after that I am getting errors like the one mentioned in title also when I synchronized the project I am getting different errors like: Connection time out, Failed to resolved build listener.
Enabling/Disabling offline work and setting proxy in gradle.properties file doesn't work for me.
Also you guys have seen that I used 'kapt' in dependency as it is necessary to use, without it I am getting error "failed to resolve 15.0.0". Removing 15.0.0 doesn't work for me.
Error
Cause:org.jetbrains.plugins.gradle.tooling.util.ModuleComponentIdentifierImpl.getModuleIdentifier()Lorg/gradle/api/artifacts/ModuleIdentifier;ing
I am using Android Studio 3.2 and sadly I can't update this version.
Gradle version: 5.1.1 and
Plugin version: 3.4.0
With no changes at all to source code or pipelines, I am now experiencing an issue where none of my build pipelines work anymore in Azure DevOps. The package that is being referenced isn't a dependency for this project, nor has it ever been. I can't work out what's causing this or how I can go about troubleshooting.
2018-11-26T10:25:14.2812751Z Restoring packages for C:\Agent\_work\19\s\OrchestrateIT.Web\OrchestrateIT.csproj...
2018-11-26T10:25:14.7577515Z C:\Program Files\dotnet\sdk\2.1.400\NuGet.targets(114,5): error : Unable to load the service index for source https://orchestrate-it.pkgs.visualstudio.com/_packaging/Shared_DBUpdate/nuget/v3/index.json. [C:\Agent\_work\19\s\OrchestrateIT.DataImportScheduler\OrchestrateIT.DataImportScheduler.csproj]
2018-11-26T10:25:14.7577910Z C:\Program Files\dotnet\sdk\2.1.400\NuGet.targets(114,5): error : Response status code does not indicate success: 401 (Unauthorized). [C:\Agent\_work\19\s\OrchestrateIT.DataImportScheduler\OrchestrateIT.DataImportScheduler.csproj]
2018-11-26T10:25:14.7579439Z 0 Warning(s)
2018-11-26T10:25:14.7579628Z 1 Error(s)
2018-11-26T10:25:14.7579743Z
2018-11-26T10:25:14.7579902Z Time Elapsed 00:00:02.18
2018-11-26T10:25:14.7906687Z ##[error]Error: C:\Program Files\dotnet\dotnet.exe failed with return code: 1
Local (manual) build works fine. I have already tried clearing Nuget cache and VSTS agent cache. A quick workaround might be to solve the authorisation issue (even though the package isn't required) however I'm not sure how to go about doing this.
Any advice would be greatly appreciated.
Even though my Personal Access Token had not expired, for some reason I needed to remove and add this package back to my sources with the same PAT. This resolved the authentication issue and therefore resolved the build issue.
It is still unclear to me as to why this package is being considered as a dependency for this project though.
getting the below error while installing spring IDE from eclipse market place
An error occurred while collecting items to be installed
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Unable to read repository at http: //dist.springsource.com/release/TOOLS/update/3.8.4.RELEASE/e4.5/features/org.springframework.ide.eclipse.aop.feature_3.8.4.201703310634-RELEASE.jar.
Read timed out
Unable to read repository at http: //dist.springsource.com/release/TOOLS/update/3.8.4.RELEASE/e4.5/plugins/org.springframework.ide.eclipse.config.graph_3.8.4.201703310634-RELEASE.jar.
Read timed out
Unable to read repository at http ://dist.springsource.com/release/TOOLS/update/3.8.4.RELEASE/e4.5/features/org.springframework.ide.eclipse.roo.feature_3.8.4.201703310634-RELEASE.jar.
Read timed out
Unable to read repository at http: //dist.springsource.com/release/TOOLS/update/3.8.4.RELEASE/e4.5/plugins/org.springframework.ide.eclipse.webflow.core_3.8.4.201703310634-RELEASE.jar.
Read timed out
Check for Eclipse updates at first
Goto Windows-> peferences -> Install/Update -> Available software Sites,update "http://download.springsource.com" instead of "http://dist.springsource.com". restart Eclipse, and add it back.
And select help>install new software>contact all update sites (check)
I did this for Eclipse Mars version
I am using the Eclipse Oxygen Release (4.7.0) and I followed the solution suggested by #Vasath.
In the list of Available software sites, I edited "SpringSource Update Site for Eclipse 4.7" by replacing
http://download.springsource.com/release/TOOLS/update/e4.7 with
http://dist.springsource.com/release/TOOLS/update/e4.7.
It worked, Spring IDE is installed and working fine.
Karaf 2.2.3 recently released and finally has a pre-bundled spring-jms feature. In order to make life easy I added it to the featuresBoot config property with the other defaults:
featuresBoot=config,ssh,management,spring-jms
However, when I start Karaf it behaves uncontrollably. Sometimes it will install on boot and other times it doesn't. When it doesn't auto-install I attempt to add it via the command line:
features:install spring-jms
And even that behaves wildly. See below:
karaf#root> features:install spring-jms
Error executing command: java.lang.IllegalArgumentException
karaf#root> features:install spring-jms
Error executing command: invalid entry size (expected 3293 but got 16823 bytes)
karaf#root> features:install spring-jms
Error executing command: Manifest not present in the first entry of the zip mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aopalliance/1.0_5
karaf#root> features:install spring-jms
Refreshing bundles org.springframework.context.support (50)
Error executing command: Could not start bundle mvn:org.eclipse.jetty/jetty-client/7.4.5.v20110725 in feature(s) jetty-7.4.5.v20110725: Unresolved constraint in bundle org.eclipse.jetty.client [83]: Unable to resolve 83.0: missing requirement [83.0] package; (&(package=org.eclipse.jetty.http)(version>=7.4.0)(!(version>=8.0.0)))
karaf#root> features:install spring-jms
Refreshing bundles org.springframework.context.support (50)
Those are back-to-back executions of the install command. The last execution works.
Anyone else see this behavior? Or know how to correct it?
Tony,
First, make sure that you are using the correct version Java, I use jdk 1.6_24. When using this, with no other bundles installed (a fresh installation), it installs properly. If I were you I would:
1) try installing a fresh instance of Karaf,
2) copy your maven repository to a new location, and
3) run Karaf in a fresh installation,
4) install spring-jms again.
If that doesn't work, reply to this and let me know your environment, along with all of the exceptions generated in your karaf log file.
By any chance are you using a customized org.ops4j.pax.url.mvn.cfg? I am, and it has caused a huge boot-time race condition problem that led to features sporadically failing to load.
Take a look at https://issues.apache.org/jira/browse/KARAF-910 "Race between FeatureService and ConfigAdmin for resolving mvn: URLs?"