From commits-return-37378-archive-asf-public=cust-asf.ponee.io@nifi.apache.org Thu Jan 25 20:32:08 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 6E2FF180651 for ; Thu, 25 Jan 2018 20:32:08 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 5CCD1160C17; Thu, 25 Jan 2018 19:32:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A2F3A160C3D for ; Thu, 25 Jan 2018 20:32:07 +0100 (CET) Received: (qmail 28442 invoked by uid 500); 25 Jan 2018 19:32:06 -0000 Mailing-List: contact commits-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list commits@nifi.apache.org Received: (qmail 28433 invoked by uid 99); 25 Jan 2018 19:32:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jan 2018 19:32:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 5A8151A02CF for ; Thu, 25 Jan 2018 19:32:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.711 X-Spam-Level: X-Spam-Status: No, score=-100.711 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 8eqOcWTq6YzK for ; Thu, 25 Jan 2018 19:32:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 09EAD5F398 for ; Thu, 25 Jan 2018 19:32:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7FFB4E0EEF for ; Thu, 25 Jan 2018 19:32:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 77153240F6 for ; Thu, 25 Jan 2018 19:32:02 +0000 (UTC) Date: Thu, 25 Jan 2018 19:32:02 +0000 (UTC) From: "Aldrin Piri (JIRA)" To: commits@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MINIFI-429) Unable to use SSL Context with ListenHTTP MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MINIFI-429?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1633= 9709#comment-16339709 ]=20 Aldrin Piri commented on MINIFI-429: ------------------------------------ Hi [~davidrsmith], Glad to hear that resolved it.=C2=A0 Yes,=C2=A0I think it seems like a reas= onable one but I have suggested MINIFI-422=C2=A0 to help avoid some of thes= e issues given so much overlap between the two instances.=C2=A0 Should be m= inimal, outward changes to our users but a more consolidated and unified de= velopment approach to catch these things sooner. > Unable to use SSL Context with ListenHTTP > ----------------------------------------- > > Key: MINIFI-429 > URL: https://issues.apache.org/jira/browse/MINIFI-429 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Core Framework, Processing Configuration > Affects Versions: 0.3.0 > Environment: VM running CentoS 7.3, with 16Gb ram & 4 CPU's > Reporter: David Smith > Assignee: David Smith > Priority: Major > > I=C2=A0 have a VM which is running, NiFi 1.3.0 and MiNiFi 0.3.0 (Java ver= sion) and Java 8. They share a common keystore which I have set up as Stand= ardSSLContextService in=C2=A0 NIFI. > I have created a flow which starts with a ListenHTTP, a couple of updateA= ttributes, and then a PostHTTP. The flow works fine in NiFi, I exported it = as a template and used the MiniFi 0.3.0 Toolkit to convert it into a yml fi= le. I have edited the new config.yml file with the passowrds for the keysto= res etc. however when I start Minifi I get an ERROR when ListenHTTP tries t= o start, PostHTTP appears to start correctly. Unfortunately the VM is in a = segregated system so it is difficult to copy configs an logs. > Below are a copy of the ERROR message and what I believe is the pertinent= parts of the config.yml file: > =C2=A0 > ERROR [main] o.apache.nifi.controller.FlowController Unable to start List= enHTTP[id=3D ] due to java.langIllegalStateException: Processor Liste= nHTTP is not in a valid state due to ['SSL Context Service' validated again= st '968df85a-dfd5-39ad-0000-000000000000' is invalid because Controller Ser= vice=C2=A0=C2=A0'968df85a-dfd5-39ad-0000-000000000000' is not a valid Contr= oller Service Identifier or does not reference the correct type of Controll= er Service] > =C2=A0 > config.yml=C2=A0 (part of) > name: ListenHTTP > class: org.apache.nifi.processors.standard.ListenHTTP > max concurrent tasks: 1 > scheduling strategy: TIMER DRIVEN > scheduling period: 0 sec > yield period: 1 sec > run duration nanos: 0 > Properties: > =C2=A0 =C2=A0 =C2=A0Authorized DN Pattern: .* > =C2=A0 =C2=A0 Base Path: contentListener > =C2=A0 =C2=A0 HTTP Headers to receive as Attributes (Regex) : > =C2=A0 =C2=A0 Listening Port : 22222 > =C2=A0 =C2=A0 Max data to receive per second: > =C2=A0 =C2=A0Max Unconfirmed FLowFile Time: 60 secs > =C2=A0 =C2=A0SSL Context Service: 968df85a-dfd5-39ad-0000-00000000000 > =C2=A0 > Controller Services: > =C2=A0- id:=C2=A0968df85a-dfd5-39ad-0000-00000000000=C2=A0 =C2=A0name: St= andardSSLContextService=C2=A0 =C2=A0type: org.apache.nifi.ssl.StandardSSLCo= ntextService > =C2=A0 =C2=A0Properties: > =C2=A0 =C2=A0 =C2=A0 Keystore FIlename: /opt/keystore/host.key > =C2=A0 =C2=A0 =C2=A0 Keystore Password: XXXXXXX > =C2=A0 =C2=A0 =C2=A0 Keystore Type: JKS > =C2=A0 =C2=A0 =C2=A0 SSL Protocol: TLS > =C2=A0 =C2=A0 =C2=A0 Truststore Filename: /opt/keystore/trust.key > =C2=A0 =C2=A0 =C2=A0 Truststore Password:=C2=A0 YYYYYY > =C2=A0 =C2=A0 =C2=A0 Truststore Type: JKS > =C2=A0 =C2=A0 =C2=A0 Key-password:=C2=A0 XXXXXXX > =C2=A0 > =C2=A0 > If any further information is required please ask. -- This message was sent by Atlassian JIRA (v7.6.3#76005)