-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 3.24.0
-
Fix Version/s: None
-
Component/s: Bootstrap
-
Labels:
-
Notability:3
When the "-Dinstall4j.pidDir=/var/run/nexus" property is added inside the "$install-dir/bin/nexus.vmoptions" then the "./nexus status" command does not function properly.
Following steps can be used to reproduce the issue locally.
1. Setup nexus "nexus-3.24.0-02" to run as service (as 'nexus' user). As mentioned in https://help.sonatype.com/repomanager3/installation/run-as-a-service
2. Verify everything works fine. So far all good.
# service nexus start # service nexus status # service nexus stop
3. Now as per the documentation try to define the "-Dinstall4j.pidDir=/var/run/nexus" property inside the $install-dir/bin/nexus.vmoptions
4. Create respective directory with correct permissions.
# mkdir -p /var/run/nexus # chown -R nexus:nexus /var/run/nexus
5. Now the 'status' command does not work properly (also the service stop command also does not work properly)
# service nexus start # service nexus status Last login: Mon Jul 6 09:50:26 AEST 2020 on pts/2 nexus is stopped. # ./nexus-3.24.0-02/bin/nexus status Last login: Mon Jul 6 10:13:57 AEST 2020 on pts/2 nexus is stopped.
Although the nexus process is Up and running also the UI is also accessible.
Workaround:
Try removing the "-Dinstall4j.pidDir=/var/run/nexus" property inside the "$install-dir/bin/nexus.vmoptions " and then restart the nxrm3 process and validate again.
- duplicates
-
NEXUS-23309 The "stop" and "status" commands in the nexus startup script do not pass in nexus.vmoptions arguments
-
- New
-