Closed lzamparo closed 8 years ago
I would recommend to use a screen
or tmux
session for this purpose. Even when your ssh times out the interactive session will stay active within screen
or tmux
. I don't think there is a way to get back to your interactive job otherwise.
Yes to the comment above and what is timing out your SSH? We don't do that.
Good question on re-attaching. I believe you've lost the tty that would make that possible. One moment while I look.
@akahles ok thanks, I'll delete and resubmit (sigh).
@tatarsky I don't know what is timing out my SSH session, could it be some default of my client on OSX? My ~/.ssh/config has nothing set in this regard. Should I explicitly set something like ServerAliveInterval
? Also, any idea if qrerun
would recover an active queue session that had not yet launched?
Why would you want to recover an active queue session that had not yet launched? I believe that the benefit in priority through Q-time is minimal.
I tend to use ServerAliveInterval 60 when some middle box is doing idle packet based termination.
I don't know what qrerun does with an interactive qsub. The tty I believe needs to be still attached to the shell.
Ok, I'll kill the job and resubmit. Thx.
@akahles queuetime is not a factor in queue priority in the current config IIRC.
@tatarsky thanks for clarifying. Then I see no disadvantage in just resubmitting the job, as it had not started yet.
Yeah, just killed + resubmitted and am learning tmux to avoid this in the future
Hi,
Say I have a job enqueued in the active queue that's waiting to start:
However, since it had been waiting for multiple hours without actually starting, my terminal session timed out and was prematurely ended:
If I ssh back into hal, is there any way to salvage this actively enqueued job? I'm not so familiar with the torque tools, but surely there is a way?
Thanks,