- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: ssh hang
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2004 07:54 AM
11-22-2004 07:54 AM
1. Login to server A - either telnet, CDE, etc
2. ssh to server B - "ssh serverB"
3. Run a swinstall or launch an application
4. Exit from server b - either "exit" or "ctrl D"
While exiting server B the terminal session hangs and never returns to the command prompt on server A. You then need to kill the session on server B. After killing the session you are returned to a command prompt on server A. This only happens if you launch a daemon, start an application, or install a new application via swinstall. Other standard commands like cd ,mkdir, cat, etc. work fine. I think it has something to do with associating a process with a tty then trying to exit but am not sure. Any Ideas? Any help would be appreciated?
Thanks
Ray
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2004 08:00 AM
11-22-2004 08:00 AM
SolutionDid you leave a active process running over there on serverB
http://www.openssh.com/faq.html#3.10
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2004 08:26 AM
11-22-2004 08:26 AM
Re: ssh hang
Yes gernerally there is always a process such as a daemon started beforethe exit occurs. I will take a look at the link you provided.
Thanks!
Ray
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2004 08:27 AM
11-22-2004 08:27 AM
Re: ssh hang
Sorry for mis-spelling your name!!
Ray
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2004 11:05 PM
12-15-2004 11:05 PM
Re: ssh hang
Try recent version of HP Secure Shell ( A.03.81.002). I tried out your scenario but it worked correctly for me.
I tried the following
# ssh sonnet
# sleep 20 &
[1] 7904
# exit
You have running jobs
# ctrl + D
logout root
Connection to sonnet closed.
#
--
M
logout root
Connection to sonnet closed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2005 07:53 AM
02-16-2005 07:53 AM
Re: ssh hang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2005 08:48 AM
02-16-2005 08:48 AM
Re: ssh hang
exec > /dev/null < /dev/null 2>&1
Here is a sample script that illustrates how to place the entry into a script. The return code can be anything you want. We used 3 to help prove we could capture the return code we were looking for.
#!/bin/sh
exec > /dev/null < /dev/null 2>&1
sleep 30 &
return 3