Can't start nexus as non-root user

350 views
Skip to first unread message

Kaliyug Antagonist

unread,
Mar 20, 2018, 10:03:41 AM3/20/18
to Nexus Users
nexus-3.9.0-01 on RHEL 7.

I simply unzipped the tar file and started nexus as root. It worked as expected, the log showed that nexus was started.

Now, I have a user 'nexus':
[nexus@l5109p nexus-3.9.0-01]$ id
uid
=40061(nexus) gid=40061(nexus) groups=40061(nexus) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023


When I try to start nexus using this user, it doesn't start. I cannot view any errors in log as the log is not simply updated.

How shall I proceed?

Note: On another machine, I had been running nexus as root. Yesterday, I simply changed the ownership of the directories to the nexus user. Nexus now runs as it's own user on that machine, without any issues. Taking guarantees from this, I decided to start with nexus user itself on the new machine(l5109p) but now nexus doesn't start at all with it's own user.

Brian Fox

unread,
Mar 20, 2018, 10:05:33 AM3/20/18
to Kaliyug Antagonist, Nexus Users
You need to figure out what permission is blocking it. Did you change the file ownership recursively along with the directory? Is it trying to open a port that isn't allowed by non-root on this machine?

--
You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users+unsubscribe@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.
To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/aca2aa11-f093-4bde-93a5-57dd7ea25b3d%40glists.sonatype.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.

Rich Seddon

unread,
Mar 20, 2018, 10:16:18 AM3/20/18
to Nexus Users, kaliyuga...@gmail.com
Yes, make sure the "nexus" user is the owner of both the install (nexus-3.9.0) and work directories (sonatype-work/nexus3) and everything under them.

Another thing to check... make sure the "nexus" user has a shell set, that is required for the bin/nexus startup script to be able to execute.

If you're starting this via systemd you can also run "systemctl status nexus.service"  to see log information from the console output from the last attempted startup.  Substitute nexus.service with the name you've given the service, of course.
Reply all
Reply to author
Forward
Message has been deleted
0 new messages