{"action":"created","issue":{"url":"https://api.github.com/repos/monero-project/monero/issues/1035","repository_url":"https://api.github.com/repos/monero-project/monero","labels_url":"https://api.github.com/repos/monero-project/monero/issues/1035/labels{/name}","comments_url":"https://api.github.com/repos/monero-project/monero/issues/1035/comments","events_url":"https://api.github.com/repos/monero-project/monero/issues/1035/events","html_url":"https://github.com/monero-project/monero/issues/1035","id":174827066,"number":1035,"title":"Bitmonero stuck after many json request","user":{"login":"AJIekceu4","id":16595267,"avatar_url":"https://avatars.githubusercontent.com/u/16595267?v=3","gravatar_id":"","url":"https://api.github.com/users/AJIekceu4","html_url":"https://github.com/AJIekceu4","followers_url":"https://api.github.com/users/AJIekceu4/followers","following_url":"https://api.github.com/users/AJIekceu4/following{/other_user}","gists_url":"https://api.github.com/users/AJIekceu4/gists{/gist_id}","starred_url":"https://api.github.com/users/AJIekceu4/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AJIekceu4/subscriptions","organizations_url":"https://api.github.com/users/AJIekceu4/orgs","repos_url":"https://api.github.com/users/AJIekceu4/repos","events_url":"https://api.github.com/users/AJIekceu4/events{/privacy}","received_events_url":"https://api.github.com/users/AJIekceu4/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2016-09-02T19:00:38Z","updated_at":"2016-12-15T15:59:37Z","closed_at":null,"body":"Hello all. My server running 3 bitmonero instance with different ports: 13666,23666,33666.\n13666 and 23666 is Monero 'Hydrogen Helix' (v0.9.4.0-04906e6) version from **02.09.2016**\n33666 is Monero 'Hydrogen Helix' (v0.9.4.0-unknown) old version from **06.04.2016**\n\nI make json request to all 3 bitmonero via script (node js) every 50ms (20 times per second). And after some time 13666 and 23666 stop working (for some time). At this time - no error in console, but bitmonero did not answer to json request. Script and bitmonero connected via 127.0.0.1 (via internet problem also exist, already test it). I test it on 2 different servers with Ubuntu 16-04 and Ubuntu 14-04 (both have HDD in RAID 1) and problem exist on both.\n\nLog from bitmonero when problem exist:\nhttp://pastebin.com/raw/N473m6E1\n\nAlso i noticed that this bug appears at the same time on both 13666 and 23666 (they started in different time > 1 hours). You can see it on screenshots:\n\n![13666](https://cloud.githubusercontent.com/assets/16595267/18215072/34ac485c-7158-11e6-8d87-fe81b4108fd3.jpg)\n![23666](https://cloud.githubusercontent.com/assets/16595267/18215074/34ad585a-7158-11e6-8d70-51510b6627a4.jpg)\n![33666](https://cloud.githubusercontent.com/assets/16595267/18215073/34acfffe-7158-11e6-8140-64706bf10948.jpg)\n\nIf i manually use curl when bitmonero stuck:\n`curl -X POST http://127.0.0.1:13666/json_rpc -d '{\"jsonrpc\":\"2.0\",\"id\":\"0\",\"method\":\"getlastblockheader\"}' -H 'Content-Type: application/json'`\n\nAnd **after 60 seconds** get answer:\n`curl: (7) Failed to connect to 127.0.0.1 port 13666: Connection timed out`\n\nProblem exist if i run only 1 bitmonero instance on server (v0.9.4.0-04906e6). \nFirst time i notice this problem after i compile some previous release (from 03.05.2016 i think). **Anyway it was version in which blockchain mdb converted to new format (or something like this, because it promt info about convert)**. \n"},"comment":{"url":"https://api.github.com/repos/monero-project/monero/issues/comments/267364473","html_url":"https://github.com/monero-project/monero/issues/1035#issuecomment-267364473","issue_url":"https://api.github.com/repos/monero-project/monero/issues/1035","id":267364473,"user":{"login":"NanoAkron","id":6762681,"avatar_url":"https://avatars.githubusercontent.com/u/6762681?v=3","gravatar_id":"","url":"https://api.github.com/users/NanoAkron","html_url":"https://github.com/NanoAkron","followers_url":"https://api.github.com/users/NanoAkron/followers","following_url":"https://api.github.com/users/NanoAkron/following{/other_user}","gists_url":"https://api.github.com/users/NanoAkron/gists{/gist_id}","starred_url":"https://api.github.com/users/NanoAkron/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/NanoAkron/subscriptions","organizations_url":"https://api.github.com/users/NanoAkron/orgs","repos_url":"https://api.github.com/users/NanoAkron/repos","events_url":"https://api.github.com/users/NanoAkron/events{/privacy}","received_events_url":"https://api.github.com/users/NanoAkron/received_events","type":"User","site_admin":false},"created_at":"2016-12-15T15:59:37Z","updated_at":"2016-12-15T15:59:37Z","body":"Hi again @AJIekceu4 - is this an issue with the latest 0.10.1 with the most recent JSON correction?"}}
{"actor":{"display_login":"NanoAkron"}}