I just noticed you are using Ubuntu 18. You really should be using SystemD which the script does not create. Here is what I use in my environments. This file should be placed in /etc/systemd/system and I call it nifi-registry.service.
[Unit] Description=Apache NiFi Registry Documentation=http://nifi.apache.org Requires=network.target remote-fs.target After=network.target remote-fs.target [Service] Type=forking User=nifi-registry Group=nifi-registry Environment=JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-amd64 ExecStart=/opt/nifi-registry/latest/bin/nifi-registry.sh start ExecStop=/opt/nifi-registry/latest/bin/nifi-registry.sh stop [Install] WantedBy=multi-user.target 1. systemctl daemon-reload -> to pick up the changes and rerun system generators 2. systemctl enable nifi-registry -> enables the nifi-registry service to start on system re/boot 3. systemctl start nifi-registry -> start the nifi-registry service, IF you enable the service in step 2 you will only have to do this once. 4. systemctl stop nifi-registry -> stop the nifi-registry service. Hope this help! Jeremy Dyer On Tue, Aug 27, 2019 at 9:45 AM Erik Anderson <eand...@pobox.com> wrote: > Personally I would just use the registry packaged in the docker container > > https://hub.docker.com/r/apache/nifi-registry > > Makes deployment and upgrades a snap. Nearly plug-and-play with enterprise > integrations, assuming you get your LDAP magic value strings > (LDAP_MANAGER_DN, LDAP_USER_SEARCH_BASE, LDAP_USER_SEARCH_FILTER) figured > out. > > Erik Anderson > Bloomberg >
