nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Parisi <phroc...@apache.org>
Subject Re: minifi cpp problem: protocol transmission failed, yielding
Date Fri, 04 May 2018 10:54:10 GMT
Arne,
  Do you have your certs defined in minifi.properties ? You either need
those properties or an SSL context service.

On Fri, May 4, 2018, 6:47 AM Arne Oslebo <arne.oslebo@uninett.no> wrote:

> Hello,
>
> I've pulled minifi cpp from master and I'm trying to send data to a
> secure nifi cluster with it. The config.yml is simply a getfile
> connected to a remote processing group:
>
> Flow Controller:
>     name: MiNiFi Flow
>
> Processors:
>     - name: GetFile
>       class: org.apache.nifi.processors.standard.GetFile
>       max concurrent tasks: 1
>       scheduling strategy: TIMER_DRIVEN
>       scheduling period: 1 sec
>       penalization period: 30 sec
>       yield period: 1 sec
>       run duration nanos: 0
>       auto-terminated relationships list:
>       Properties:
>           Input Directory: /tmp/getfile
>           Keep Source File: true
>
> Connections:
>     - name: TransferFilesToRPG
>       id: 471deef6-2a6e-4a7d-912a-81cc17e3a207
>       source name: GetFile
>       source relationship name: success
>       destination id: 8e7979f9-0161-1000-941e-3be83b4479b0
>       max work queue size: 0
>       max work queue data size: 1 MB
>       flowfile expiration: 60 sec
>
> Remote Processing Groups:
>     - name: NiFi Flow
>       id: 8e7979f9-0161-1000-941e-3be83b4479b0
>       url: https://w.x.y.z:8443/nifi
>       timeout: 30 secs
>       yield period: 10 sec
>       Input Ports:
>           - id: 29fd32ba-0163-1000-c751-29aa2e8750c5
>             name: Minifi
>             max concurrent tasks: 1
>             transport protocol: HTTP
>
> Certificate and key is set in minifi.properties and minifi successfully
> authenticates with the cluster:
> 2018-05-04 11:23:12,105 INFO [NiFi Web Server-85]
> o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (CN=minifi,
> OU=NIFI) GET https://w.x.y.z:8443/nifi-api/site-to-site (source ip:
> w.x.y.z)
> 2018-05-04 11:23:12,105 INFO [NiFi Web Server-85]
> o.a.n.w.s.NiFiAuthenticationFilter Authentication success for CN=minifi,
> OU=NIFI
> 2018-05-04 11:23:12,169 INFO [NiFi Web Server-84]
> o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (CN=minifi,
> OU=NIFI) GET https://w.x.y.z:8443/nifi-api/site-to-site/peers (source
> ip: w.x.y.z)
> 2018-05-04 11:23:12,170 INFO [NiFi Web Server-84]
> o.a.n.w.s.NiFiAuthenticationFilter Authentication success for CN=minifi,
> OU=NIFI
>
> The problem is that no data is sent to the cluster. In the
> minifi-app.log I find a warning that protocol transmission failed:
> [2018-05-04 11:23:21.945]
> [org::apache::nifi::minifi::processors::GetFile] [info] GetFile process
> /tmp/getfile/test
> [2018-05-04 11:23:21.945]
> [org::apache::nifi::minifi::core::ProcessSession] [info] Transferring
> ca111018-4f7c-11e8-88be-000c297ab98c from GetFile to relationship success
> [2018-05-04 11:23:22.196]
> [org::apache::nifi::minifi::RemoteProcessorGroupPort] [warning] protocol
> transmission failed, yielding
>
> I've tried both RAW and HTTP as transport protocol with the same result.
>
> Any idea what might be wrong?
>
> Thanks for any help,
> Arne
>

Mime
View raw message