Re: [CentOS] sidekiq receives SIGHUP when started via ssh -t

2017-10-18 Thread Yuri Kanivetsky
Hi, I've just found the reason. From what I can see, on the server the process received SIGHUP right after fork. It had no time to switch to new session and detach from controlling terminal. And to work around that one might add sleep to the end: ssh u...@example.com -t '. ~/.bash_profile && rvm

Re: [CentOS] sidekiq receives SIGHUP when started via ssh -t

2017-10-16 Thread Yuri Kanivetsky
Hi, I was able to narrow it down to this ruby script: #!/usr/bin/env ruby Process.daemon while true sleep 1 end And I can reproduce it on one particular CentOS server, on the other CentOS server it works as on Ubuntu. The CentOS server where I can reproduce the issue is supposed to have

[CentOS] sidekiq receives SIGHUP when started via ssh -t

2017-10-13 Thread Yuri Kanivetsky
Hi, I have a couple of ideas how to fix it, but I'm trying to figure out what's going on first. I mainly start this program (sidekiq) on Debian systems, and it might be my first time running it under CentOS, so my conjecture is that it has to do with differences between distributions... Now then,