Thanks very much for the feedback Joe, much appreciated. Checking as you suggested, nothing yet but that's got to be it, some config issue on my part, that's messing up property parsing.
On Mon, Feb 8, 2021 at 5:15 PM Joe Witt <joe.w...@gmail.com> wrote: > PatW > > I'd triple-check to ensure there are no weird/special/unexpected > characters in your nifi.properties file. These are often not obvious in > default text views so you might need to explicitly set some view to expose > them. > > Yeah this is certainly not a great user experience - we give you just > enough to have an idea but leave plenty to the imagination here. > > I suppose the good news is we know it is a port. > > Check lines in/around > nifi.remote.input.socket.port= > nifi.web.http.port=8080 > nifi.web.https.port= > nifi.cluster.node.protocol.port= > nifi.cluster.load.balance.port=6342 > > Thanks > > On Mon, Feb 8, 2021 at 2:47 PM Pat White <patwh...@verizonmedia.com> > wrote: > >> Hi Folks, >> >> Appreciate any debugging help on a very odd error, after upgrading a Nifi >> cluster from 1.6.0 to 1.11.4, flowController fails to start due to: >> >> Caused by: org.springframework.beans.factory.BeanCreationException: Error >> creating bean with name 'flowService': FactoryBean threw exception on >> object creation; nested exception is >> org.springframework.beans.factory.BeanCreationException: Error creating >> bean with name 'flowController' defined in class path resource >> [nifi-context.xml]: Cannot resolve reference to bean 'clusterCoordinator' >> while setting bean property 'clusterCoordinator'; nested exception is >> org.springframework.beans.factory.BeanCreationException: Error creating >> bean with name 'clusterCoordinator': FactoryBean threw exception on object >> creation; nested exception is java.lang.IllegalArgumentException: Port must >> be inclusively in the range [1, 65535]. Port given: 0 >> >> >> The error trace is very similar to the example Andy described in >> NIFI-6336, the issue there i believe is not specifying >> 'nifi.cluster.node.protocol.port' in 'nifi.properties', however my conf has >> that set, 'nifi.cluster.node.protocol.port=50233' and should be using >> 50233 instead of '0'. >> >> Cluster had been running fine previously and as far as i can tell, Nifi >> and ZK confs and settings are all ok. Also compared to another cluster that >> had been upgraded with no issues, and is running 1.11.4 just fine. >> >> Increased debug logging but without success so far. Am looking at the >> right property association? >> >> patw >> >> >>
