Sponsored Content
Operating Systems HP-UX Users getting kicked out of sessions Post 302756641 by vbe on Wednesday 16th of January 2013 08:25:53 AM
Old 01-16-2013
ssh has by default some timeout configured... I cant remember where though... So was ssh introduced in replacement of telnet at the time first issues appeared?
I can t remember well of the issue but it seemed to happen on solaris connection when connecting to HP boxes...
I never had any issues of the sort from my PC (with RX...) or between HP boxes unless there was a TIMEOUT set somewhere ( like /etc/profile...).
I have more vicious issues that looks similar to you but are random, since I cant explain ( Im no network engineer) though I know the cause I cant get anthing done about it: Network team have started to use probe devices... and when they get on a server they act almost like a hacker... scanning all ports etc... finally if a server has NFS on it, it goes bezeurk...
So NFS can also cause such issues ( tranfer of huge files... )

Look if you cant monitor your network devices on your box...

Last edited by vbe; 01-16-2013 at 09:40 AM..
 

10 More Discussions You Might Find Interesting

1. Programming

C programming sessions

Hey guys, i'm in trouble, i'm high school teacher, and a student ask me for help, he want's to know where he can study C language for his application exam. Somebody could help us? (1 Reply)
Discussion started by: eleia
1 Replies

2. AIX

Locking a file when using VI to prevent multiple-edit sessions by diff users

At the office, we often have to edit one file with VI. We are 4-6 workers doing it and sometimes can be done at the same time. We have found a problem and want to prevent it with a file lock. Is it possible and how ? problem : Worker-a starts edit VI session on File-A at 1PM Worker-b... (14 Replies)
Discussion started by: Browser_ice
14 Replies

3. AIX

Users Are Getting Kicked out of 2Hr Sessions

:confused:We've had close to 100 calls about users logging into our AIX server. The users open up about 3 to 5 sessions in the server. After 2hrs of idle time, users are frozen or stuck in the IBM UniVerse Application. We (system administrators) have been blaming the application (which we'll take... (2 Replies)
Discussion started by: Sarccastik Dude
2 Replies

4. Solaris

Password accepted but kicked out

The Sun Solaris x86 system seemed to accept my username and password when I do SSH, but then the login prompt went away or hang. What happened? (8 Replies)
Discussion started by: conandor
8 Replies

5. Solaris

Switching between sessions

Unix sys admin in training here and I was performing a rollout of java code. While rolling out my connection to the server was broken. I logged back on to the box and performed a ps -ef | grep 'user' . I could see that session and pid number. My question is was there anyway to resume or... (1 Reply)
Discussion started by: vedder191
1 Replies

6. AIX

Users kicked out after changing their password in an ssh session

Hi I have experienced this for years and just put up with it. However a client of mine now wants to stop this happening to their users. I have scoured the internet but can find no reference to the problem. I tried switching to PAM authentication thinking this might help but it made no... (6 Replies)
Discussion started by: johnf
6 Replies

7. Solaris

To restrict the users not to change the passwords for NIS users

Hi All, How to restrict the NIS users not to change their passwords in for NIS users?? and my NIS user is unable to login to at client location what could be the problem for this ? Any body can help me. Thanks in advance. (1 Reply)
Discussion started by: Sharath Kumar
1 Replies

8. Shell Programming and Scripting

Kill sessions

Hi , I am connecting to the linux redhat machine as user : APPS I would like to know how i can kill -9 , all APPS sessions beside me . Please advice Thanks (2 Replies)
Discussion started by: yoavbe
2 Replies

9. Shell Programming and Scripting

Create multiple users with individual passwords to users

hi, i am new to shell scripts i write a shell script to create multiple users but i need to give passwords to that users while creating users, command to write this script (1 Reply)
Discussion started by: DONFOX
1 Replies

10. AIX

Telnet sessions stay as idle users

Hi The telnet sessions stay as idle users. It is not getting kicked out. Please advise what could be the issue. only when we reboot the server these telnet sessions goes. Below is the current output from the server. we rebooted the server three days ago: pmut6:/> uptime 04:21PM... (8 Replies)
Discussion started by: newtoaixos
8 Replies
Smokeping_probes_SSH(3) 					     SmokePing						   Smokeping_probes_SSH(3)

NAME
Smokeping::probes::SSH - Secure Shell Probe for SmokePing SYNOPSIS
*** Probes *** +SSH binary = /usr/bin/ssh-keyscan # mandatory forks = 5 offset = 50% step = 300 timeout = 15 # The following variables can be overridden in each target section keytype = dsa pings = 5 port = 5000 # [...] *** Targets *** probe = SSH # if this should be the default probe # [...] + mytarget # probe = SSH # if the default probe is something else host = my.host keytype = dsa pings = 5 port = 5000 DESCRIPTION
Integrates ssh-keyscan as a probe into smokeping. The variable binary must point to your copy of the ssh-keyscan program. If it is not installed on your system yet, you should install openssh >= 3.8p1 The Probe asks the given host n-times for it's public key, where n is the amount specified in the config File. As part of the initialization, the probe asks 127.0.0.1 for it's public key and tries to parse the output. Make sure you have SSH running on the localhost as well. VARIABLES
Supported probe-specific variables: binary The location of your ssh-keyscan binary. Example value: /usr/bin/ssh-keyscan This setting is mandatory. forks Run this many concurrent processes at maximum Example value: 5 Default value: 5 offset If you run many probes concurrently you may want to prevent them from hitting your network all at the same time. Using the probe- specific offset parameter you can change the point in time when each probe will be run. Offset is specified in % of total interval, or alternatively as 'random', and the offset from the 'General' section is used if nothing is specified here. Note that this does NOT influence the rrds itself, it is just a matter of when data acqusition is initiated. (This variable is only applicable if the variable 'concurrentprobes' is set in the 'General' section.) Example value: 50% step Duration of the base interval that this probe should use, if different from the one specified in the 'Database' section. Note that the step in the RRD files is fixed when they are originally generated, and if you change the step parameter afterwards, you'll have to delete the old RRD files or somehow convert them. (This variable is only applicable if the variable 'concurrentprobes' is set in the 'General' section.) Example value: 300 timeout How long a single 'ping' takes at maximum Example value: 15 Default value: 5 Supported target-specific variables: keytype Type of key, used in ssh-keyscan -t keytype Example value: dsa Default value: rsa pings How many pings should be sent to each target, if different from the global value specified in the Database section. Note that the number of pings in the RRD files is fixed when they are originally generated, and if you change this parameter afterwards, you'll have to delete the old RRD files or somehow convert them. Example value: 5 port Port to use when testing the ssh connection -p port Example value: 5000 Default value: 22 AUTHORS
Christian Recktenwald <smokeping-contact@citecs.de> 2.6.8 2013-03-17 Smokeping_probes_SSH(3)
All times are GMT -4. The time now is 07:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy