{"action":"created","issue":{"url":"https://api.github.com/repos/AUTUpStageTeam/UpStage/issues/256","labels_url":"https://api.github.com/repos/AUTUpStageTeam/UpStage/issues/256/labels{/name}","comments_url":"https://api.github.com/repos/AUTUpStageTeam/UpStage/issues/256/comments","events_url":"https://api.github.com/repos/AUTUpStageTeam/UpStage/issues/256/events","html_url":"https://github.com/AUTUpStageTeam/UpStage/issues/256","id":47762160,"number":256,"title":"\"too many open files\" bug","user":{"login":"helenvarley","id":3437324,"avatar_url":"https://avatars.githubusercontent.com/u/3437324?v=3","gravatar_id":"","url":"https://api.github.com/users/helenvarley","html_url":"https://github.com/helenvarley","followers_url":"https://api.github.com/users/helenvarley/followers","following_url":"https://api.github.com/users/helenvarley/following{/other_user}","gists_url":"https://api.github.com/users/helenvarley/gists{/gist_id}","starred_url":"https://api.github.com/users/helenvarley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/helenvarley/subscriptions","organizations_url":"https://api.github.com/users/helenvarley/orgs","repos_url":"https://api.github.com/users/helenvarley/repos","events_url":"https://api.github.com/users/helenvarley/events{/privacy}","received_events_url":"https://api.github.com/users/helenvarley/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/AUTUpStageTeam/UpStage/labels/bug","name":"bug","color":"f7c6c7"},{"url":"https://api.github.com/repos/AUTUpStageTeam/UpStage/labels/HIGH","name":"HIGH","color":"e11d21"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2014-11-04T20:38:34Z","updated_at":"2015-06-10T11:26:06Z","closed_at":"2015-06-10T11:26:06Z","body":"today we had a situation where none of us (5 people) could enter http://upstage.org.nz:8083/ - we were all getting the error message \"too many open files\" (see attached image). this has happened in the past but usually to only one person at a time, & reloading solves it. this time it happened to all of us who were trying to enter, & not only the stages but everything past the home page, & it continued for some time. mem reported it last night, i checked & was able to enter, but this morning could not & nobody could.\r\n\r\npaul has restarted the instance as a temporary fix, but said to log it as a high priority bug, saying \"This happens when connections aren't closed properly. It's a combination of a Linux security feature and poor connection handling in UpStage code. I CAN increase the limit at the OS level, but the BEST solution is to fix the code - think of it as a memory leak of sorts.\"\r\n\r\n![toomanyopenfiles](https://cloud.githubusercontent.com/assets/3437324/4907547/79811e8a-6462-11e4-9d85-451f03061a44.jpg)\r\n"},"comment":{"url":"https://api.github.com/repos/AUTUpStageTeam/UpStage/issues/comments/110706233","html_url":"https://github.com/AUTUpStageTeam/UpStage/issues/256#issuecomment-110706233","issue_url":"https://api.github.com/repos/AUTUpStageTeam/UpStage/issues/256","id":110706233,"user":{"login":"yue-l","id":5555033,"avatar_url":"https://avatars.githubusercontent.com/u/5555033?v=3","gravatar_id":"","url":"https://api.github.com/users/yue-l","html_url":"https://github.com/yue-l","followers_url":"https://api.github.com/users/yue-l/followers","following_url":"https://api.github.com/users/yue-l/following{/other_user}","gists_url":"https://api.github.com/users/yue-l/gists{/gist_id}","starred_url":"https://api.github.com/users/yue-l/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yue-l/subscriptions","organizations_url":"https://api.github.com/users/yue-l/orgs","repos_url":"https://api.github.com/users/yue-l/repos","events_url":"https://api.github.com/users/yue-l/events{/privacy}","received_events_url":"https://api.github.com/users/yue-l/received_events","type":"User","site_admin":false},"created_at":"2015-06-10T11:26:06Z","updated_at":"2015-06-10T11:26:06Z","body":"This happens when issues occur during server deployment processes.\r\nCurrently UpStage server does not suffer this situation."}}