starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

nohup process terminates when terminal disconnects from ssh session #22352

New Issue
Open
opened 2026-01-31 08:10:39 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 08:10:39 +00:00
Owner
Copy Link

Originally created by @siddhsql on GitHub (Oct 5, 2024).

Windows Terminal version

1.20.11781.0

Windows build number

10.0.22631.4169

Other Software

No response

Steps to reproduce

  1. ssh to a remote machine from the Windows terminal
  2. run a program (e.g., a node process that spins up a server listening to connections) like nohup npm run &

leave terminal connected. after some period of inactivity (could be few hours) terminal will disconnect (broken pipe) as machine could go to sleep etc.

When this happens the program you started on the remote machine also terminates.

Expected Behavior

program you started on the remote machine should keep running.

Actual Behavior

program you started on the remote machine terminates. Note this does not happen if you exit from the ssh session by typing the exit command vs. leaving the terminal connected and it disconnects due to inactivity. if it helps, on Mac (with iTerm), the problem does not happen when leaving the terminal connected and it disconnects due to inactivity

Originally created by @siddhsql on GitHub (Oct 5, 2024). ### Windows Terminal version 1.20.11781.0 ### Windows build number 10.0.22631.4169 ### Other Software _No response_ ### Steps to reproduce 1. ssh to a remote machine from the Windows terminal 2. run a program (e.g., a node process that spins up a server listening to connections) like `nohup npm run &` leave terminal connected. after some period of inactivity (could be few hours) terminal will disconnect (broken pipe) as machine could go to sleep etc. When this happens the program you started on the remote machine also terminates. ### Expected Behavior program you started on the remote machine should keep running. ### Actual Behavior program you started on the remote machine terminates. _Note this does not happen if you exit from the ssh session by typing the `exit` command vs. leaving the terminal connected and it disconnects due to inactivity_. if it helps, on Mac (with iTerm), the problem does not happen when leaving the terminal connected and it disconnects due to inactivity
claunia added the Issue-BugNeeds-Tag-FixNeeds-ReproProduct-Terminal labels 2026-01-31 08:10:39 +00:00
claunia commented 2026-01-31 08:10:40 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 5, 2024):

Are you using ssh from within WSL, or the native Windows build of ssh?

@DHowett commented on GitHub (Oct 5, 2024): Are you using ssh from within WSL, or the native Windows build of ssh?
claunia commented 2026-01-31 08:10:41 +00:00
Author
Owner
Copy Link

@siddhsql commented on GitHub (Oct 5, 2024):

I have tried both.

  1. ssh from Windows (no WSL)
  2. ssh from WSL using /usr/bin/ssh
@siddhsql commented on GitHub (Oct 5, 2024): I have tried both. 1. ssh from Windows (no WSL) 2. ssh from WSL using `/usr/bin/ssh`
claunia commented 2026-01-31 08:10:41 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 7, 2024):

I just tried this with my own Linux server from Windows 11 24H2. After disconnecting the network, the process kept running in the background while SSH had exited.

What I suspect is happening is that your server is receiving a signal other than SIGHUP. nohup only catches that one signal and any other signal will still cause node to exit.

As an immediate workaround, I'd suggest either changing your command to npm run &; disown or to use a multiplexer like tmux or zellij. With tmux for instance, you first launch it by running tmux, then you execute your command npm run. No matter what happens now, that tmux and npm instance will keep running forever. You can explicitly detach from it by pressing Ctrl+B, D. You can reattach again by running tmux attach. zellij works similar but is a lot more beginner friendly.

@lhecker commented on GitHub (Oct 7, 2024): I just tried this with my own Linux server from Windows 11 24H2. After disconnecting the network, the process kept running in the background while SSH had exited. What I suspect is happening is that your server is receiving a signal other than SIGHUP. `nohup` only catches that one signal and any other signal will still cause `node` to exit. As an immediate workaround, I'd suggest either changing your command to `npm run &; disown` or to use a multiplexer like `tmux` or `zellij`. With `tmux` for instance, you first launch it by running `tmux`, then you execute your command `npm run`. No matter what happens now, that `tmux` and `npm` instance will keep running forever. You can explicitly detach from it by pressing `Ctrl+B, D`. You can reattach again by running `tmux attach`. `zellij` works similar but is a lot more beginner friendly.
claunia commented 2026-01-31 08:10:42 +00:00
Author
Owner
Copy Link

@siddhsql commented on GitHub (Oct 7, 2024):

Thanks Leonard. re: this:

After disconnecting the network, the process kept running in the background while SSH had exited.

could you be specific how you disconnected from the network? If I disconnect by explicitly exiting from the ssh session using the exit command, the process does keep running. I encounter the issue when the session terminates/disconnects because of prolonged inactivity (Broken Pipe). Did you repro that?

@siddhsql commented on GitHub (Oct 7, 2024): Thanks Leonard. re: this: >After disconnecting the network, the process kept running in the background while SSH had exited. could you be specific how you disconnected from the network? If I disconnect by explicitly exiting from the ssh session using the `exit` command, the process does keep running. I encounter the issue when the session terminates/disconnects because of prolonged inactivity (Broken Pipe). Did you repro that?
claunia commented 2026-01-31 08:10:42 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 9, 2024):

I disabled the network adapter. I hoped that this would be similar to what you experienced.

@lhecker commented on GitHub (Oct 9, 2024): I disabled the network adapter. I hoped that this would be similar to what you experienced.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Repro Needs-Tag-Fix Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22352
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?