Good for you, Keren!

On 09/22/2016 09:44 AM, Tseytlin, Keren wrote:
> Hey All,
>
> Thanks so much for the help! The remote debugger ended up working. Because
> my Nifi was on AWS, I needed to do some port tunneling in order to open up
> the communication. So I had run a line similar to this:
>
> ssh -i <<LOCATION OF PEM FILE>> -N -L 5500:<<IP ADDRESS OF AWS EC2
> NIFI>>:5500 ec2-user@<<IP ADDRESS OF AWS EC2 NIFI>>
>
>
> I documented everything here if anyone is interested:
> http://kerent.me/blog/2016/09/22/Remote-Debugging-Nifi-From-EC2.html.
>
> Thanks! 
>
> Keren
>
> On 9/21/16, 5:06 PM, "Joe Witt" <joe.w...@gmail.com> wrote:
>
>> Try
>>  telnet <ip address> 5500
>>
>> If that cannot connect then it is almost certainly a firewall issue.
>>
>> On Wed, Sep 21, 2016 at 4:28 PM, Tseytlin, Keren
>> <keren.tseyt...@capitalone.com> wrote:
>>> Thanks for the answers Russell and Manish.
>>>
>>> It appears that it was an issue with the port 8000, when I moved it to
>>> something random then Nifi would start up.
>>>
>>> I¹m connecting to an EC2 that I¹ve set up because I need to test some
>>> AWS
>>> communication. Now that I have Nifi running, I¹m trying to connect with
>>> the debugger and getting the following error:
>>>
>>> Error running AWS Nifi: Unable to open debugger port
>>> (xx.xxx.xxx.xxx:5500): java.net.ConnectionException ³Operation timed
>>> out²
>>>
>>> Does this seem like a networking error? Pretty sure my security groups
>>> have opened up all port communication if coming from my IP.
>>>
>>> Keren
>>>
>>>
>>> On 9/21/16, 4:03 PM, "Russell Bateman"
>>> <russell.bate...@perfectsearchcorp.com> wrote:
>>>
>>>> Here's how I've been doing it for the last 6 months. I use IntelliJ, but
>>>> I'm also an Eclipse guy.
>>>>
>>>> http://www.javahotchocolate.com/notes/nifi.html#20160323
>>>>
>>>> Hope this helps.
>>>>
>>>> Russ
>>>>
>>>> On 09/21/2016 01:39 PM, Tseytlin, Keren wrote:
>>>>> Hi All,
>>>>>
>>>>> I want to set up the remote debugger with Nifi so that I can step
>>>>> through the code with IntelliJ. I noticed that last year someone else
>>>>> asked about how to set up remote debugging here ->
>>>>> https://mail-archives.apache.org/mod_mbox/nifi-dev/201508.mbox/%3C76415
>>>>> 19
>>>>> c73cd4ad3832b80461b8ce...@mbx080-w2-co-2.exch080.serverpod.net%3E
>>>>>
>>>>> I followed these steps, and uncommented the line:
>>>>> java.arg.debug=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,ad
>>>>> dr
>>>>> ess=8000. However, when I do that I can't get Nifi to start up properly
>>>>> anymore. It will say that Nifi is running, but it will attempt to
>>>>> display an error page (which is some text with html formatting that
>>>>> doesn't get formatted properly).
>>>>>
>>>>> Has remote debugging changed in the past year or so since that thread
>>>>> was posted? Are there any other configs in Nifi that need to be
>>>>> changed?
>>>>> Would really appreciate additional detail for remote debugging with
>>>>> Nifi.
>>>>>
>>>>> Thanks,
>>>>> Keren
>>>>> ________________________________________________________
>>>>>
>>>>> The information contained in this e-mail is confidential and/or
>>>>> proprietary to Capital One and/or its affiliates and may only be used
>>>>> solely in performance of work or services for Capital One. The
>>>>> information transmitted herewith is intended only for use by the
>>>>> individual or entity to which it is addressed. If the reader of this
>>>>> message is not the intended recipient, you are hereby notified that any
>>>>> review, retransmission, dissemination, distribution, copying or other
>>>>> use of, or taking of any action in reliance upon this information is
>>>>> strictly prohibited. If you have received this communication in error,
>>>>> please contact the sender and delete the material from your computer.
>>>>>
>>> ________________________________________________________
>>>
>>> The information contained in this e-mail is confidential and/or
>>> proprietary to Capital One and/or its affiliates and may only be used
>>> solely in performance of work or services for Capital One. The
>>> information transmitted herewith is intended only for use by the
>>> individual or entity to which it is addressed. If the reader of this
>>> message is not the intended recipient, you are hereby notified that any
>>> review, retransmission, dissemination, distribution, copying or other
>>> use of, or taking of any action in reliance upon this information is
>>> strictly prohibited. If you have received this communication in error,
>>> please contact the sender and delete the material from your computer.
>>>
> ________________________________________________________
>
> The information contained in this e-mail is confidential and/or proprietary 
> to Capital One and/or its affiliates and may only be used solely in 
> performance of work or services for Capital One. The information transmitted 
> herewith is intended only for use by the individual or entity to which it is 
> addressed. If the reader of this message is not the intended recipient, you 
> are hereby notified that any review, retransmission, dissemination, 
> distribution, copying or other use of, or taking of any action in reliance 
> upon this information is strictly prohibited. If you have received this 
> communication in error, please contact the sender and delete the material 
> from your computer.

Reply via email to