Member since
05-09-2017
13
Posts
2
Kudos Received
0
Solutions
01-08-2018
01:01 AM
This might not be a resolution but the error went away under the following circumstances for me: Use HTTPS Do not set an SSL Context Service Make sure your SSL endpoint has the full chain of trust.
... View more
01-07-2018
10:03 PM
Did you ever resolve this? I have the same issue. InvokeHTTP only when using HTTPS.
... View more
10-11-2017
12:07 AM
Similar result with 1.4.0
... View more
10-10-2017
09:38 PM
Thanks Matt, I'm using a stock 1.3.0 from the downloads page. Interestingly enough if I try similar code (Removed the windows bits) in 1.3.0 Linux it works just fine.
... View more
10-10-2017
09:09 PM
I'm attempting to run a python script in Apache Nifi on Windows. The line itself is just "import subprocess". Does anyone else know what's going on here? This is from a template backup that ran fine on a previous nifi server that had to be rebuilt. I'm getting the following error: ERROR [Timer-Driven Process Thread-10]
o.a.nifi.processors.script.ExecuteScript
ExecuteScript[id=bfd322e2-8a4f-3521-9080-3dfcdf7f5c99] Failed to process
session due to org.apache.nifi.processor.exception.ProcessException: javax.script.ScriptException:
java.lang.UnsatisfiedLinkError: java.lang.UnsatisfiedLinkError in
<script> at line number 5: {} org.apache.nifi.processor.exception.ProcessException:
javax.script.ScriptException: java.lang.UnsatisfiedLinkError:
java.lang.UnsatisfiedLinkError in <script> at line number 5 at
org.apache.nifi.processors.script.ExecuteScript.onTrigger(ExecuteScript.java:230) at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1120) at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:147) at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47) at
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132) at
java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at
java.util.concurrent.FutureTask.runAndReset(Unknown Source) at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown
Source) at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
Source) at
java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at
java.lang.Thread.run(Unknown Source)
... View more
Labels:
- Labels:
-
Apache NiFi
06-14-2017
03:31 AM
Thanks for your help Matt. Due to restricted access to the site we ended up solving with a python script that monitors the Processor state via the Nifi API. Apologies I couldn't see this through to the end.
... View more
06-08-2017
03:44 AM
Just checked an that property is already set to true. Is there anything else I should be looking for?
... View more
06-07-2017
10:39 PM
Thanks for your reply Matt, it's a single instance nifi running on Windows. I'm heading into site in a few minutes to check that property.
... View more
06-07-2017
10:18 AM
Hello. My company is using Nifi in a temporary solution to move some files around on a Windows Server. We have some other issues with the server that causes it to reboot often and we're finding that sometimes Nifi does not restart the processors on the box. Where should I look to find a cause for this and is there a way I can force start the processors automatically if they're stopped. We're trying to resolve the reboot issue but we're looking for Nifi to be as resilient as possible during this time.
... View more
Labels:
- Labels:
-
Apache NiFi
05-09-2017
11:51 PM
2 Kudos
Hi, I'm running Nifi 1.1.2 on docker and I have some questions about preserving state. We're using ListSFTP and GetSFTP to get some files from a client of ours. At the moment we have nifi.database.directory, nifi.flowfile.repository.directory, nifi.provenance.repository.directory.default pointing to a docker volume that resides on shared storage. Our aim is to make sure that if we need to kill a docker host, or a container that we can pick up where we left off with a new container. At the moment this seems to be working with data provenance, but not with the state of ListSFTP or with the flowfiles themselves. Is there a supported method of doing this with nifi and docker? Or is there some other kind of mechanism that will let us preserve ListSFTP state, Flowfiles and Data Provenance through a reinstall of a nifi docker container?
... View more
Labels:
- Labels:
-
Apache NiFi