|
From: | Landsman, Arik |
Subject: | Re: [Discuss-gnuradio] Debugging ControlPort/Thrift problem (Re: costas ambiguity and correlate-and-sync block in qpsk) |
Date: | Sun, 3 Apr 2016 15:27:41 +0000 |
Hi Tom,
Where is thrift.conf usually located?.. Thanks, Arik 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> wrote:
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
|
[Prev in Thread] | Current Thread | [Next in Thread] |