{"action":"created","issue":{"url":"https://api.github.com/repos/paritytech/parity/issues/9136","repository_url":"https://api.github.com/repos/paritytech/parity","labels_url":"https://api.github.com/repos/paritytech/parity/issues/9136/labels{/name}","comments_url":"https://api.github.com/repos/paritytech/parity/issues/9136/comments","events_url":"https://api.github.com/repos/paritytech/parity/issues/9136/events","html_url":"https://github.com/paritytech/parity/issues/9136","id":341568227,"node_id":"MDU6SXNzdWUzNDE1NjgyMjc=","number":9136,"title":"Major upgrade of network is impossible","user":{"login":"Pzixel","id":11201122,"node_id":"MDQ6VXNlcjExMjAxMTIy","avatar_url":"https://avatars3.githubusercontent.com/u/11201122?v=4","gravatar_id":"","url":"https://api.github.com/users/Pzixel","html_url":"https://github.com/Pzixel","followers_url":"https://api.github.com/users/Pzixel/followers","following_url":"https://api.github.com/users/Pzixel/following{/other_user}","gists_url":"https://api.github.com/users/Pzixel/gists{/gist_id}","starred_url":"https://api.github.com/users/Pzixel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Pzixel/subscriptions","organizations_url":"https://api.github.com/users/Pzixel/orgs","repos_url":"https://api.github.com/users/Pzixel/repos","events_url":"https://api.github.com/users/Pzixel/events{/privacy}","received_events_url":"https://api.github.com/users/Pzixel/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-16T15:30:58Z","updated_at":"2018-07-16T16:07:34Z","closed_at":null,"author_association":"NONE","body":"> I'm running:\r\n>\r\n> - **Which Parity version?**: 1.7.7\r\n> - **Which operating system?**: Linux\r\n> - **How installed?**: docker\r\n> - **Are you fully synchronized?**: yes\r\n> - **Which network are you connected to?**: ethereum\r\n> - **Did you try to restart the node?**: yes\r\n\r\nI'm trying to update my network to 1.10. To perform such a conversion I updated docker image one one machine and changed `chains.json`:\r\n\r\n![image](https://user-images.githubusercontent.com/11201122/42767300-46f76fbe-8925-11e8-8e37-fc8c98807d17.png)\r\n\r\n_I merely moved `gasLimitBoundDivisor` to the new location_\r\n\r\nWhen I start the node it outputs following:\r\n\r\n```text\r\nauthority1_1  | Loading config file from /parity/config/authority.toml\r\nauthority1_1  | 2018-07-16 10:34:05 UTC Parity browser interface is deprecated. It's going to be removed in the next version, use standalone Parity UI instead.\r\nauthority1_1  | 2018-07-16 10:34:05 UTC Standalone Parity UI: https://github.com/Parity-JS/shell/releases\r\nauthority1_1  | 2018-07-16 10:34:05 UTC Starting Parity/v1.10.9-stable-23a9eef-20180707/x86_64-linux-gnu/rustc1.27.0\r\nauthority1_1  | 2018-07-16 10:34:05 UTC Keys path /root/.local/share/io.parity.ethereum/keys/MyApp\r\nauthority1_1  | 2018-07-16 10:34:05 UTC DB path /root/.local/share/io.parity.ethereum/chains/MyApp/db/8b02f6358e5c34ac\r\nauthority1_1  | 2018-07-16 10:34:05 UTC Path to dapps /root/.local/share/io.parity.ethereum/dapps\r\nauthority1_1  | 2018-07-16 10:34:05 UTC State DB configuration: fast\r\nauthority1_1  | 2018-07-16 10:34:05 UTC Operating mode: active\r\nauthority1_1  | 2018-07-16 10:34:06 UTC Configured for MyApp using AuthorityRound engine\r\n```\r\n\r\nAnd it fails to reconnect to the network.\r\n\r\nI don't see any tutorials with step-by-step explanation of how to migrate existing network to new parity versions (they say that I have to migrate because older versions are unsupported so I can't stick with them) so they probably should be there. Any suggestions for how to fix it would be appreciated."},"comment":{"url":"https://api.github.com/repos/paritytech/parity/issues/comments/405299500","html_url":"https://github.com/paritytech/parity/issues/9136#issuecomment-405299500","issue_url":"https://api.github.com/repos/paritytech/parity/issues/9136","id":405299500,"node_id":"MDEyOklzc3VlQ29tbWVudDQwNTI5OTUwMA==","user":{"login":"Tbaut","id":33178835,"node_id":"MDQ6VXNlcjMzMTc4ODM1","avatar_url":"https://avatars2.githubusercontent.com/u/33178835?v=4","gravatar_id":"","url":"https://api.github.com/users/Tbaut","html_url":"https://github.com/Tbaut","followers_url":"https://api.github.com/users/Tbaut/followers","following_url":"https://api.github.com/users/Tbaut/following{/other_user}","gists_url":"https://api.github.com/users/Tbaut/gists{/gist_id}","starred_url":"https://api.github.com/users/Tbaut/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Tbaut/subscriptions","organizations_url":"https://api.github.com/users/Tbaut/orgs","repos_url":"https://api.github.com/users/Tbaut/repos","events_url":"https://api.github.com/users/Tbaut/events{/privacy}","received_events_url":"https://api.github.com/users/Tbaut/received_events","type":"User","site_admin":false},"created_at":"2018-07-16T16:07:34Z","updated_at":"2018-07-16T16:07:34Z","author_association":"COLLABORATOR","body":"Why did you change the `chains.json`? The new docker should have the right one. Is there any other error that could help us understand what happened (launching with `-l debug` for instance)? "}}
{"actor":{"display_login":"Tbaut"}}