I have followed the details outlined in the GitHub, bootstrap article, and "Getting Started" page to create a Minifi-CPP build utilizing MQTT processors. I am currently using CentOS 7. I have uploaded a text file with the entire message that is displayed.minifi_githubBuildErrorLog.txt I believe the key error is: /usr/local/lib/libpython3.4m.a(posixmodule.o): In function `posix_openpty':
/opt/Python-3.4.9/./Modules/posixmodule.c:6041: undefined reference to `openpty'
/usr/local/lib/libpython3.4m.a(posixmodule.o): In function `posix_forkpty':
/opt/Python-3.4.9/./Modules/posixmodule.c:6130: undefined reference to `forkpty'
collect2: error: ld returned 1 exit status
main/CMakeFiles/minifiexe.dir/build.make:119: recipe for target 'main/minifi' failed
make: *** [main/minifi] Error 1
CMakeFiles/Makefile2:4451: recipe for target 'main/CMakeFiles/minifiexe.dir/all' failed
make: *** [main/CMakeFiles/minifiexe.dir/all] Error 2
Makefile:162: recipe for target 'all' failed
make: *** [all] Error 2
Can I get assistance on how to fix this error? This question closely relates to my other question: "ConsumeMQTT is not working with Minifi-CPP-0.5.0"
... View more
Along with struggling to get a clean build using the GitHub, I have been unable to get the ConsumeMQTT processor to work. I first started off with a base Minifi-CPP build found at https://nifi.apache.org/minifi/getting-started.html and https://nifi.apache.org/minifi/download.html I followed all the instructions and created a flow that consisted of a ConsumeMQTT processor and an UpdateAttribute processor. This resulted in the error: [2019-02-27 07:48:19.355] [org::apache::nifi::minifi::Properties] [info] Using configuration file located at /opt/nifi-minifi-cpp-0.5.0/conf/minifi-uid.properties
[2019-02-27 07:48:19.355] [main] [info] MINIFI_HOME=/opt/nifi-minifi-cpp-0.5.0
[2019-02-27 07:48:19.355] [org::apache::nifi::minifi::Properties] [info] Using configuration file located at /opt/nifi-minifi-cpp-0.5.0/conf/minifi.properties
[2019-02-27 07:48:19.362] [org::apache::nifi::minifi::FlowController] [info] FlowController NiFi Configuration file /opt/nifi-minifi-cpp-0.5.0/conf/config.yml
[2019-02-27 07:48:19.362] [main] [info] Loading FlowController
[2019-02-27 07:48:19.362] [org::apache::nifi::minifi::FlowController] [info] Load Flow Controller from file /opt/nifi-minifi-cpp-0.5.0/conf/config.yml
[2019-02-27 07:48:19.363] [org::apache::nifi::minifi::core::FlowConfiguration] [error] No Processor defined for ConsumeMQTT
[2019-02-27 07:48:19.363] [org::apache::nifi::minifi::core::YamlConfiguration] [error] Could not create a processor ConsumeMQTT with id 5994c484-d177-3611-0000-000000000000
[2019-02-27 07:48:19.364] [main] [error] Failed to load configuration due to exception: Could not create processor ConsumeMQTT To check to see if the Minifi build was bad, I removed the ConsumeMQTT processor and ran the program with just an UpdateAttribute processor. Minifi appeared to be working as intended and did not throw any errors in the logs. Next, I looked at the GitHub and confirmed that ConsumeMQTT is a supported processor. I then attempted to create a build using the GitHub. After several attempts of trying to get a successful build (Enabled MQTT using the bootstrap), I ran the flow exactly as I had tested in my previous statement. First I received the following error: ./minifi.sh: line 287: /opt/nifi-minifi-cpp-0.5.0-source/bin/minifi: No such file or directory I am not sure why this file is missing. I did not see it in the GitHub so my assumption is that it was supposed to be created when the build was correctly created. I proceeded to copy the minifi file from the base build I had tested. Once I ran the minifi.sh script, the logs had the same error as stated prior that ConsumeMQTT was not defined. Any suggestions on how I should proceed? Is ConsumeMQTT still a supported processor?
... View more
I believe our issue is browser version. Our browsers are outdated. Firefox and Chrome version 35 or 36 (These do not work and get stuck at logo loading screen) and some have Chrome version 50.0.2661.94 which works.
... View more
NiFi Registry successfully loads for myself (Initial admin) and one other user who has no permissions in Registry but full permissions in the NiFi its linked to. Multiple users are unable to access the UI of Registry. When they hit the URL I give them (https://example.com:17443/nifi-registry), the NiFi Registry "R" logo is displayed and never reaches the UI. They are never prompted with a "Insufficient permissions" or "Unable to load" errors. The browsers they try always display this logo (Firefox and chrome). I am using NiFi Registry 0.1.0 and NiFi 1.6.0. Also, why is there no "nifi-user.log" for NiFi-Registry. That would be helpful to figure out why users arent able to access the UI. Thanks, Jayson
... View more