Installing Nexus OSS using the standard Jetty based server distribution bundle is a Sonatype recommended best practice.
General instructions for installing Nexus OSS as a stand-alone server are in the Nexus Book.
Running Nexus OSS WAR file in another application server or servlet container is not recommended.
Troubleshooting
Several of you have reported issues starting Nexus on Debian or Ubuntu when running under gij. If you see a IOException: Stream Closed during startup, check your JVM or JRE and read this article for the fix.
If Nexus is attempting to bind to a port that is already taken by another process, you will need to change the host or port that Nexus attempts to bind to. To do this read this article.
5 Comments
The location of the sonatype-work directory can be customized by altering the nexus-work property in $NEXUS_HOME/conf/plexus.properties
Shouldn't it be $NEXUS_HOME/conf/plexus.properties? There is also $NEXUS_HOME/nexus/WEB-INF/plexus.properties with the nexus-work property, should it be ignored?
Oops, I meant shouldn't it be $NEXUS_HOME/conf/nexus.properties?
How do you make the install not look like a "trial" anymore. For instance in nexus.properties we have nexus.bundle.type=trial. Also at startup we see "Running Nexus Professional Trial" at startup. Is there a non-trial install or do we have to spelunk around to make it look like a non-trial version?
Regards,
Ron
Centos 6.3 set the JAVA_HOME(JDK-1.6) correctly.
when i startup with: /etc/init.d/nexus console
error hanppen: [see the attacked log file]
but i can log in. it works. but when i browse storage. i got a server error alert.
We are closing this article for comments.
If you have a support license, please contact us by submitting a support ticket.
If you do not have a support license, please use our Nexus Users List or our other free support resources.