Networking
cancel
Showing results for 
Search instead for 
Did you mean: 

System error: [10061] Connection refused

 
Ali Bajunaid
Advisor

System error: [10061] Connection refused

Some time when the system (HP-UX) is very loaded and clients connecting from Windows to host thru TCP/IP socket they get this error:

System error: [10061] Connection refused

dbc_max_pct 2
ksi_send_max 256
max_async_ports 2000
max_thread_proc 1024
maxdsiz 0X80000000
maxdsiz_64bit 0XF0000000
maxfiles 2048
maxfiles_lim 4096
maxssiz 134217728
maxssiz_64bit 1073741824
maxswapchunks 16384
maxtsiz 0XF000000
maxtsiz_64bit 0X40000000
maxuprc (NPROC-8)
maxusers 1664
maxvgs 40
shmmax 4294967296
nproc 13332

tcp_largest_anon_port:

Largest anonymous port number to use. [1024, 65535]
Default: 65535

Can some one help me on this.

Thanks
38 REPLIES 38
Robert-Jan Goossens
Honored Contributor

Re: System error: [10061] Connection refused

Hi,

Loaded with users at those moments ?

Are you using NIS ?

Robert-Jan.
Ali Bajunaid
Advisor

Re: System error: [10061] Connection refused

Yes, loaded whit users.

We are not using NIS

Thanks
Steven E. Protter
Exalted Contributor

Re: System error: [10061] Connection refused

check out npproc and nfiles parameters in the kernel.

Run the attached script to collect data while this is going on.

check swapinfo -tam

The problem could be anywhere. If you have lots of users you need to know whether its the network, the cpu, the kernel or what thats doing this.

If its some users all the time, look additionally at settings in /var/adm/inetd.sec

If its telnet, look and see how many ptty devices you have set up.

Does it happen at high load factors or all the time.

If this post helps, please assign points.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Michael Steele_2
Honored Contributor

Re: System error: [10061] Connection refused

1) This usually is a port issue so what is the client server application between HP-UX and Windows? Omniback? Network Node Manager? From this we can id the ports for you to check.

2) Verify DNS and WINS domain names and name resolutions.

Here is a Forum hit:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xc0fa5dc05a7ad711abdc0090277a778c,00.html

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xc8f8d211e18ad5118ff10090279cd0f9,00.html

3) From what I've gleaned from these threads and your problem it sounds like the network is too loaded and dropping packets. So check for dropped packets with netstat from both HP-UX and Windows.

netstat -m | grep -i -e dropped -e collision
Support Fatherhood - Stop Family Law
Ron Kinner
Honored Contributor

Re: System error: [10061] Connection refused

I am at home now so can't check it but there is an ndd command - which controls the size of the new connection queue - which can be changed to help here. do
ndd -h |grep tcp
to see the list of ndd parameters. You can check
netstat -s
first - I believe there is a statistic there about the number of dropped new connection attempts - if it is building up during this time then you may be able to help it somewhat by lengthening the queue. Of course, if the CPU is overloaded or out of memory you might get the same problem. There is also another parameter in HPUX about the maximum number of files open at once. A TCP connection is considered an open file so you might be reaching this limit.

Ron
Ali Bajunaid
Advisor

Re: System error: [10061] Connection refused

Please find the output

Michael Steele_2
Honored Contributor

Re: System error: [10061] Connection refused

Hi Ali:

Something's not right here. Zero inode? This is not possible.

I'd suggest an immediate reboot to start with, and then patch updates. But you'll also have to reduce some kernel parameters:

ninode
nfile

You probably have some system memory fragmentation issues since you're only using 124/2020, or 6%.

15:06:15 text-sz ov proc-sz ov inod-sz ov file-sz ov
15:06:16 N/A N/A 3387/13332 0 0/108704 0 12407/202038 0
15:06:17 N/A N/A 3386/13332 0 0/108704 0 12402/202038 0
15:06:18 N/A N/A 3386/13332 0 0/108704 0 12402/202038 0
15:06:19 N/A N/A 3386/13332 0 0/108704 0 12402/202038 0

############################################

Please attach these commands:

lvlnboot -v
pvdisplay -v /dev/dsk/c0t8d0 | head -50
pvdisplay -v /dev/dsk/c2t8d0 | head -60

This is also odd:

15:06:33 c0t8d0 100.00 0.50 4 14 0.81 533.74
c2t8d0 100.00 0.50 5 26 3.63 389.77
Support Fatherhood - Stop Family Law
RolandH
Honored Contributor

Re: System error: [10061] Connection refused

See waht I have found in the technical knowledge db.

PROBLEM: After each update of a client from an HP-UX Installation Server, Omniback is changing the inet port in /etc/services for the Sun Solaris servers to 5550 instead of the default one 5555.

The following errors can be found in the session messages from the update:

[Warning] [110:103] Command execution on client failed!
remshd: Login incorrect.
[Normal] Update of client system marte-bp.inversis.com completed.

[Critical] [110:101] Client import failed!
[12:1625] Import host failed.
System error: [10061] Connection refused

The port 5550 was the default port in the previous Omniback installation.


CONFIGURATION
Operating System - HP-UX, Sun Solaris
Version - 3.10, 3.50, 4.0, 4.10
Product - omniback II

RESOLUTION: When an Inet port different than the default (5555) is being used in an Omniback cell, this value is stored in the /etc/opt/omni/customize/socket file.

After removing this file, Omniback started to use the default port (5555) in the installations with no problems.

For troubleshooting this type of problem, where the issue appears to come from a configurable parameter and could be taken from a file, the following unix command can be used:

#find /etc/opt/omni -name '*' -exec grep -l 5550 {} \;

In this case the output of the command returned the file: /etc/opt/omni/customize/socket

Sometimes you lose and sometimes the others win
Ali Bajunaid
Advisor

Re: System error: [10061] Connection refused

Our problem is not related to OMNI BACK, we are using an application running on WIN 2000 accessing HP-UNIX thru TCP/IP Socket