Problem

Following a SwiftNEt configuration and RA client instalation, there are every 30 seconds errors in Gateway's log:

GC018W 08.03.2017 10:40:14 GateController detected the status BROKEN

(Dynamic process) caused by S_SWNET_3 bad stop. S_SWNET_3 will normally be restart by the supervisor.
JCT012W 08.03.2017 10:40:14 [S_SWNET_4] Job [h_swift_job S_SWNET_4] pid 14000 exited with status 1.
GC018W 08.03.2017 10:40:28 GateController detected the status BROKEN

(Dynamic process) caused by S_SWNET_4 bad stop. S_SWNET_4 will normally

be restart by the supervisor.
JCT012W 08.03.2017 10:40:28 [S_SWNET_3] Job [h_swift_job S_SWNET_3] pid 14006 exited with status 1.

The swiftnet command works:

$ -> /RA/bin >

$ -# ./sag_test_connect -fileact

Enter the SWIFTNet user name: HSM1:fileact2

Enter the password for SWIFTNet user HSM1:fileact2:

Sending InitRequest

Received InitResponse

Sending CreateContextRequest

Received CreateContextResponse

Sending ConnectivityRequest

Received ConnectivityResponse

Get status.

Sending DestroyContextRequest

Received DestroyContextResponse

Sending TermRequest

Received TermResponse

SWIFTAlliance Gateway FileAct connectivity test completed successfully.

The ports 48002 and 48003 opens following the above command. Only the 48002 remains activ:

$ -# netstat -an | grep 4800

tcp 0 0 138.21.230.52:49369 10.235.255.49:48002 ESTABLISHED

tcp 0 0 138.21.230.52:50036 10.235.255.49:48002 TIME_WAIT

tcp 0 0 138.21.230.52:38290 10.235.255.49:48003 TIME_WAIT

tcp 0 0 138.21.230.52:49368 10.235.255.49:48002 ESTABLISHED

Resolution

In this specific scenario, the Remote Site A in question had a backup Remote Site B which was not activated.

After every Gateway stop/start the backup Remote Site B was activated and the above errors appeared in the logs.

To solve the problem there are 2 possible ways:

1.

Delete the backup Remote Site B (from Remote Site A and then entirely Remote Site B) as it is not configured properly yet, so it is not used.

or

2.

Remove the backup Remote Site B configuration from the first valid Remote Site A and then right click the Remote Site B (the one that was set as backup for the first one) and uncheck all the options from General / Role and General / Initialization mode.

In this way this Remote Site will remain inactive even after a Gateway restart.