Re: [Discuss-gnuradio] Debugging ControlPort/Thrift problem (Re: costas ambiguity and correlate-and-sync block in qpsk)

[Andy Walls]

Well, on that machine (Fedora 20) I never built thrift.  No problem. ;)

On April 3, 2016 12:51:31 PM EDT, "Landsman, Arik" <address@hidden> wrote:
>setting port=0 in thrift.conf did the trick, GRC now runs all
>flowgraphs as expected. 
>
>Andy, still at odds on how you got yours to work.. did you modify
>thrift.conf in any way? 
>________________________________________
>From: Andy Walls address@hidden
>Sent: Sunday, April 03, 2016 11:36 AM
>To: Tom Rondeau; Landsman, Arik
>Cc: address@hidden
>Subject: Re: Debugging ControlPort/Thrift problem (Re:
>[Discuss-gnuradio] costas ambiguity and correlate-and-sync block in
>qpsk)
>
>Hmm.  Maybe GRC trying to evaluate the block for the sake of values in
>other blocks is spawning and keeping the mini flowgraph open.
>
>Weird.
>
>On April 3, 2016 11:31:02 AM EDT, Tom Rondeau <address@hidden> wrote:
>>On Sun, Apr 3, 2016 at 11:27 AM, Landsman, Arik
>><address@hidden>
>>wrote:
>>
>>> Hi Tom,
>>>
>>> Where is thrift.conf usually located?..
>>>
>>> Thanks,
>>> Arik
>>>
>>
>>
>>In ~/.gnuradio/thrift.conf
>>
>>
>>And interesting observation about having to remove Modulate Vector
>>completely. That might be the same problem I'm experiencing. Strange
>it
>>should matter just by being there.
>>
>>Tom
>>
>>
>>
>>> ------------------------------
>>> *From:* address@hidden address@hidden on behalf of
>>Tom
>>> Rondeau address@hidden
>>> *Sent:* Sunday, April 03, 2016 11:22 AM
>>> *To:* Andy Walls
>>> *Cc:* Landsman, Arik; address@hidden
>>> *Subject:* Re: Debugging ControlPort/Thrift problem (Re:
>>> [Discuss-gnuradio] costas ambiguity and correlate-and-sync block in
>>qpsk)
>>>
>>> On Sun, Apr 3, 2016 at 8:49 AM, Andy Walls
>><address@hidden
>>>
>><http://redir.aspx?REF=MLTuqE1mz3OoEU0FQph_u9UvFjVZkTydup7q_wI-4c3OmAsr1FvTCAFtYWlsdG86YW5keUBzaWx2ZXJibG9ja3N5c3RlbXMubmV0>
>>> > wrote:
>>>
>>>>
>>>> > Otherwise, you didn't drop a control port related block on the
>>>> > flowgraph did you?
>>>>
>>>>
>>>> Here is some good info on how GRNURadio's control port works at a
>>high
>>>> level:
>>>> https://gnuradio.org/redmine/projects/gnuradio/wiki/ControlPort
>>>>
>><http://redir.aspx?REF=azbe_GyxFRKBpOrbCXsEn87Wj8ET5GUm0QC3BOXvRTTOmAsr1FvTCAFodHRwczovL2dudXJhZGlvLm9yZy9yZWRtaW5lL3Byb2plY3RzL2dudXJhZGlvL3dpa2kvQ29udHJvbFBvcnQ.>
>>>> https://gnuradio.org/doc/doxygen/page_ctrlport.html
>>>>
>><http://redir.aspx?REF=SxLIHILotdP8HOdDt_K6tXfxwQKnxOUFu1TiyaDWXwfOmAsr1FvTCAFodHRwczovL2dudXJhZGlvLm9yZy9kb2MvZG94eWdlbi9wYWdlX2N0cmxwb3J0Lmh0bWw.>
>>>>
>>>> From that second page, it appears that running two flowgraphs on
>the
>>>> same machine has a problem caused by Apache Thrift and GNURadio's
>>>> configuration of the Control Port network port (default of 9090).
>>>>
>>https://gnuradio.org/doc/doxygen/page_ctrlport.html#ctrlport_thrift_issues
>>>>
>><http://redir.aspx?REF=PEreM48t5VngbsJ1nPZyY40coia_Ki9MnN28CfQhswzOmAsr1FvTCAFodHRwczovL2dudXJhZGlvLm9yZy9kb2MvZG94eWdlbi9wYWdlX2N0cmxwb3J0Lmh0bWwjY3RybHBvcnRfdGhyaWZ0X2lzc3Vlcw..>
>>>>
>>>> So please only run on flowgraph at a time, at first, to
>troubleshoot
>>>> this issue.
>>>>
>>>> Second, you may want to try setting the GR_CONF_THRIFT_PORT
>>environment
>>>> variable to something other than 9090, a port that you know is open
>>on
>>>> your machine, for each separate flowgraph that you run.
>>>>
>>>> FYI, the modulate_vector block runs a "mini"-flowgraph, before the
>>main
>>>> flowgraph actually runs:
>>>>
>>>>
>>>>
>>https://github.com/gnuradio/gnuradio/blob/master/gr-digital/lib/modulate_vector.cc#L59
>>>>
>><http://redir.aspx?REF=rCyK29_HIPXb4AHqBP038K2B4o2SxURzlIzwumhDH6vOmAsr1FvTCAFodHRwczovL2dpdGh1Yi5jb20vZ251cmFkaW8vZ251cmFkaW8vYmxvYi9tYXN0ZXIvZ3ItZGlnaXRhbC9saWIvbW9kdWxhdGVfdmVjdG9yLmNjI0w1OQ..>
>>>>
>>>> Hopefully, there isn't some sort of weird race condition with the
>>Thrift
>>>> port being open for the modulate_vector block's mini-flowgraph and
>>the
>>>> main flowgraph.
>>>>
>>>>
>>>> Hi Tom,
>>>>
>>>> Do you have any comments or insights on Arik's Thrift error message
>>>> and/or the possibility of modulate_vector's mini-flowgraph causing
>>>> problems with Thrift's network port and the main flowgraph?
>>>>
>>>> Regards,
>>>> Andy
>>>>
>>>
>>> Andy,
>>>
>>> I think you've got it on the Thrift issue. However, running the
>>modulate
>>> vector mini flowgraph first should kill itself immediately and free
>>up the
>>> port, so I don't think that's the problem. On the other hand, I've
>>been
>>> seeing issues recently where every time I launch GRC, it seems to
>>cause a
>>> conflict with whatever port I'm setting. Almost as though GRC is
>>launching
>>> something and holding on to the port specified in the thrift.conf
>>file. I
>>> thought this could just be a problem on my laptop (I've been
>>traveling a
>>> lot -- more than usual even -- and developing on my laptop can lead
>>to me
>>> doing a lot of crazy things), but I think I've since seen it on my
>>office
>>> workstation as well. That could be a problem here, too. We'll have
>to
>>track
>>> that down.
>>>
>>> Using the GR_CONF_THRIFT_PORT variable is a good idea to set the
>port
>>per
>>> flowgraph you're running. Another option is to set the port to 0 in
>>> thrift.conf, which will cause Thrift to open an ephemeral port for
>>each
>>> server is creates. You'll just have to pay attention to the message
>>output
>>> that announces the ControlPort endpoint to find out what port it's
>>running
>>> on.
>>>
>>> Tom
>>>
>>>