4 ms·
I thought I saw something posted before that this is basically a bug in the ARC code that runs the site, or the underlying server daemon. I filed it in memory
by brk 17y ago
I thought I saw something posted before that this is basically a bug in the ARC code that runs the site, or the underlying server daemon. I filed it in memory (wet) as roughly a memory leak. There is a process that HUP's (something) whenever it happens.
My impression is that it's a known issue, and in the priority queue, but probably still ranks right behind other more pressing issues like deciding what's for dinner.
- jacquesm 17y agoThis thread: ? http://news.ycombinator.com/item?id=1049859 http://news.ycombinator.com/item?id=1049859 I mistook the RSTs for a socket without a listen so I thought the server was restarting, but the overflowing listen queue is more likely, especially in the light of riffers comment there. That means the server is still up but not accepting connections. iirc the default is something like 5 outstanding connections, that is a thing you could fairly easily remedy. It's bugging me because I see it happening more and more often. edit: irony, I had to submit this three times to get through...
- brk 17y agoNo, it was a different, much older comment. I think by pg. I see this about once/day (and I spend WAY too much time refreshing HN). Slightly surprised that you see it frequently enough to comment/inquire, guess it's just random luck :)
- jacquesm 17y ago> and I spend WAY too much time refreshing HN Errm, yes. I think I do too. > Slightly surprised that you see it frequently enough to comment/inquire, guess it's just random luck :) At least once per hour sometimes many more, at least 10 times per day.