SAS MC | An existing connection was forcibly closed by remote host

[MariaD]

Hil folsk,

We recently installed SAS 9.4 TS1M6 on Linux 64bit server. We have a UAT server and a production server. All installations process ends without any errors.

We have an intermitted error on SAS MC. Sometimes, when we tried to logon (using sasadm user) on SAS MC the following error appears:

An existing connection was forcibly closed by remote host

When this erros happens, we  not be able to login on UAT or Production environment. But we can connect without any problem in SAS EG or SAS VA using the same user. 

After review the metadata log, the following messages was found:

2019-08-15T04:36:18,128 INFO [00590554] :sasadm@saspw - New client connection (1161165) accepted from server port 8561 for user sasadm@saspw. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [::ffff:10.100.1.158]:36271 for APPNAME=SASManagementConsole 904600.
2019-08-15T04:36:18,128 INFO [00590554] :sasadm@saspw - Request made to cluster SASMeta - Logical Metadata Server (A5DDP1W5.AW000001).
2019-08-15T04:36:18,128 INFO [00590554] :sasadm@saspw - Redirect client in cluster SASMeta - Logical Metadata Server (A5DDP1W5.AW000001) to server SASMeta - Metadata Server (A5DDP1W5.AY000001) at sasuat.company.com:8561.
2019-08-15T04:36:18,274 INFO [00590574] 1161165:sas - A connection reset indicates the peer has closed their connection to this session. This session will remove the peer from its set of active peers.
2019-08-15T04:36:18,274 INFO [00590574] 1161165:sas - The Bridge Protocol Engine Socket Access Method was unable to read peer data.
2019-08-15T04:36:18,275 INFO [00590574] 1161165:sas - Client connection 1161165 for user sasadm@saspw closed.

We tried to use different client machine, some without any antivirus or firewall but the problem is the same. 

Anyone has encountered this kind of error?

[SASKiwi]

Do you get the same problem with a personal login to SMC rather than using a service/admin account? In general using a personal login to SMC would be better practice.

This type of problem is better diagnosed by SAS Tech Support. 

[MariaD]

Hi @SASKiwi ,

Yes, same occurs with a personal login. I'm already open a ticket but until now their can't identify the cause either. 

Regards,

[SASKiwi]

@MariaD - OK, I'll leave it up to those with more experience.

[AnandVyas]

Hi @MariaD,

Could you launch SMC from linux server directly and see if you are facing the same issue? You will need to have X11 forwarding enabled and clients Like X Ming or MobaXTerm to launch it from server directly.

In-case you can't launch it from server, can you enable debug logs for metadata server and try to replicate the issue? The above logs you have mentioned doesn't seem to have any ERROR or WARN, just INFO for the session disconnect which could be due to various reasons.

If you also have metadata clustering enabled, you will have to enable debug logs on all the clustered servers.

Thanks!

Thanks!

[MariaD · Accepted solution]

Thanks! After reviewing the firewall again, we discovered a block on it. Now, it's working fine.

[SASKiwi]

@MariaD  - Please update post as answered then. Good to hear it is now fixed.