Sponsored Content
Full Discussion: SSH slow at connect
Operating Systems HP-UX SSH slow at connect Post 302723553 by SapBasisSystem on Tuesday 30th of October 2012 10:46:00 AM
Old 10-30-2012
Hi,

We have set only nsswitch.conf in some systems HP-UX:

Code:
# cat etc/nsswitch.conf
hosts: files [NOTFOUND=continue UNAVAIL=continue TRYAGAIN=continue] dns
 
# cat /etc/resolv.conf
cat: Cannot open /etc/resolv.conf: No such file or directory

In this case, the connection is slow.

In other cases, we have set the two files:

Code:
# cat etc/nsswitch.conf
hosts: files [NOTFOUND=continue UNAVAIL=continue TRYAGAIN=continue] dns
 
# cat resolv.conf
search LLL.com
nameserver XXX
nameserver YYY

In this case, the conection is slow, too.

I checked in the syslog.log i cannot see error related.

Thanks a lot,

Last edited by zaxxon; 10-30-2012 at 11:50 AM.. Reason: code tags, see PM
 

10 More Discussions You Might Find Interesting

1. BSD

ipfw slow ssh and ftp connections

just as the title says. thanks. #General Rule Sets /sbin/ipfw add 0300 check-state /sbin/ipfw add 0301 deny tcp from any to any in established /sbin/ipfw add 0302 pass tcp from any to any out setup keep-state /sbin/ipfw add 0303 pass udp from any to any out #SSH FTP /sbin/ipfw add 0400... (11 Replies)
Discussion started by: dwildgoose
11 Replies

2. UNIX for Dummies Questions & Answers

SSH and FTP connect slow

Hi again guys, Earlier today, just all of a sudden, all SSH and FTP connections to my internal Linux box just slowed down to a crawl. After the connection/authentication though, everything was back to normal speed. Until you have to connect again. A box reboot didnt work either. Now, from... (1 Reply)
Discussion started by: Aeros
1 Replies

3. UNIX for Dummies Questions & Answers

Painfully Slow SSH login on Solaris box

Running open solaris on a e420 that I recently picked up. Having issues sshing to it from either of my Linux boxes as its very slow to login (from the solaris box to the linux box it connects just fine. Here is the output of ssh -vvv. I have hightlighted where it seems the slowdown is. Does... (0 Replies)
Discussion started by: creedog
0 Replies

4. IP Networking

Samba Slow to Connect Xp to Solaris

Hi everyone, I posted this on the Solaris forums but so far no one has been able to help... I'm new to solaris and I've installed 10, update 5. I've configured samba (very badly I believe) so that I can access my solaris box from my XP 64 computer. Both are on a local network (connected via... (1 Reply)
Discussion started by: ciscocbee
1 Replies

5. Solaris

ssh very slow

I'm facing a problem when trying to ssh to SUN servers with solaris OS,it takes a long time until prompted for password ..after connecting to the server everything work fine..how can I solve this issue??? (11 Replies)
Discussion started by: mm00123
11 Replies

6. Solaris

Slow login via SSH

Hi Guys and Girls, I know this is a common question but I've searched and we've tried the suggestions without luck. When I log into the box via SSH from a windows machine I get a 1 min 20 sec delay. If we add my IP address and machine name to /etc/hosts then I get an instant login. I would be happy... (12 Replies)
Discussion started by: MikeKulls
12 Replies

7. Shell Programming and Scripting

Net::SSH::Perl slow to login.

I have some sample code that's supposed to ssh to another machine using Net::SSH::Perl, execute a command, and print the output of that command. It's very basic, and it works. However, I noticed that upon logging in: $ssh->login('username','password'); It takes roughly 10-13 seconds to... (2 Replies)
Discussion started by: mrwatkin
2 Replies

8. Solaris

Slow ssh connection after patching

I have Solaris-10 server which was patched by patch cluster last weekend. After patching, it connects slow with other server. Meaning, when I do - ssh server2 OR ssh wluser2@server2 OR ssh root@server2 It waits for 9-10 seconds and then prompt for password, while it used to be instant... (2 Replies)
Discussion started by: solaris_1977
2 Replies

9. SuSE

SLES 11.2 slow SSH password prompt

We are having an issue with slow password prompts via SSH login on all of our SLES 11.2 boxes. The output from a ssh -v login attempt shows a delay here: debug1: SSH2_MSG_SERVICE_ACCEPT receivedThis issue only happens on the first logon of the day; subsequent logons are normal. Adding the client's... (8 Replies)
Discussion started by: j_aix
8 Replies

10. Solaris

Slow ssh on Solaris 10 zone

ssh is slow on solaris zone , and is getting stuck at the following place. debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug3: Wrote 664 bytes for a total of 3325 Below is the ssh version being used: Sun_SSH_1.1.6, SSH protocols 1.5/2.0, OpenSSL 0x0090704f ... (10 Replies)
Discussion started by: skamal4u
10 Replies
NSSWITCH.CONF(5)					     Linux Programmer's Manual						  NSSWITCH.CONF(5)

NAME
nsswitch.conf - System Databases and Name Service Switch configuration file DESCRIPTION
Various functions in the C Library need to be configured to work correctly in the local environment. Traditionally, this was done by using files (e.g., `/etc/passwd'), but other nameservices (like the Network Information Service (NIS) and the Domain Name Service (DNS)) became popular, and were hacked into the C library, usually with a fixed search order. The Linux libc5 with NYS support and the GNU C Library 2.x (libc.so.6) contain a cleaner solution of this problem. It is designed after a method used by Sun Microsystems in the C library of Solaris 2. We follow their name and call this scheme "Name Service Switch" (NSS). The sources for the "databases" and their lookup order are specified in the /etc/nsswitch.conf file. The following databases are available in the NSS: aliases Mail aliases, used by sendmail(8). Presently ignored. ethers Ethernet numbers. group Groups of users, used by getgrent(3) functions. hosts Host names and numbers, used by gethostbyname(3) and similar functions. netgroup Network wide list of hosts and users, used for access rules. C libraries before glibc 2.1 only support netgroups over NIS. network Network names and numbers, used by getnetent(3) functions. passwd User passwords, used by getpwent(3) functions. protocols Network protocols, used by getprotoent(3) functions. publickey Public and secret keys for Secure_RPC used by NFS and NIS+. rpc Remote procedure call names and numbers, used by getrpcbyname(3) and similar functions. services Network services, used by getservent(3) functions. shadow Shadow user passwords, used by getspnam(3). An example /etc/nsswitch.conf (namely, the default used when /etc/nsswitch.conf is missing): passwd: compat group: compat shadow: compat hosts: dns [!UNAVAIL=return] files networks: nis [NOTFOUND=return] files ethers: nis [NOTFOUND=return] files protocols: nis [NOTFOUND=return] files rpc: nis [NOTFOUND=return] files services: nis [NOTFOUND=return] files The first column is the database. The rest of the line specifies how the lookup process works. You can specify the way it works for each database individually. The configuration specification for each database can contain two different items: * The service specification like `files', `db', or `nis'. * The reaction on lookup result like `[NOTFOUND=return]'. For libc5 with NYS, the allowed service specifications are `files', `nis', and `nisplus'. For hosts, you could specify `dns' as extra ser- vice, for passwd and group `compat', but not for shadow. For glibc, you must have a file called /lib/libnss_SERVICE.so.X for every SERVICE you are using. On a standard installation, you could use `files', `db', `nis', and `nisplus'. For hosts, you could specify `dns' as extra service, for passwd, group, and shadow `compat'. These services will not be used by libc5 with NYS. The version number X is 1 for glibc 2.0 and 2 for glibc 2.1. The second item in the specification gives the user much finer control on the lookup process. Action items are placed between two service names and are written within brackets. The general form is `[' ( `!'? STATUS `=' ACTION )+ `]' where STATUS => success | notfound | unavail | tryagain ACTION => return | continue The case of the keywords is insignificant. The STATUS values are the results of a call to a lookup function of a specific service. They mean: success No error occurred and the wanted entry is returned. The default action for this is `return'. notfound The lookup process works ok but the needed value was not found. The default action is `continue'. unavail The service is permanently unavailable. This can either mean the needed file is not available, or, for DNS, the server is not available or does not allow queries. The default action is `continue'. tryagain The service is temporarily unavailable. This could mean a file is locked or a server currently cannot accept more connections. The default action is `continue'. Interaction with +/- syntax (compat mode) Linux libc5 without NYS does not have the name service switch but does allow the user some policy control. In /etc/passwd you could have entries of the form +user or +@netgroup (include the specified user from the NIS passwd map), -user or -@netgroup (exclude the specified user), and + (include every user, except the excluded ones, from the NIS passwd map). Since most people only put a + at the end of /etc/passwd to include everything from NIS, the switch provides a faster alternative for this case (`passwd: files nis') which doesn't require the single + entry in /etc/passwd, /etc/group, and /etc/shadow. If this is not sufficient, the NSS `compat' service provides full +/- semantics. By default, the source is `nis', but this may be overriden by specifying `nisplus' as source for the pseudo-databases passwd_compat, group_compat and shadow_compat. This pseudo-databases are only available in GNU C Library. FILES
A service named SERVICE is implemented by a shared object library named libnss_SERVICE.so.X that resides in /lib. /etc/nsswitch.conf configuration file /lib/libnss_compat.so.X implements `compat' source for glibc2 /lib/libnss_db.so.X implements `db' source for glibc2 /lib/libnss_dns.so.X implements `dns' source for glibc2 /lib/libnss_files.so.X implements `files' source for glibc2 /lib/libnss_hesiod.so.X implements `hesiod' source for glibc2 /lib/libnss_nis.so.X implements `nis' source for glibc2 /lib/libnss_nisplus.so.2 implements `nisplus' source for glibc 2.1 NOTES
Within each process that uses nsswitch.conf, the entire file is read only once; if the file is later changed, the process will continue using the old configuration. With Solaris, it isn't possible to link programs using the NSS Service statically. With Linux, this is no problem. Linux 1999-01-17 NSSWITCH.CONF(5)
All times are GMT -4. The time now is 03:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy