Without doing much pre-config installation on Nexus 3.13, on a new install, the install won’t start and throwing out errors during the “Apply upgrade” section. Here’s what I’m seeing:
2018-09-04 16:13:46,376+0000 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.upgrade.internal.UpgradeServiceImpl - Upgrade component from 1.9 to 1.10
2018-09-04 16:13:46,377+0000 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.upgrade.internal.UpgradeServiceImpl - Upgrade component from 1.10 to 1.11
2018-09-04 16:13:46,384+0000 ERROR [FelixStartLevel <query>select from repository where recipe_name in ['docker-hosted', 'docker-proxy']</query>] *SYSTEM com.orientechnologies.orient.core.storage.impl.local.paginated.OLocalPaginatedStorage - Exception `37EC5983` in storage `plocal:/opt/nexus/sonatype-work/nexus3/db/config`: 2.2.36 (build d3beb772c02098ceaea89779a7afd4b7305d3788, branch 2.2.x)
....
....
Caused by: com.orientechnologies.orient.core.exception.OCommandExecutionException: Class 'REPOSITORY' was not found in database 'config'
This is a new install. I’m assuming something occurred in the install process and created files in the /opt/nexus/sonatype-work/nexus3 directory then when I went to start nexus again things just didn’t play nice.
I removed the contents from /opt/nexus/sonatype-work/nexus3 and it worked.
Related
I am testing a deployment of dbt within Cloud composer. On my local machine (Ubuntu 20.04) I have got success in running the dbt models with airflow. When running on Google Cloud composer I get the following error
{subprocess.py:74} INFO - Output:
{subprocess.py:78} INFO - Running with dbt=0.21.0
{subprocess.py:78} INFO - Encountered an error while reading the project:
{subprocess.py:78} INFO - ERROR: Runtime Error
{subprocess.py:78} INFO - at path ['name']: 'jaffle_shop' does not match '^[^\\d\\W]\\w*$'
{subprocess.py:78} INFO -
{subprocess.py:78} INFO - Error encountered in /home/airflow/gcs/dags/dbt_project.yml
{subprocess.py:78} INFO - Encountered an error:
{subprocess.py:78} INFO - Runtime Error
{subprocess.py:78} INFO - Could not run dbt
{subprocess.py:82} INFO - Command exited with return code 2
{taskinstance.py:1503} ERROR - Task failed with exception
We are using a BashOperator to run dbt models in Airflow.
Initially had some problems with dependencies but they were solved.
Using a standard dbt_project.yml file with a single model just to test how this works.
Another way is to use Docker but we need try if this works.
Edit
Versions
dbt: 0.21.0
cloud-composer: 1.17.1
airflow: 2.1.2
Pypi Packages
airflow-dbt: 0.4.0
dbt: 0.21.0
jsonschema: 3.1 (Added this as Pypi was throwing an error about the version
I really appreciate if anyone can help
Pete
The problem here is the jsonschema dependency. Version 3.1.0 does not work, while versions 3.1.1 and 3.2.0 will work--and should also work within Composer's dependency requirements.
There looks to have been an issue with switching to js-regex for the jsonschema folks in 3.1.0, which caused them to revert back to regular re in 3.1.1.
There are some details here, and a couple of related issues described here and here.
In general, it would be much nicer if Cloud Composer supported virtual environments to avoid this entire dependency-collision mess, but apparently Google does not support that approach.
We are using Nexus3 - 3.23.0-03
while starting up our Nexus container it gives us below warning
“Removing .lock file
removed ‘/nexus-data/lock’
/sonatype/nexus/bin/nexus: 331: cd: can’t cd to …/jre/bin
2020-11-30 11:57:25,441+0100 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.pax.logging.NexusLogActivator - start
Nexus not started yet.”
but later nexus gets up & functional , we would like to know if its a bug/error/having less impact or its issue with Nexus startup scripts so that we can ignore this or consider this to be resolved,
Please suggest or advise. Thanks!
Regards,
SAMURAI
I've upgraded two instances of Artifactory to 6.9.0 version. One of them works without issue(OpenJDK 1.8.131 on centos 7.4), but I see error in the artifactory.log on another instance(OpenJDK version "1.8.0_151" on OEL 6.9):
2019-04-11 08:10:49,379 [art-exec-15] [ERROR] (o.a.s.a.ArchiveIndexerImpl:162) - Failed to index 'repository-name:com/service/service/0.14.2.1154/service-0.14.2.1154.jar': Unexpected record signature: 0X622F2123
I've tried to switch artifactory to Oracle JDK 1.8.0_121 and OpenJDK 11.0.2 - it didn't help.
p.s.
REST API and Artifactory GUI return artifacts without any issue.
The issue isn't reproduced on small jars without dependencies.
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.
My current version of Artifactory Pro 6.5.2. I can upgrade incrementally from 6.5.2 to 6.5.9 to 6.0.0. If I try to upgrade beyond 6.0.0, I receive a 404 error when attempting to access Artifactory.
HTTP Status 404 – Not Found
Type Status Report
Message /artifactory/webapp/
Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
Apache Tomcat/8.5.32
I see the following errors in /var/opt/jfrog/artifactory/logs/catalina/catalina.out
Failed to ensure db table 'master_key_status' exists
Error creating bean with name 'accessJdbcHelperImpl': Invocation of init method failed; nested exception is java.lang.IllegalStateException: Could not initialize database: Not supported
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/access]]
The database I'm using is MySQL
mysql Ver 15.1 Distrib 5.5.60-MariaDB, for Linux (x86_64) using readline 5.1
Has any encountered a similar issue when upgrading Artficatory Pro?
Thanks
Just marking down the answer.
The issue was with the JDBC driver version of the Maria DB.
One more update done by you was adding the timezone value.