Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 4B2C8200D08 for ; Thu, 21 Sep 2017 14:44:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 49BEC1609D0; Thu, 21 Sep 2017 12:44:06 +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 8ED9E1609B8 for ; Thu, 21 Sep 2017 14:44:05 +0200 (CEST) Received: (qmail 46511 invoked by uid 500); 21 Sep 2017 12:44:04 -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 46502 invoked by uid 99); 21 Sep 2017 12:44:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Sep 2017 12:44:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 3CCFA18E511 for ; Thu, 21 Sep 2017 12:44:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id yzM87DqGMnzF for ; Thu, 21 Sep 2017 12:44:02 +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 058076125C for ; Thu, 21 Sep 2017 12:44:02 +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 3880AE06C7 for ; Thu, 21 Sep 2017 12:44:01 +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 7A53824189 for ; Thu, 21 Sep 2017 12:44:00 +0000 (UTC) Date: Thu, 21 Sep 2017 12:44:00 +0000 (UTC) From: "Nishant Gupta (JIRA)" To: commits@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MINIFI-348) Schema validation error parsing Flow Configuration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 21 Sep 2017 12:44:06 -0000 [ https://issues.apache.org/jira/browse/MINIFI-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174676#comment-16174676 ] Nishant Gupta commented on MINIFI-348: -------------------------------------- I am getting this below error:(Minifi logs) 2017-09-21 18:01:04,842 INFO [StandardProcessScheduler Thread-6] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled ConvertRecord[id=726f6eac-6986-34d5-0000-000000000000] to run with 1 threads 2017-09-21 18:01:04,842 INFO [StandardProcessScheduler Thread-4] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled ConvertRecord[id=d301bd59-6452-354d-0000-000000000000] to run with 1 threads 2017-09-21 18:01:04,842 INFO [StandardProcessScheduler Thread-5] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled AttributesToJSON[id=89a3f404-af13-3b2a-0000-000000000000] to run with 1 threads 2017-09-21 18:01:04,857 INFO [StandardProcessScheduler Thread-3] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled EvaluateJsonPath[id=b1a92b2b-2a07-3d1a-0000-000000000000] to run with 1 threads 2017-09-21 18:01:04,857 INFO [StandardProcessScheduler Thread-7] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled EvaluateJsonPath[id=c73f92f1-124c-372e-0000-000000000000] to run with 1 threads 2017-09-21 18:01:04,857 INFO [StandardProcessScheduler Thread-1] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled ExecuteSQL[id=36b76b6f-5aac-3f44-0000-000000000000] to run with 1 threads 2017-09-21 18:01:04,857 INFO [StandardProcessScheduler Thread-2] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled ExtractText[id=90eb5f1e-50fe-3a53-0000-000000000000] to run with 1 threads *2017-09-21 18:01:04,862 ERROR [main] o.apache.nifi.controller.FlowController Unable to start FetchDistributedMapCache[id=fb275d4d-36e6-3483-0000-000000000000] due to java.lang.IllegalStateException: Processor FetchDistributedMapCache is not in a valid state due to ['Distributed Cache Service' validated against '139d7094-b6c2-3a41-0000-000000000000' is invalid because DistributedMapCacheClientService - 1.2.0 from org.apache.nifi - nifi-distributed-cache-services-nar is not compatible with DistributedMapCacheClient - unversioned from default - system] 2017-09-21 18:01:04,862 ERROR [main] o.apache.nifi.controller.FlowController Unable to start PutDistributedMapCache[id=ba406dd0-bced-3954-0000-000000000000] due to java.lang.IllegalStateException: Processor PutDistributedMapCache is not in a valid state due to ['Distributed Cache Service' validated against '139d7094-b6c2-3a41-0000-000000000000' is invalid because DistributedMapCacheClientService - 1.2.0 from org.apache.nifi - nifi-distributed-cache-services-nar is not compatible with DistributedMapCacheClient - unversioned from default - system]* 2017-09-21 18:01:04,862 INFO [StandardProcessScheduler Thread-6] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled PutFile[id=2a75ec11-50ea-3285-0000-000000000000] to run with 1 threads 2017-09-21 18:01:04,873 INFO [StandardProcessScheduler Thread-4] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled ReplaceText[id=e7e92fc1-18ec-33a1-0000-000000000000] to run with 1 threads 2017-09-21 18:01:04,878 INFO [StandardProcessScheduler Thread-5] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled SplitText[id=b865d9b7-c9ff-3741-0000-000000000000] to run with 1 threads 2017-09-21 18:01:04,879 INFO [StandardProcessScheduler Thread-2] org.eclipse.jetty.util.log Logging initialized @87844ms to org.eclipse.jetty.util.log.Slf4jLog 2017-09-21 18:01:04,890 INFO [main] o.apache.nifi.controller.FlowController Started 0 Remote Group Ports transmitting 2017-09-21 18:01:04,890 INFO [StandardProcessScheduler Thread-7] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled UpdateAttribute[id=fac27842-b9f5-3c2c-0000-000000000000] to run with 1 threads 2017-09-21 18:01:04,915 INFO [StandardProcessScheduler Thread-3] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled UpdateAttribute[id=e1280df4-3aef-3874-0000-000000000000] to run with 1 threads 2017-09-21 18:01:04,920 INFO [main] org.apache.nifi.minifi.MiNiFiServer Flow loaded successfully. 2017-09-21 18:01:04,920 INFO [main] org.apache.nifi.BootstrapListener Successfully initiated communication with Bootstrap 2017-09-21 18:01:04,920 INFO [main] org.apache.nifi.minifi.MiNiFi Controller initialization took 6386919740 nanoseconds. 2017-09-21 18:01:04,965 INFO [StandardProcessScheduler Thread-2] org.eclipse.jetty.server.Server jetty-9.4.3.v20170317 2017-09-21 18:01:04,993 INFO [StandardProcessScheduler Thread-2] org.eclipse.jetty.server.session DefaultSessionIdManager workerName=node0 2017-09-21 18:01:04,993 INFO [StandardProcessScheduler Thread-2] org.eclipse.jetty.server.session No SessionScavenger set, using defaults 2017-09-21 18:01:04,993 INFO [StandardProcessScheduler Thread-2] org.eclipse.jetty.server.session Scavenging every 600000ms 2017-09-21 18:01:04,998 INFO [StandardProcessScheduler Thread-2] o.e.jetty.server.handler.ContextHandler Started o.e.j.s.ServletContextHandler@2f4441a9{/,null,AVAILABLE} 2017-09-21 18:01:05,028 INFO [StandardProcessScheduler Thread-2] o.eclipse.jetty.server.AbstractConnector Started ServerConnector@1c79bba5{HTTP/1.1,[http/1.1]}{0.0.0.0:7001} 2017-09-21 18:01:05,028 INFO [StandardProcessScheduler Thread-2] org.eclipse.jetty.server.Server Started @87989ms 2017-09-21 18:01:05,028 INFO [StandardProcessScheduler Thread-8] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled ListenHTTP[id=2dbd771e-8245-37f2-0000-000000000000] to run with 1 threads > Schema validation error parsing Flow Configuration > -------------------------------------------------- > > Key: MINIFI-348 > URL: https://issues.apache.org/jira/browse/MINIFI-348 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Processing Configuration > Affects Versions: 0.2.0 > Environment: Rasbian Jessie (current version) > Reporter: Nathan Green > Priority: Minor > Attachments: config.yml, EdgeCollect.xml, flow.xml, minifi-app.log, minifi-bootstrap.log > > > Using Minifi 0.2.0 Java for a project using Raspberry Pi's. > Have created a simple flow in NIFI, saved template and exported then converted to yaml using the Minifi Toolkit 0.2.0. Validation of the template passes. > When executing Minifi, get the following warning in the log: > 2017-07-10 09:45:34,671 WARN [main] o.a.n.c.StandardFlowSynchronizer Schema validation error parsing Flow Configuration at line 17, col 27: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected. > 2017-07-10 09:45:34,692 WARN [main] o.a.n.c.StandardFlowSynchronizer Schema validation error parsing Flow Configuration at line 79, col 27: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected. > Files attached: EdgeCollect.xml - exported template from Nifi > config.yml - the yaml config generated by toolkit (some minor manual edits) > flow.xml - Minifi created flow.xml file > *.log - log files from minifi server -- This message was sent by Atlassian JIRA (v6.4.14#64029)