Nexus silently fails to start

the PID file appears for 2-3 seconds before it vanishes, no logs are added to nexus.log

I’ve tried running as nexus user & as root, i’ve verified all files are owned by nexus and even set permissions to 775

This VM is a DR clone of a working nexus installation

journalctl xe shows: nexus.service: main process existed, code=exited, status=255/n/a

are you invoking this manually ie running the command to start nexus? Or are you running it through the service startup script? If its not generating anything at all in the logs then its dying super early in the launch process indicating perhaps a missing dependency or a seriously egregious configuration error.

If you are launching it by manually invoking you should get some sort of error output. Can you try this and paste the results for analysis?

1 Like