RIM Node is down but services are running

[rohitk1609]

Hi Techies,

I am facing a problem when my RIM node is down but my services are running fine. I am getting below error message in log files:

An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full↵↓Unable to connect to the remote server.

Please help to up the RIM node

Thanks in Advance!

Rohit

[YoussefBelloum]

Hi,

Maybe ltu‌ can help here

[Levi_Turner]

1. Open regedit
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters
3. Either:
   1. Edit the existing MaxUserPort entry to a higher value. The default value is 5,000 and the maximum value is 65,534.
   2. Create a DWORD Entry, edit the entry, and enter a decimal value

Hope that helps.

[vlad_komarov]

Levi,

Thanks for reply.

I am not 100% sure that this was a resource issue...

In the case Rohit has mentioned, the full system restart has fixed the problem and all nodes are available now.

I did a single node restart first (the one that was offline), but it did not help.

Full system restart (all 7 nodes) have fixed the issue.

My main concern is how to detect this problem in the future.

We are running a services status check on all nodes and it sends the alert if the critical service is down.

In this case all services were running and I did not notice that we have a problem until I've looked at QMC over the weekend.

Apparently, the disconnect happened on Friday...

Any suggestions how we can detect this kind of issues in the future?

Regards,

Vlad

[rohitk1609]

Do Memory in primary partition less than 8 GB can be any cause?

[vlad_komarov]

We have ENOUGH memory on that server.

We do have ~6 GB of HD free space on C: partition, but it should be enough also... Considering that all apps / logs are located on 😧 partition.

VK

[agigliotti]

Hi Levi,

I'm facing a similar problem, below my System Repository log:

-----

System.Repository.Repository.Core.Repository.ServerNodeConfigurationRepository 119 203833e9-387f-4a07-8a3c-7ce1e9c58769 UMBRA\qlikservice Unexpected error in ExecuteGet An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full 127.0.0.1:4432↵↓The underlying provider failed on Open.    at Devart.Data.PostgreSql.h.x()↵↓   at Devart.Data.PostgreSql.h..ctor(PgSqlConnectionOptions A_0)↵↓   at Devart.Data.PostgreSql.ag.a(au A_0, Object A_1, DbConnectionBase A_2)↵↓   at Devart.Common.DbConnectionFactory.a(DbConnectionPool A_0, au A_1, DbConnectionBase A_2)↵↓   at Devart.Common.DbConnectionPool.a(DbConnectionBase A_0)↵↓   at Devart.Common.DbConnectionPool.GetObject(DbConnectionBase owningConnection)↵↓   at Devart.Common.DbConnectionFactory.b(DbConnectionBase A_0)↵↓   at Devart.Common.DbConnectionClosed.Open(DbConnectionBase outerConnection)↵↓   at Devart.Common.DbConnectionBase.Open()↵↓   at Devart.Data.PostgreSql.PgSqlConnection.Open()↵↓   at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext](TTarget target, Action`2 operation, TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed)↵↓   at System.Data.Entity.Infrastructure.Interception.DbConnectionDispatcher.Open(DbConnection connection, DbInterceptionContext interceptionContext)↵↓   at System.Data.Entity.Core.EntityClient.EntityConnection.Open()↵↓   at System.Data.Entity.Core.EntityClient.EntityConnection.Open()↵↓   at System.Data.Entity.Core.Objects.ObjectContext.EnsureConnection(Boolean shouldMonitorTransactions)↵↓   at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction(Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)↵↓   at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__5()↵↓   at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)↵↓   at System.Data.Entity.Core.Objects.DataClasses.EntityCollection`1.Load(List`1 collection,

-----

and also the below very similar error:

-----

System.Repository.Repository.Core.Repository.ServerNodeConfigurationRepository 12 9a6c7b0c-5fa1-4b34-88a3-a1669114bb61 UMBRA\qlikservice Unexpected error in ExistsByID An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full 127.0.0.1:4432↵↓The underlying provider failed on Open.    at Devart.Data.PostgreSql.h.x()↵↓   at Devart.Data.PostgreSql.h..ctor(PgSqlConnectionOptions A_0)↵↓   at Devart.Data.PostgreSql.ag.a(au A_0, Object A_1, DbConnectionBase A_2)↵↓   at Devart.Common.DbConnectionFactory.a(DbConnectionPool A_0, au A_1, DbConnectionBase A_2)↵↓   at Devart.Common.DbConnectionPool.a(DbConnectionBase A_0)↵↓   at Devart.Common.DbConnectionPool.GetObject(DbConnectionBase owningConnection)↵↓   at Devart.Common.DbConnectionFactory.b(DbConnectionBase A_0)↵↓   at Devart.Common.DbConnectionClosed.Open(DbConnectionBase outerConnection)↵↓   at Devart.Common.DbConnectionBase.Open()↵↓   at Devart.Data.PostgreSql.PgSqlConnection.Open()↵↓   at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext](TTarget target, Action`2 operation, TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed)↵↓   at System.Data.Entity.Infrastructure.Interception.DbConnectionDispatcher.Open(DbConnection connection, DbInterceptionContext interceptionContext)↵↓   at System.Data.Entity.Core.EntityClient.EntityConnection.Open()↵↓   at System.Data.Entity.Core.EntityClient.EntityConnection.Open()↵↓   at System.Data.Entity.Core.Objects.ObjectContext.EnsureConnection(Boolean shouldMonitorTransactions)↵↓   at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction(Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)↵↓   at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__5()↵↓   at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)↵↓   at System.Data.Entity.Core.Objects.ObjectQuery`1.<System.Collections.Generic.IEnumerable<T>.GetEnumerator>b__0()↵↓   at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext()↵↓   at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source)↵↓   at Repository.Core.Repository.Common.EntityTransactionRepository.ExistsById(Guid id)↵↓   at Repository.Core.Repository.Common.ModelRepository`1.ExistsByID(Guid id) 9a6c7b0c-5fa1-4b34-88a3-a1669114bb61

-----

Both QMC and Hub are not reachable.

Using pgAdmin seems that PostgreSQL database is not responding.

What does could be the root cause of this error ?

Thanks in advance for your time.

Best Regards

Andrea

[agigliotti]

I'm facing a similar issue since I upgraded to April '18 version.

did you find the root cause of this issue ?

did you solve it ?

Please let me know.

Thanks

Andrea

[vlad_komarov]

I would strongly recommend to NOT use the April 2018 release.

It's very unstable and it's not worth to spend time handling issues there.

The June 2018 SR1 release is better, but there are few issues there as well.

We are still on Feb 2018 version.....

VK

[agigliotti]

Unfortunately I got the above issue even after upgraded to June 2018 patch 1 version.