{"action":"opened","issue":{"url":"https://api.github.com/repos/ethereum/go-ethereum/issues/3254","repository_url":"https://api.github.com/repos/ethereum/go-ethereum","labels_url":"https://api.github.com/repos/ethereum/go-ethereum/issues/3254/labels{/name}","comments_url":"https://api.github.com/repos/ethereum/go-ethereum/issues/3254/comments","events_url":"https://api.github.com/repos/ethereum/go-ethereum/issues/3254/events","html_url":"https://github.com/ethereum/go-ethereum/issues/3254","id":188850478,"number":3254,"title":"Windows: not getting new blocks (stuck at 2609182)","user":{"login":"SCBuergel","id":11379673,"avatar_url":"https://avatars.githubusercontent.com/u/11379673?v=3","gravatar_id":"","url":"https://api.github.com/users/SCBuergel","html_url":"https://github.com/SCBuergel","followers_url":"https://api.github.com/users/SCBuergel/followers","following_url":"https://api.github.com/users/SCBuergel/following{/other_user}","gists_url":"https://api.github.com/users/SCBuergel/gists{/gist_id}","starred_url":"https://api.github.com/users/SCBuergel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SCBuergel/subscriptions","organizations_url":"https://api.github.com/users/SCBuergel/orgs","repos_url":"https://api.github.com/users/SCBuergel/repos","events_url":"https://api.github.com/users/SCBuergel/events{/privacy}","received_events_url":"https://api.github.com/users/SCBuergel/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-11T21:04:19Z","updated_at":"2016-11-11T21:04:19Z","closed_at":null,"body":"I am running the latest geth 1.4.18 from github release binary on Windows 7. I synced the chain initially via `geth --fast console` and realized that my geth seems to get to know about updated blocks only very rarely despite the fact that geth is chatting a lot about incoming blocks, so this does not seem to be a connectivity issue. I am checking for new blocks via `web3.eth.blockNumer` and that number stayed constant for a very long time despite new blocks showing up in the console, see exemple below. The same behavior persists now that I am running it without `--fast`, actually it seems worse because I dont see any new blockNumber anymore:\r\n```\r\n> web3.eth.blockNumber\r\n2609182\r\n> I1111 21:59:08.754610 core/blockchain.go:1001] imported 163 block(s) (0 queued\r\n 0 ignored) including 126 txs in 8.0125174s. #80574 [5e66bdd6 / fc3bb229]\r\nI1111 21:59:16.758126 core/blockchain.go:1001] imported 636 block(s) (0 queued 0\r\n ignored) including 497 txs in 8.0035163s. #81210 [fc3bb229 / bfd7ca5a]\r\nI1111 21:59:24.892659 core/blockchain.go:1001] imported 579 block(s) (0 queued 0\r\n ignored) including 350 txs in 8.134533s. #81789 [bfd7ca5a / c9dddebd]\r\nI1111 21:59:32.909177 core/blockchain.go:1001] imported 654 block(s) (0 queued 0\r\n ignored) including 257 txs in 8.016518s. #82443 [c9dddebd / d612896f]\r\nI1111 21:59:33.039693 core/blockchain.go:1001] imported 16 block(s) (0 queued 0\r\nignored) including 10 txs in 130.5165ms. #82459 [d612896f / a89a8504]\r\n> web3.eth.blockNumber\r\n2609182\r\n```"}}
{"actor":{"display_login":"SCBuergel"}}