You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by rakesh <ra...@gmail.com> on 2017/10/13 12:10:52 UTC
Capture Change Mysql Processor is unable to start using minifi
Hello Team,
I am trying to replicate MYSQL data from multiple locations(sites) to
central location. For this, we are using CaptureChangeMysql processor at
sites to send change data to central location. We can only rely upon binary
logs that taking snapshot of tables hence the reason to use
CaptureChangeMysql. We tried NIFI 3.0/4.0 at sites which will push to
central instance. This is working without any issues.
As NIFI is little heavier, we are thinking of using MINIFI 0.2 at sites (
Even tried 0.2.1 by building the source thinking
https://issues.apache.org/jira/browse/MINIFI-403 <http://> will solve but
no luck) and put NIFI server at central. When we run the MINIFI instance, we
are getting following error, though we have put recommended libraries from
NIFI instance into MINIFI Lib directory.
2017-10-10 19:25:10,000 ERROR [main] o.apache.nifi.controller.FlowController
Unable to start CaptureChangeMySQL[id=7da38743-a33c-397f-0000-000000000000]
due to java.lang.IllegalStateException: Processor CaptureChangeMySQL is not
in a valid state due to ['Distributed Map Cache Client' validated against
'cda56c6d-0474-3249-0000-000000000000' is invalid because
DistributedMapCacheClientService - 1.3.0 from org.apache.nifi -
nifi-distributed-cache-services-nar is not compatible with
DistributedMapCacheClient - unversioned from default - system, 'Relationship
success' is invalid because Relationship 'success' is not connected to any
component and is not auto-terminated]
2017-10-10 19:25:10,005 ERROR [main] o.apache.nifi.controller.FlowController
Unable to start transmitting with
RemoteGroupPort[name=ToMiNiFiProb,targets=http://172.16.9.120:8080/nifi/?processGroupId=root∁onentIds=e73777db-015e-1000-d175-60d040746148]
due to {}
java.lang.IllegalStateException: 89b230cc-8dc5-18e0-8b12-3acf989faff5 is not
in a valid state: Port 'ToMiNiFiProb' has no outbound connections
at
org.apache.nifi.controller.AbstractPort.verifyCanStart(AbstractPort.java:574)
at
org.apache.nifi.remote.StandardRemoteGroupPort.verifyCanStart(StandardRemoteGroupPort.java:487)
at
org.apache.nifi.remote.StandardRemoteProcessGroup.startTransmitting(StandardRemoteProcessGroup.java:1020)
at
org.apache.nifi.controller.FlowController.onFlowInitialized(FlowController.java:811)
at org.apache.nifi.minifi.MiNiFiServer.start(MiNiFiServer.java:114)
at org.apache.nifi.minifi.MiNiFi.<init>(MiNiFi.java:140)
at org.apache.nifi.minifi.MiNiFi.main(MiNiFi.java:239)
2017-10-10 19:25:10,006 ERROR [main] o.apache.nifi.controller.FlowController
Unable to start transmitting with RemoteGroupPort[name=Copy of
ToMiNiFiProb,targets=http://172.16.9.120:8080/nifi/?processGroupId=root∁onentIds=e73777db-015e-1000-d175-60d040746148]
due to {}
java.lang.IllegalStateException: 89b230e2-8dc5-18e0-e93f-69f75f9ebeb9 is not
in a valid state: Port 'Copy of ToMiNiFiProb' has no outbound connections
at
org.apache.nifi.controller.AbstractPort.verifyCanStart(AbstractPort.java:574)
at
org.apache.nifi.remote.StandardRemoteGroupPort.verifyCanStart(StandardRemoteGroupPort.java:487)
at
org.apache.nifi.remote.StandardRemoteProcessGroup.startTransmitting(StandardRemoteProcessGroup.java:1020)
at
org.apache.nifi.controller.FlowController.onFlowInitialized(FlowController.java:811)
at org.apache.nifi.minifi.MiNiFiServer.start(MiNiFiServer.java:114)
at org.apache.nifi.minifi.MiNiFi.<init>(MiNiFi.java:140)
at org.apache.nifi.minifi.MiNiFi.main(MiNiFi.java:239)
Kindly suggest.
Thanks
Rakesh
--
Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
Re: Capture Change Mysql Processor is unable to start using minifi
Posted by rakesh <ra...@gmail.com>.
Hi Aldrin,
Thanks for your help my issue got resolved....
Please have a look at this.
http://apache-nifi-users-list.2361937.n4.nabble.com/Update-sql-args-n-value-to-Date-format-For-PutSql-tc3213.html
<http://apache-nifi-users-list.2361937.n4.nabble.com/Update-sql-args-n-value-to-Date-format-For-PutSql-tc3213.html>
Thanks
Rakesh
--
Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
Re: Capture Change Mysql Processor is unable to start using minifi
Posted by Aldrin Piri <al...@gmail.com>.
Unfortunately templates exported from NiFi do not contain Controller
Services that are not referenced by one of the selected extensions.
As a result, yes, this would be another Controller Services entry.
Something to the effect of the following should work:
- id: <unique id>
name: Map Cacher Server
type: org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer
Properties:
Port: 4557
Maximum Cache Entries: 10000
Eviction Strategy: "Least Frequently Used"
These properties are derived from:
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-services/nifi-distributed-cache-services-bundle/nifi-distributed-cache-server/src/main/java/org/apache/nifi/distributed/cache/server/DistributedCacheServer.java
Admittedly, this is not necessarily a target case but is certainly
doable. The caveat is that our tooling is a bit light at the moment
to support such scenarios but we certainly hope to make such processes
easier in the future.
Let us know if you experience any additional issues.
--aldrin
On Mon, Oct 16, 2017 at 11:10 AM, rakesh <ra...@gmail.com> wrote:
> Your doubt is correct, DistributedMapCacheServer controller service is not
> present in config.yml since yml is generated from NiFi template.
>
> 1.Nifi Template has been created from canvas which contains Capture Change
> Mysql and Remote Process Group. With 2 controller services enabled.
> <http://apache-nifi-users-list.2361937.n4.nabble.com/
> file/t310/NifiHelp.png>
>
>
> 2.config.yml has been generated with above configuration which I sent you
> in
> my previous reply.
>
> The yml has DistributedMapCacheClient Service but there is no reference to
> DistributedMapCacheServer in yml.
>
> Do we need to explicitly add DistributedMapCacheServer? if yes please share
> how to add.
>
>
>
>
> --
> Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
>
Re: Capture Change Mysql Processor is unable to start using minifi
Posted by rakesh <ra...@gmail.com>.
Your doubt is correct, DistributedMapCacheServer controller service is not
present in config.yml since yml is generated from NiFi template.
1.Nifi Template has been created from canvas which contains Capture Change
Mysql and Remote Process Group. With 2 controller services enabled.
<http://apache-nifi-users-list.2361937.n4.nabble.com/file/t310/NifiHelp.png>
2.config.yml has been generated with above configuration which I sent you in
my previous reply.
The yml has DistributedMapCacheClient Service but there is no reference to
DistributedMapCacheServer in yml.
Do we need to explicitly add DistributedMapCacheServer? if yes please share
how to add.
--
Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
Re: Capture Change Mysql Processor is unable to start using minifi
Posted by Aldrin Piri <al...@gmail.com>.
Do you also have a DistributedMapCacheServer controller service configured
in your config? I do not see one of these instantiated in your log. This
would explain why the client service is getting the connection refused
events.
On Mon, Oct 16, 2017 at 9:53 AM, rakesh <ra...@gmail.com> wrote:
> Exception started from the same here I'm attaching log file
> minifi-app.log
> <http://apache-nifi-users-list.2361937.n4.nabble.com/
> file/t310/minifi-app.log>
> Info: while creating nifi template all controller services are enabled same
> template is converted as yml.
>
>
>
> --
> Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
>
Re: Capture Change Mysql Processor is unable to start using minifi
Posted by rakesh <ra...@gmail.com>.
Exception started from the same here I'm attaching log file
minifi-app.log
<http://apache-nifi-users-list.2361937.n4.nabble.com/file/t310/minifi-app.log>
Info: while creating nifi template all controller services are enabled same
template is converted as yml.
--
Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
Re: Capture Change Mysql Processor is unable to start using minifi
Posted by Aldrin Piri <al...@gmail.com>.
Looks as though the cache was never started and it was then not possible to
connect to it. Are there other errors when the flow initializes concerning
the cache's initialization?
On Mon, Oct 16, 2017 at 8:23 AM, rakesh <ra...@gmail.com> wrote:
> Hi Aldrin,
>
> Thanks for your help. The error reported is goneaway after I removed the
> client cache jar file however I am getting following error.
>
> 2017-10-16 16:13:30,543 ERROR [Timer-Driven Process Thread-2]
> o.a.n.c.m.processors.CaptureChangeMySQL
> CaptureChangeMySQL[id=ec3e8c52-1f98-3a38-0000-000000000000] Failed to
> process session due to org.apache.nifi.processor.
> exception.ProcessException:
> java.io.IOException: Could not connect to Distributed Map Cache server to
> get table information: {}
> org.apache.nifi.processor.exception.ProcessException: java.io.IOException:
> Could not connect to Distributed Map Cache server to get table information
> at
> org.apache.nifi.cdc.mysql.processors.CaptureChangeMySQL.
> onTrigger(CaptureChangeMySQL.java:593)
> at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(
> StandardProcessorNode.java:1118)
> at
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(
> ContinuallyRunProcessorTask.java:144)
> 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)
> Caused by: java.io.IOException: Could not connect to Distributed Map Cache
> server to get table information
> at
> org.apache.nifi.cdc.mysql.processors.CaptureChangeMySQL.outputEvents(
> CaptureChangeMySQL.java:742)
> at
> org.apache.nifi.cdc.mysql.processors.CaptureChangeMySQL.
> onTrigger(CaptureChangeMySQL.java:571)
> ... 11 common frames omitted
> Caused by: java.net.ConnectException: Connection refused: connect
> at sun.nio.ch.Net.connect0(Native Method)
> at sun.nio.ch.Net.connect(Unknown Source)
> at sun.nio.ch.Net.connect(Unknown Source)
> at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)
> at java.nio.channels.SocketChannel.open(Unknown Source)
> at
> org.apache.nifi.distributed.cache.client.StandardCommsSession.<init>(
> StandardCommsSession.java:51)
> at
> org.apache.nifi.distributed.cache.client.DistributedMapCacheClientServi
> ce.createCommsSession(DistributedMapCacheClientService.java:300)
> at
> org.apache.nifi.distributed.cache.client.DistributedMapCacheClientServi
> ce.leaseCommsSession(DistributedMapCacheClientService.java:315)
> at
> org.apache.nifi.distributed.cache.client.DistributedMapCacheClientServi
> ce.withCommsSession(DistributedMapCacheClientService.java:370)
> at
> org.apache.nifi.distributed.cache.client.DistributedMapCacheClientServi
> ce.get(DistributedMapCacheClientService.java:184)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.nifi.controller.service.StandardControllerServiceInvoc
> ationHandler.invoke(StandardControllerServiceInvocationHandler.java:89)
> at com.sun.proxy.$Proxy23.get(Unknown Source)
> at
> org.apache.nifi.cdc.mysql.processors.CaptureChangeMySQL.outputEvents(
> CaptureChangeMySQL.java:740)
> ... 12 common frames omitted
>
>
> Here with I'm attaching my config.yml of MiNiFi. config.yml
> <http://apache-nifi-users-list.2361937.n4.nabble.com/file/t310/config.yml>
> Kindly help us to resolve this.
>
>
> Thanks
> Rakesh.
>
>
>
> --
> Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
>
Re: Capture Change Mysql Processor is unable to start using minifi
Posted by rakesh <ra...@gmail.com>.
Hi Aldrin,
Thanks for your help. The error reported is goneaway after I removed the
client cache jar file however I am getting following error.
2017-10-16 16:13:30,543 ERROR [Timer-Driven Process Thread-2]
o.a.n.c.m.processors.CaptureChangeMySQL
CaptureChangeMySQL[id=ec3e8c52-1f98-3a38-0000-000000000000] Failed to
process session due to org.apache.nifi.processor.exception.ProcessException:
java.io.IOException: Could not connect to Distributed Map Cache server to
get table information: {}
org.apache.nifi.processor.exception.ProcessException: java.io.IOException:
Could not connect to Distributed Map Cache server to get table information
at
org.apache.nifi.cdc.mysql.processors.CaptureChangeMySQL.onTrigger(CaptureChangeMySQL.java:593)
at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1118)
at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:144)
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)
Caused by: java.io.IOException: Could not connect to Distributed Map Cache
server to get table information
at
org.apache.nifi.cdc.mysql.processors.CaptureChangeMySQL.outputEvents(CaptureChangeMySQL.java:742)
at
org.apache.nifi.cdc.mysql.processors.CaptureChangeMySQL.onTrigger(CaptureChangeMySQL.java:571)
... 11 common frames omitted
Caused by: java.net.ConnectException: Connection refused: connect
at sun.nio.ch.Net.connect0(Native Method)
at sun.nio.ch.Net.connect(Unknown Source)
at sun.nio.ch.Net.connect(Unknown Source)
at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)
at java.nio.channels.SocketChannel.open(Unknown Source)
at
org.apache.nifi.distributed.cache.client.StandardCommsSession.<init>(StandardCommsSession.java:51)
at
org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService.createCommsSession(DistributedMapCacheClientService.java:300)
at
org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService.leaseCommsSession(DistributedMapCacheClientService.java:315)
at
org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService.withCommsSession(DistributedMapCacheClientService.java:370)
at
org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService.get(DistributedMapCacheClientService.java:184)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.nifi.controller.service.StandardControllerServiceInvocationHandler.invoke(StandardControllerServiceInvocationHandler.java:89)
at com.sun.proxy.$Proxy23.get(Unknown Source)
at
org.apache.nifi.cdc.mysql.processors.CaptureChangeMySQL.outputEvents(CaptureChangeMySQL.java:740)
... 12 common frames omitted
Here with I'm attaching my config.yml of MiNiFi. config.yml
<http://apache-nifi-users-list.2361937.n4.nabble.com/file/t310/config.yml>
Kindly help us to resolve this.
Thanks
Rakesh.
--
Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
Re: Capture Change Mysql Processor is unable to start using minifi
Posted by Aldrin Piri <al...@gmail.com>.
Hi Rakesh,
The nifi-distributed-cache-client-service-api.jar is the issue. Building
off latest master, that does not appear in the lib directory for me.
Perhaps that was accidentally copied?
The nifi-standard-services-api-nar contains the aforementioned jar. As a
general point of consideration, only NARs should be copied into the lib
directory. Any JARs will not have the same isolation guarantees which was
the source of the bug in 403 and what you are seeing here.
# apiri @ brick in /usr/local/Cellar/nifi/1.3.0/libexec [11:32:28]
> $ jar -tf lib/nifi-standard-services-api-nar-1.3.0.nar
> META-INF/
> META-INF/MANIFEST.MF
> META-INF/bundled-dependencies/
> META-INF/bundled-dependencies/nifi-dbcp-service-api-1.3.0.jar
>
> META-INF/bundled-dependencies/nifi-distributed-cache-client-service-api-1.3.0.jar
> META-INF/bundled-dependencies/nifi-hbase-client-service-api-1.3.0.jar
> META-INF/bundled-dependencies/nifi-http-context-map-api-1.3.0.jar
> META-INF/bundled-dependencies/nifi-load-distribution-service-api-1.3.0.jar
> META-INF/bundled-dependencies/nifi-lookup-service-api-1.3.0.jar
> META-INF/bundled-dependencies/nifi-record-1.3.0.jar
>
> META-INF/bundled-dependencies/nifi-record-serialization-service-api-1.3.0.jar
> META-INF/bundled-dependencies/nifi-schema-registry-service-api-1.3.0.jar
> META-INF/bundled-dependencies/nifi-ssl-context-service-api-1.3.0.jar
> META-INF/bundled-dependencies/nifi-utils-1.3.0.jar
> META-INF/DEPENDENCIES
> META-INF/LICENSE
> META-INF/NOTICE
> META-INF/maven/
> META-INF/maven/org.apache.nifi/
> META-INF/maven/org.apache.nifi/nifi-standard-services-api-nar/
> META-INF/maven/org.apache.nifi/nifi-standard-services-api-nar/pom.xml
>
> META-INF/maven/org.apache.nifi/nifi-standard-services-api-nar/pom.properties
On Fri, Oct 13, 2017 at 11:05 AM, rakesh <ra...@gmail.com> wrote:
> Hi Aldrin,
>
>
> Thanks for your reply. Here with I'm attaching minifi 0.2.1 lib snap along
> with yml and xml.
>
> Kindly help us to resolve.
> <http://apache-nifi-users-list.2361937.n4.nabble.com/file/t310/minifi0.png
> >
> config.yml
> <http://apache-nifi-users-list.2361937.n4.nabble.com/file/t310/config.yml>
> ProbToCentralPortUpdate.xml
> <http://apache-nifi-users-list.2361937.n4.nabble.com/file/t310/
> ProbToCentralPortUpdate.xml>
>
>
>
>
>
>
> --
> Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
>
Re: Capture Change Mysql Processor is unable to start using minifi
Posted by rakesh <ra...@gmail.com>.
Hi Aldrin,
Thanks for your reply. Here with I'm attaching minifi 0.2.1 lib snap along
with yml and xml.
Kindly help us to resolve.
<http://apache-nifi-users-list.2361937.n4.nabble.com/file/t310/minifi0.png>
config.yml
<http://apache-nifi-users-list.2361937.n4.nabble.com/file/t310/config.yml>
ProbToCentralPortUpdate.xml
<http://apache-nifi-users-list.2361937.n4.nabble.com/file/t310/ProbToCentralPortUpdate.xml>
--
Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
Re: Capture Change Mysql Processor is unable to start using minifi
Posted by Aldrin Piri <al...@gmail.com>.
The library in question is, in fact one that was troublesome and removed in
MINIFI-403.
Could you please share what your lib directory looks like and please verify
the hash you built from for 0.2.1?
I revisited the work I did for 403 and am able to use the flow provided
there that is also making use of the Distributed Map Cache Client.
Additional resources such as your config.yml and template would also be
useful to provide if this continues to be an issue.
The latter error is a result of the flow being malformed with no outbound
connections for that port. This would need to either be removed or
connected appropriately to be started.
On Fri, Oct 13, 2017 at 8:10 AM, rakesh <ra...@gmail.com> wrote:
> Hello Team,
>
> I am trying to replicate MYSQL data from multiple locations(sites) to
> central location. For this, we are using CaptureChangeMysql processor at
> sites to send change data to central location. We can only rely upon binary
> logs that taking snapshot of tables hence the reason to use
> CaptureChangeMysql. We tried NIFI 3.0/4.0 at sites which will push to
> central instance. This is working without any issues.
>
> As NIFI is little heavier, we are thinking of using MINIFI 0.2 at sites (
> Even tried 0.2.1 by building the source thinking
> https://issues.apache.org/jira/browse/MINIFI-403 <http://> will solve
> but
> no luck) and put NIFI server at central. When we run the MINIFI instance,
> we
> are getting following error, though we have put recommended libraries from
> NIFI instance into MINIFI Lib directory.
>
> 2017-10-10 19:25:10,000 ERROR [main] o.apache.nifi.controller.
> FlowController
> Unable to start CaptureChangeMySQL[id=7da38743-a33c-397f-0000-
> 000000000000]
> due to java.lang.IllegalStateException: Processor CaptureChangeMySQL is
> not
> in a valid state due to ['Distributed Map Cache Client' validated against
> 'cda56c6d-0474-3249-0000-000000000000' is invalid because
> DistributedMapCacheClientService - 1.3.0 from org.apache.nifi -
> nifi-distributed-cache-services-nar is not compatible with
> DistributedMapCacheClient - unversioned from default - system,
> 'Relationship
> success' is invalid because Relationship 'success' is not connected to any
> component and is not auto-terminated]
>
> 2017-10-10 19:25:10,005 ERROR [main] o.apache.nifi.controller.
> FlowController
> Unable to start transmitting with
> RemoteGroupPort[name=ToMiNiFiProb,targets=http://172.16.9.120:8080/nifi/?
> processGroupId=root∁onentIds=e73777db-015e-1000-d175-60d040746148]
> due to {}
>
> java.lang.IllegalStateException: 89b230cc-8dc5-18e0-8b12-3acf989faff5 is
> not
> in a valid state: Port 'ToMiNiFiProb' has no outbound connections
>
> at
> org.apache.nifi.controller.AbstractPort.verifyCanStart(
> AbstractPort.java:574)
>
> at
> org.apache.nifi.remote.StandardRemoteGroupPort.verifyCanStart(
> StandardRemoteGroupPort.java:487)
>
> at
> org.apache.nifi.remote.StandardRemoteProcessGroup.startTransmitting(
> StandardRemoteProcessGroup.java:1020)
>
> at
> org.apache.nifi.controller.FlowController.onFlowInitialized(
> FlowController.java:811)
>
> at org.apache.nifi.minifi.MiNiFiServer.start(MiNiFiServer.java:114)
>
> at org.apache.nifi.minifi.MiNiFi.<init>(MiNiFi.java:140)
>
> at org.apache.nifi.minifi.MiNiFi.main(MiNiFi.java:239)
>
> 2017-10-10 19:25:10,006 ERROR [main] o.apache.nifi.controller.
> FlowController
> Unable to start transmitting with RemoteGroupPort[name=Copy of
> ToMiNiFiProb,targets=http://172.16.9.120:8080/nifi/?processGroupId=root
> ∁onentIds=e73777db-015e-1000-d175-60d040746148]
> due to {}
>
> java.lang.IllegalStateException: 89b230e2-8dc5-18e0-e93f-69f75f9ebeb9 is
> not
> in a valid state: Port 'Copy of ToMiNiFiProb' has no outbound connections
>
> at
> org.apache.nifi.controller.AbstractPort.verifyCanStart(
> AbstractPort.java:574)
>
> at
> org.apache.nifi.remote.StandardRemoteGroupPort.verifyCanStart(
> StandardRemoteGroupPort.java:487)
>
> at
> org.apache.nifi.remote.StandardRemoteProcessGroup.startTransmitting(
> StandardRemoteProcessGroup.java:1020)
>
> at
> org.apache.nifi.controller.FlowController.onFlowInitialized(
> FlowController.java:811)
>
> at org.apache.nifi.minifi.MiNiFiServer.start(MiNiFiServer.java:114)
>
> at org.apache.nifi.minifi.MiNiFi.<init>(MiNiFi.java:140)
>
> at org.apache.nifi.minifi.MiNiFi.main(MiNiFi.java:239)
>
> Kindly suggest.
>
> Thanks
>
> Rakesh
>
>
>
> --
> Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
>