TeamForge : Post

Forum Topic - Socket problem.: (5 Items)

View: as

Sebastián Cerella(deleted)

11/07/2012 5:52 AM

post96935

Hi, there has been a problem with the "Socket" (QNX 4.25) to a disturbance in the management network of the company . "
Socket" consumes memory and CPU disabling the node (image in attachment ). It has happened in many servers at the same 
time but not in others connected to the same network. Versions of "Socket" used in these servers with the problem is 4.
25K and 4.25H. Versions of "Proc" used in these servers is 4.25Q. The "resolv.conf" is configured with the nameservers. 

Please, somebody I will guide to fix it?
Thank you very much.
Sebastian Cerella

Attachment:

Consu.jpg 59.35 KB

Oleg Bolshakov(deleted)

Re: Socket problem.

Oleg Bolshakov(deleted)

11/07/2012 6:25 AM

post96939

Re: Socket problem.

Hi Sebastián,

Nobody can help you without additional info. What is your network structure? What output of following commands?

sin ar
sin ir
sin ver
sin ti

But it's better try to upgrade from TCP/IP 4.25 to TCP/IP 5.10 and use Tcpip manager instead of Socket.

Also we don't know what happens in your network, how applications use the network, etc. Try to localize the problem. Can
 you reproduce this issue with minimal networking configuration with minimum of apps?

Respectfully,
Oleg

07.11.2012, в 14:52:04, Sebastián Cerella написал:

> Hi, there has been a problem with the "Socket" (QNX 4.25) to a disturbance in the management network of the company . 
"Socket" consumes memory and CPU disabling the node (image in attachment ). It has happened in many servers at the same 
time but not in others connected to the same network. Versions of "Socket" used in these servers with the problem is 4.
25K and 4.25H. Versions of "Proc" used in these servers is 4.25Q. The "resolv.conf" is configured with the nameservers. 

> Please, somebody I will guide to fix it?
> Thank you very much.
> Sebastian Cerella
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post96935
> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com
> <Consu.jpg>

Sebastián Cerella(deleted)

11/07/2012 7:27 AM

post96942

Re: Socket problem.

Oleg, I did not include what you request because it happens on different servers with different functions. The variety 
is great. I am attaching for two of them. I add in only one, because the other not have, syslog logs. The option of 
moving to 5.1 is that we know we should do but that involves a significant cost to the operation of the plant (steel). 
Unfortunately, I don´t know the network scheme because not manage us. It´s the management network of the company. 
Beyond this does not seem normal that a process starts to consume memory.
Thanks for your answer.

Sebastián.

Attachment:

SocketProblem.txt 43.69 KB

Chaim Filiba

11/07/2012 8:11 AM

post96944

Re: Socket problem.

Hi guys,
we complained recently on the same problem to QNX support and the answer was this:
There are limiting options for Socket to change the behaviour for bursts of traffic and memory consumption. The 
behaviour was changed for TCP/IP 5 to be more conservative.

Paul Linkins(deleted)

Re: Socket problem.

Paul Linkins(deleted)

01/14/2013 2:08 PM

post98551

Re: Socket problem.

I have exactly the same problem. I have 3 servers running Socket and all of them periodically run into high CPU 
utilization with Socket along with the software clock running slow (losing up to 10 minutes per hour). The other 25 
nodes on the network that don't run Socket are not affected. I am running Proc 4.25Q and Socket 4.25H. When it occurs, 
all 3 simultaneously experience the problem. I am sure it is triggered by some sort of network traffic.

I have not found a solution to this problem. I don't know if upgrading to TCPIP 5 is an option for me.

Return