RFA connection call

Question

question

sgarland

16 ●0 ●1 ●4

RFA connection call

– in one such case we see that we retry several times when a connection is not available (retying in 1500ms is printed in the logs)

However in our netstat output – we see we do establish a connection – and it subsequently goes into a close_wait status – ie:

tcp 58 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 58 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 58 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 58 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 58 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 58 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 58 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 58 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 58 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 61 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 61 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 61 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 61 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 61 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 61 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 61 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 61 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 61 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 61 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 64 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 64 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 64 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 64 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 64 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 64 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 64 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 64 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 64 0 138.20.27.91:51960 10.175.181.40:14002 ESTABLISHED 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc
tcp 68 0 138.20.27.91:51960 10.175.181.40:14002 CLOSE_WAIT 13608/mdrc

Where it remains there until the process is killed.

In particular we’d like to know what call the RFA API makes when trying to establish a connection to the EED – is this possible?

trep rfa rfa-api

May 11, 2017 at 05:29 AM

10 |1500

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Jirapongse May 11, 2017 at 06:20 AM

This question is monitored by Warat.

warat.boonyanit May 11, 2017 at 10:25 PM

Hi @sgarland

Could you please show us the logs from rfa.log?

It should have additional info like this one.

[Mon Oct 03 11:14:37 2016]: (ComponentName) RSSL_Adapter: (Severity) Error: RSSL Channel read failed on connection "Default::Connection_RSSL 192.168.27.46:14002".  Channel will be closed.  (Internal debug info: "<..\..\..\Ripc\Impl\ripcsrvr.c:6662> Error:1002 ripcRead() failure. System errno: (10053)
", errno: RSSL_RET_FAILURE [10053] - )

The system errno should give you more information.

On windows, the number is Windows Sockets Error codes

On Linux, it is errno.h.

Alex Putkov.1 May 26, 2017 at 01:10 PM

Hi @sgarland

Thank you for your participation in the forum. Are any of the replies below satisfactory in resolving your query? If yes please click the 'Accept' text next to the reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question.

Thanks,

AHS

Answer 1 · 2017-05-15T06:26:05Z

sgarland

16 ●0 ●1 ●4

logging we've seen in some cases is like this

[Wed Apr 19 02:04:40 2017]: (ComponentName) RSSL_Cons_Adapter: (Severity) Information: Connection Status Changed, RSSL_Cons_Connection "Default::Connection_RSSL 192.168.220.55:14002" State: "Down" StatusCode: "None" StatusText: Connection down

[Wed Apr 19 02:04:40 2017]: (ComponentName) RSSL_Cons_Adapter: (Severity) Information: RSSL_Cons_Connection "Default::Connection_RSSL 192.168.220.55:14002" will be tried in 15000 milliseconds

[Wed Apr 19 02:05:25 2017]: (ComponentName) RSSL_Adapter: (Severity) Error: Connection "Connection_RSSL" down or unavailable

Possibly due to the provider not accepting client session requests.

[Wed Apr 19 02:05:25 2017]: (ComponentName) RSSL_Adapter: (Severity) Warning: RSSL Channel closing on connection "Default::Connection_RSSL 192.168.220.55:14002" due to "connection channel init failed"

Other times we get nothing and the connection seems to hang.

We're using solarflares onload, so we're interesting in the actual call we make to connect

May 15, 2017 at 06:26 AM

10 |1500

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

warat.boonyanit May 16, 2017 at 02:35 AM

For RSSL connection, RFA use socket api, e.g. connect() select() etc..

I'm not sure how solarflares' onload work under the hood, but does the application work on a machine that doesn't have onload?

Answer 2 · 2017-05-19T09:10:50Z

sgarland

16 ●0 ●1 ●4

@Warat B - yes, disabling onload and running without this allows RFA to initialize correctly.

In RFA which function call is reporting that no data is ready; when there actually is data ready?

do you using level, or edge triggers?

Is the socket directly in the set; or is it in some other waitable object first?

May 19, 2017 at 09:10 AM

10 |1500

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

warat.boonyanit May 24, 2017 at 04:31 AM

Hi @sgarland

Are you on Linux? You can get the function call by using strace.

Unlike Elektron API, RFA is a proprietary software.

However, if you have specific questions from strace, I can pass the questions to development.

Q&A Forum

question

RFA connection call

2 Answers

Write an Answer

question

RFA connection call

2 Answers

Write an Answer

Related Questions