Trying to upgrade Nexus 2.1.4 Repo to 3.X. This is what i have done till now and what what went wrong!
-- installed the 3.0.2 version on the same machine in a different port (8090) Then opened the UI and tried doing the upgrade agent and there was no upgrade agent in 3.0.2.
-- so i installed 3.1 on the different port and came across a java exception error in nexus Repo UI while migrating stuff from 2.1.4 (installed on port 80). I found out that one need to be at-least on 3.2.4 V to migrate.
-- now i installed 3.6 on a different port (8082)in the same machine. couldn't start nexus service now. which i was able to for other nexus version in other ports.
Related
Trustwave PCI (Payment Card Industry) compliance has just failed with 'The remote host is running a version of nginx that is no longer supported'. I am running the latest LTS version of ubuntu server 18.04 with the latest version of nginx 1.14.2.
I have looked on line, but I cant find a list of which versions of nginx are still supported/unsupported. I would like to find either a way to determine if 1.14.2 is supported, or an authoritative list to dispute the finding.
Thanks to #lex-li, everything listed under "legacy" is unsupported here, though I thought nginx 1.14.2 was the latest because using the ppa for a stable version of nginx, apt install was telling me that it was the latest version. Recently nginx must have changed their install so that if you want to upgrade past 1.14, you need to uninstall nginx, then follow the instructions here
I have installed Nexus on Ubuntu 18.04 LTS. When I want to start Nexus service I get this error:
nexus[24049]: No suitable Java Virtual Machine could be found on your system.
nexus[24049]: The version of the JVM must be at least 1.8 and at most 1.8.
nexus[24049]: Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.
systemd[1]: nexus.service: Control process exited, code=exited status=83
systemd[1]: nexus.service: Failed with result 'exit-code'.
systemd[1]: Failed to start LSB: nexus.
I have Open JDK version 10.0.2 installed in my system:
openjdk version "10.0.2" 2018-07-17
OpenJDK Runtime Environment (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.4)
OpenJDK 64-Bit Server VM (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.4, mixed mode)
My question is why Nexus uses ONLY JDK8? and am I able to have both JDK versions alongside?
INSTALL4J_JAVA_HOME is not an environment variable setting. It is configured in the nexus installation directory. You'll need to edit "/bin/nexus" file.
You'll find near the top of that configuration script a commented out line:
# INSTALL4J_JAVA_HOME_OVERRIDE=
remove the comment tag and set the value to your jdk location. I set mine to a java 1.8 jdk that I installed. (Not the JDK 11.0.4 default dir that some linux installations are prepackaged with. I read somewhere that you must use the Java 1.8 with nexus version 3.x and that other versions will fail. I don't know the truth to that claim, you certainly can try other version to see if they work.)
After doing that, the nexus service was able to start.
I still haven't been able to get access to the nexus manager through a browser via port 8082. I'm just now trying to track that issue down. Probably a configuration issue or something else I need to set up.
Does the version of Node.js on my development machine / integrated development environment (IDE) machine have any effect on my ability to upgrade my Firebase Cloud Functions Node.js runtime to version 8?
I finally got my functions Node.js runtime upgraded to v8 but I had a difficult time doing it. I eventually installed node version manager, nvm, to nail my development machines Node version to 8.0.0 but then ran into the 8.0.0 issue w/ firebase-tools. "must use 8.1.0. 8.0.0 fails"
nvm install v8.1.0
nvm alias default 8.1.0
So, running Node.js v8.1.0 on my development machine seemed to be the breakthrough. I'd like to know but don'e have time to spend on recreating it all.
I'm trying to install Spark2 in my cloudera cluster (evaluation version) following the cloudera's instructions to install this component. I downloaded the CSD, installed it and using the parcel downloaded the component, distribute it but when I try to activate it I'm having this message:
CDH (5.8 and higher) parcel required for SPARK2
(2.2.0.cloudera1-1.cdh5.12.0.p0.142354) is not available.
This is the information of the cluster:
Version: Cloudera Enterprise Data Hub Edition Trial 5.12.1 (#6 built
by jenkins on 20170818-0807 git:
9bdee611802535491d400e03c98ef694a2c77d0a)
Java VM Name: Java HotSpot(TM) 64-Bit Server VM
Java VM Vendor: Oracle Corporation
Java Version: 1.7.0_67
CSD
SPARK2_ON_YARN-2.2.0.cloudera1.jar
Parcel
http://archive.cloudera.com/spark2/parcels/2.2.0.cloudera1/
I'm thinking it could be because my CDH version (5.12.1) and the version of the last spark2 parcel (cdh5.12.0) but I don't find any other package for cdh5.12.1 and my next question is: for cdh5.13.0 which is the spark2 parcel?
The error message is misleading. The real issue is that your cluster is running on Java 1.7. Spark 2.2 is only supported on Java 1.8. Upgrade Java on your cluster and you should be able to install the Spark 2.2 parcel.
Finally solved. The problem was that I need to update de cdh core, after update, spark 2 just works fine.
I've just discovered that all the install guides for railo+resin assume you're installing the obsolete 3.1.2 bundle (railo-3.1.0.012-resin-3.1.2-without-jre.zip). I have Resin 4 installed now, what is the process for deploying the Railo WAR / JAR's (under linux)?
Should be nearly identical to setting up Railo on Resin 3.1. Have you tried it?
http://www.getrailo.org/index.cfm/documentation/installation/railo-resin-apache/