Support Questions

Find answers, ask questions, and share your expertise

user solr does not exist

avatar
New Contributor

Hello All,

As my first 'project' I try to follow the steps as described in:

https://hortonworks.com/tutorial/analyzing-social-media-and-customer-sentiment-with-apache-nifi-and-...

But when I come at the point to do su solr, there is no such user.

Configuration of Solr as describes was successful. Any idea how to proceed?

Thanks...

1 ACCEPTED SOLUTION

avatar

@j van Arendonk

Heya! Looks like there's a bit of a mixup! You are SSH'd into the "wrong" sandbox.

The VM that you set up is actually a wrapper around the "real" sandbox. See how the hostname of the machine you are SSH'd into is "sandbox-host"? You are SSH'd into the VM, whereas you want to SSH into the sandbox within the VM. There are a few different ways of doing that, feel free to take your pick:

  1. Using SSH (notice that the port needs to be 2222):
    1. For VirtualBox: ssh -p 2222 root@localhost
    2. For VMWare: ssh -p 2222 root@<the-ip-of-your-vm>
  2. Using the browser: with the sandbox running, open a browser to http://localhost:4200

You'll know you are successfully SSH'd into the sandbox when the prompt you see is "[root@sandbox /]#" (notice there is no "-host").

Hope that helps! Let us know how it goes! 🙂

View solution in original post

5 REPLIES 5

avatar
Master Mentor

@j van Arendonk

Did you add the SOLR service? That should have created the solr user owns the /opt/lucidworks-hdpsearch

Please validate that part.

avatar
New Contributor

Yes, I did add Solr Service (as described in documentation). It shows up as started in the dashboard.

avatar
Master Mentor

@j van Arendonk

can you check the directory owner and group

$ ls -al  /opt/lucidworks-hdpsearch

The solr user should also show up in

$ cat /etc/passwd

revert

avatar
New Contributor

[root@sandbox-host ~]# ls -al /opt/lucidworks-hdpsearch ls: cannot access /opt/lucidworks-hdpsearch: No such file or directory

[root@sandbox-host ~]# cat /etc/passwd root:x:0:0:root:/root:/bin/bash bin:x:1:1:bin:/bin:/sbin/nologin daemon:x:2:2:daemon:/sbin:/sbin/nologin adm:x:3:4:adm:/var/adm:/sbin/nologin lp:x:4:7:lp:/var/spool/lpd:/sbin/nologin sync:x:5:0:sync:/sbin:/bin/sync shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown halt:x:7:0:halt:/sbin:/sbin/halt mail:x:8:12:mail:/var/spool/mail:/sbin/nologin operator:x:11:0:operator:/root:/sbin/nologin games:x:12:100:games:/usr/games:/sbin/nologin ftp:x:14:50:FTP User:/var/ftp:/sbin/nologin nobody:x:99:99:Nobody:/:/sbin/nologin avahi-autoipd:x:170:170:Avahi IPv4LL Stack:/var/lib/avahi-autoipd:/sbin/nologin systemd-bus-proxy:x:999:997:systemd Bus Proxy:/:/sbin/nologin systemd-network:x:998:996:systemd Network Management:/:/sbin/nologin dbus:x:81:81:System message bus:/:/sbin/nologin polkitd:x:997:995:User for polkitd:/:/sbin/nologin tss:x:59:59:Account used by the trousers package to sandbox the tcsd daemon:/dev/null:/sbin/nologin postfix:x:89:89::/var/spool/postfix:/sbin/nologin chrony:x:996:994::/var/lib/chrony:/sbin/nologin sshd:x:74:74:Privilege-separated SSH:/var/empty/sshd:/sbin/nologin packer:x:1000:1000:packer:/home/packer:/bin/bash rpc:x:32:32:Rpcbind Daemon:/var/lib/rpcbind:/sbin/nologin rpcuser:x:29:29:RPC Service User:/var/lib/nfs:/sbin/nologin

avatar

@j van Arendonk

Heya! Looks like there's a bit of a mixup! You are SSH'd into the "wrong" sandbox.

The VM that you set up is actually a wrapper around the "real" sandbox. See how the hostname of the machine you are SSH'd into is "sandbox-host"? You are SSH'd into the VM, whereas you want to SSH into the sandbox within the VM. There are a few different ways of doing that, feel free to take your pick:

  1. Using SSH (notice that the port needs to be 2222):
    1. For VirtualBox: ssh -p 2222 root@localhost
    2. For VMWare: ssh -p 2222 root@<the-ip-of-your-vm>
  2. Using the browser: with the sandbox running, open a browser to http://localhost:4200

You'll know you are successfully SSH'd into the sandbox when the prompt you see is "[root@sandbox /]#" (notice there is no "-host").

Hope that helps! Let us know how it goes! 🙂