4 ms·
I'm confused, what exactly do you think is happening? Obviously individual EC2 instances run for years without being rebooted or having processes die or nobody
by nicpottier 14y ago
I'm confused, what exactly do you think is happening? Obviously individual EC2 instances run for years without being rebooted or having processes die or nobody would use it. (I've run services on EC2 since they first launched and have never had such issues)
What's your theory on why your screen instances are dying and how would EC2 be responsible for it?
- lkrubner 14y agoI really do not know. I have not had the time to investigate how and why this particular service might suffer so much on EC2. I do not know if our EC2 servies were suffering something that was unique to us, or whether this is a general problem with EC2. I do know that I was annoyed as hell. And I know I have not had this problem with other cloud services, such as the one offered by Rackspace.
- nicpottier 14y agoAre you sure it isn't just a difference in configuration or distribution that you are using? Hard to imagine how screen would be terribly unique here in uniquely misbehaving on EC2.
- mh- 14y agoyou never considered to check the uptime, dmesg?
- alexkus 14y agoAlso:- The contents of /var/run/screen/ and the "S-<username>" subdir that should be there... The output of "ps u" and "ps -ef | grep s[c]reen"