Mike - The standard build of NiFi includes the bin/nifi.sh script, and one of the options for that script is the install command. When executed, that command writes a file called /etc/init.d/nifi and also manipulates a few links. I believe that something within that file and link creation causes subsequent apt-based commands to fail on Ubuntu - or at least on Ubuntu 16.04. I'm not well-versed enough in different Linux startup variations to know exactly where this is going wrong, but the workaround I provided in a previous response is how we've avoided using the built-in install command.
On Fri, Jun 15, 2018 at 9:52 AM, Mike Thomsen <mikerthom...@gmail.com> wrote: > Jeff, > > How did you get install NiFi as a service? I'm not aware of us offering > any systemd configurations for NiFi as part of the standard build from > Apache. > > In the mean time, I would suggest using Docker to run Mongo with NiFi if > this is a blocker for you and the goal here is to get a development > environment set up. If you want to do that, this is all you need: > > docker run -d -p 27017:27017 --name mongo1 mongo:latest > > docker exec -it mongo1 mongo DB_NAME_HERE > > Thanks, > > Mike > > > On Fri, Jun 15, 2018 at 9:44 AM Jeff Zemerick <jzemer...@apache.org> > wrote: > >> Hi all, >> >> Running NiFi 1.6.0 on Ubuntu 16.04 and I installed it as a service and it >> worked great. On the same box, I then installed MongoDB (via apt-get). The >> MongoDB installation failed because of errors indicating a loop in the >> services: >> >> insserv: There is a loop between service nifi and mountdevsubfs if started >> insserv: loop involving service mountdevsubfs at depth 2 >> insserv: loop involving service udev at depth 1 >> insserv: Starting nifi depends on plymouth and therefore on system >> facility `$all' which can not be true! >> >> My knowledge around services is pretty limited. I removed the NiFi >> service and the MongoDB install finished ok. Wondering if there is anything >> I should do differently? If other information is needed please let me know. >> >> Thanks, >> Jeff >> >>
