nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Rosander <brosan...@apache.org>
Subject Re: What else besides port conflict will keep NiFi 1.0.0 from running?
Date Fri, 04 Nov 2016 19:31:49 GMT
No worries.  That's bitten me more than once :-).  It would be nice of the
JVM to print at least the port it's trying to bind to to make it a little
more obvious.

On Fri, Nov 4, 2016 at 3:29 PM, Russell Bateman <
russell.bateman@perfectsearchcorp.com> wrote:

> Bryan,
>
> Yes, thank you very much, I did and I wasn't even thinking about that
> (port 8000 no less).
>
> Embarrassed,
>
> Russ
>
> On 11/04/2016 11:47 AM, Bryan Rosander wrote:
>
> Hey Russ,
>
> It looks like you may have configured NiFi for remote debugging.  If you
> have port conflicts on the port Java tries to listen on for remote
> debugging, you'll see an error just like that.
>
> Thanks,
> Bryan
>
> On Fri, Nov 4, 2016 at 1:46 PM, Russell Bateman <russell.bateman@
> perfectsearchcorp.com> wrote:
>
>> I feel sheepish asking this question, but I don't know where to turn. Now
>> ready to move up to NiFi 1.0.0 from 0.7.1, where I've been running
>> successfully since 0.4.0 nearly a year ago, and with no changes ever (in my
>> test environment) to *nifi.properties* except:
>>
>>     nifi.web.http.port=9091
>>
>> I can't get NiFi to launch. The error from *logs/nifi-bootstrap.log* is:
>>
>> *~/dev/nifi/nifi-1.0.0/logs $ cat nifi-bootstrap.log*
>> 2016-11-04 11:32:32,217 INFO [main] o.a.n.b.NotificationServiceManager
>> Successfully loaded the following 0 services: []
>> 2016-11-04 11:32:32,221 INFO [main] org.apache.nifi.bootstrap.RunNiFi
>> Registered no Notification Services for Notification Type NIFI_STARTED
>> 2016-11-04 11:32:32,221 INFO [main] org.apache.nifi.bootstrap.RunNiFi
>> Registered no Notification Services for Notification Type NIFI_STOPPED
>> 2016-11-04 11:32:32,221 INFO [main] org.apache.nifi.bootstrap.RunNiFi
>> Registered no Notification Services for Notification Type NIFI_DIED
>> 2016-11-04 11:32:32,222 INFO [main] org.apache.nifi.bootstrap.Command
>> Apache NiFi is not currently running
>> 2016-11-04 11:32:35,684 INFO [main] o.a.n.b.NotificationServiceManager
>> Successfully loaded the following 0 services: []
>> 2016-11-04 11:32:35,687 INFO [main] org.apache.nifi.bootstrap.RunNiFi
>> Registered no Notification Services for Notification Type NIFI_STARTED
>> 2016-11-04 11:32:35,688 INFO [main] org.apache.nifi.bootstrap.RunNiFi
>> Registered no Notification Services for Notification Type NIFI_STOPPED
>> 2016-11-04 11:32:35,688 INFO [main] org.apache.nifi.bootstrap.RunNiFi
>> Registered no Notification Services for Notification Type NIFI_DIED
>> 2016-11-04 11:32:35,695 INFO [main] org.apache.nifi.bootstrap.Command
>> Starting Apache NiFi...
>> 2016-11-04 11:32:35,695 INFO [main] org.apache.nifi.bootstrap.Command
>> Working Directory: /home/russ/dev/nifi/nifi-1.0.0
>> 2016-11-04 11:32:35,696 INFO [main] org.apache.nifi.bootstrap.Command
>> Command: /home/russ/dev/jdk1.8.0_25/bin/java -classpath
>> /home/russ/dev/nifi/nifi-1.0.0/./conf:/home/russ/dev/nifi/ni
>> fi-1.0.0/./lib/nifi-properties-loader-1.0.0.jar:/home/russ/
>> dev/nifi/nifi-1.0.0/./lib/jcl-over-slf4j-1.7.12.jar:/home/
>> russ/dev/nifi/nifi-1.0.0/./lib/nifi-api-1.0.0.jar:/home/
>> russ/dev/nifi/nifi-1.0.0/./lib/logback-core-1.1.3.jar:/
>> home/russ/dev/nifi/nifi-1.0.0/./lib/logback-classic-1.1.3.
>> jar:/home/russ/dev/nifi/nifi-1.0.0/./lib/nifi-framework-
>> api-1.0.0.jar:/home/russ/dev/nifi/nifi-1.0.0/./lib/jul-to-
>> slf4j-1.7.12.jar:/home/russ/dev/nifi/nifi-1.0.0/./lib/
>> nifi-documentation-1.0.0.jar:/home/russ/dev/nifi/nifi-1.0.0/
>> ./lib/nifi-runtime-1.0.0.jar:/home/russ/dev/nifi/nifi-1.0.0/
>> ./lib/slf4j-api-1.7.12.jar:/home/russ/dev/nifi/nifi-1.0.0/
>> ./lib/nifi-properties-1.0.0.jar:/home/russ/dev/nifi/nifi-
>> 1.0.0/./lib/bcprov-jdk15on-1.54.jar:/home/russ/dev/nifi/nifi-1.0.0/./lib/log4j-over-sl
>> f 4j-1.7.12.jar:/home/russ/dev/nifi/nifi-1.0.0/./lib/commons-
>> lang3-3.4.jar:/home/russ/dev/nifi/nifi-1.0.0/./lib/nifi-nar-utils-1.0.0.jar
>> -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m
>> -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8000
>> -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true
>> -Djava.awt.headless=true -XX:+UseG1GC -Djava.protocol.handler.pkgs=sun.net.www.protocol
>> -Dnifi.properties.file.path=/home/russ/dev/nifi/nifi-1.0.0/./conf/nifi.properties
>> -Dnifi.bootstrap.listen.port=33110 -Dapp=NiFi -
>> Dorg.apache.nifi.bootstrap.config.log.dir=/home/russ/dev/nifi/nifi-1.0.0/logs
>> org.apache.nifi.NiFi
>> *2016-11-04 11:32:35,747 ERROR [NiFi logging handler]
>> org.apache.nifi.StdErr ERROR: transport error 202: bind failed: Address
>> already in use*
>> *2016-11-04 11:32:35,747 ERROR [NiFi logging handler]
>> org.apache.nifi.StdErr ERROR: JDWP Transport dt_socket failed to
>> initialize, TRANSPORT_INIT(510)*
>> *2016-11-04 11:32:35,747 ERROR [NiFi logging handler]
>> org.apache.nifi.StdErr JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No
>> transports initialized [debugInit.c:750]*
>> *2016-11-04 11:32:35,747 INFO [NiFi logging handler]
>> org.apache.nifi.StdOut FATAL ERROR in native method: JDWP No transports
>> initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)*
>> 2016-11-04 11:32:36,739 INFO [main] org.apache.nifi.bootstrap.RunNiFi
>> NiFi never started. Will not restart NiFi
>>
>> And yet,
>>
>> # lsof -i | grep 9091
>>
>> produces nothing for port 9091 (nor does netstat -lptu). So, port 9091
>> is not in use on my host, yet the error leads me to believe that this is
>> the problem. (Indeed, I've seen this error before, or something like it,
>> when running pre-1.0 NiFi and recognizing that I had a port conflict which,
>> corrected, always led to happiness.)
>>
>> Put-downs, wolf whistles and cat calls accepted (and welcome!), but what
>> am I doing wrong or where should I look?
>>
>> Thanks,
>> Russ
>>
>>
>
>

Mime
View raw message