Upgrading core protocol version (docker quickstart, standalone)

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I built the v10 docker image and launched it exposing the HTTP port for core.



docker build -f Dockerfile.testing -t stellar:v10 .
docker run --rm -it -p "5432:5432" -p "8000:8000" -p "11626:11626"
--name stellar stellar:v10 --standalone


At launch, the protocol version is 0.



I then attempted to update the protocol.



curl "http://localhost:11626/upgrades?mode=set&protocolversion=10&upgradetime=2018-08-18T00:00:00Z"


The upgrades endpoint now reports v10.



curl http://localhost:11626/upgrades?mode=get

"time": 1534550400,
"version":
"has": true,
"val": 10
,
"fee":
"has": false
,
"maxtxsize":
"has": false
,
"reserve":
"has": false




But the most recent ledger does not:



curl -s "http://localhost:8000/ledgers?cursor=now&limit=1&order=desc" 
| jq '._embedded.records[0].protocol_version'
0


The system in this state does not support any non v0 operation (after limited testing).



What are the additional steps to upgrading the protocol version?







share|improve this question
























    up vote
    1
    down vote

    favorite












    I built the v10 docker image and launched it exposing the HTTP port for core.



    docker build -f Dockerfile.testing -t stellar:v10 .
    docker run --rm -it -p "5432:5432" -p "8000:8000" -p "11626:11626"
    --name stellar stellar:v10 --standalone


    At launch, the protocol version is 0.



    I then attempted to update the protocol.



    curl "http://localhost:11626/upgrades?mode=set&protocolversion=10&upgradetime=2018-08-18T00:00:00Z"


    The upgrades endpoint now reports v10.



    curl http://localhost:11626/upgrades?mode=get

    "time": 1534550400,
    "version":
    "has": true,
    "val": 10
    ,
    "fee":
    "has": false
    ,
    "maxtxsize":
    "has": false
    ,
    "reserve":
    "has": false




    But the most recent ledger does not:



    curl -s "http://localhost:8000/ledgers?cursor=now&limit=1&order=desc" 
    | jq '._embedded.records[0].protocol_version'
    0


    The system in this state does not support any non v0 operation (after limited testing).



    What are the additional steps to upgrading the protocol version?







    share|improve this question






















      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I built the v10 docker image and launched it exposing the HTTP port for core.



      docker build -f Dockerfile.testing -t stellar:v10 .
      docker run --rm -it -p "5432:5432" -p "8000:8000" -p "11626:11626"
      --name stellar stellar:v10 --standalone


      At launch, the protocol version is 0.



      I then attempted to update the protocol.



      curl "http://localhost:11626/upgrades?mode=set&protocolversion=10&upgradetime=2018-08-18T00:00:00Z"


      The upgrades endpoint now reports v10.



      curl http://localhost:11626/upgrades?mode=get

      "time": 1534550400,
      "version":
      "has": true,
      "val": 10
      ,
      "fee":
      "has": false
      ,
      "maxtxsize":
      "has": false
      ,
      "reserve":
      "has": false




      But the most recent ledger does not:



      curl -s "http://localhost:8000/ledgers?cursor=now&limit=1&order=desc" 
      | jq '._embedded.records[0].protocol_version'
      0


      The system in this state does not support any non v0 operation (after limited testing).



      What are the additional steps to upgrading the protocol version?







      share|improve this question












      I built the v10 docker image and launched it exposing the HTTP port for core.



      docker build -f Dockerfile.testing -t stellar:v10 .
      docker run --rm -it -p "5432:5432" -p "8000:8000" -p "11626:11626"
      --name stellar stellar:v10 --standalone


      At launch, the protocol version is 0.



      I then attempted to update the protocol.



      curl "http://localhost:11626/upgrades?mode=set&protocolversion=10&upgradetime=2018-08-18T00:00:00Z"


      The upgrades endpoint now reports v10.



      curl http://localhost:11626/upgrades?mode=get

      "time": 1534550400,
      "version":
      "has": true,
      "val": 10
      ,
      "fee":
      "has": false
      ,
      "maxtxsize":
      "has": false
      ,
      "reserve":
      "has": false




      But the most recent ledger does not:



      curl -s "http://localhost:8000/ledgers?cursor=now&limit=1&order=desc" 
      | jq '._embedded.records[0].protocol_version'
      0


      The system in this state does not support any non v0 operation (after limited testing).



      What are the additional steps to upgrading the protocol version?









      share|improve this question











      share|improve this question




      share|improve this question










      asked Aug 17 at 21:19









      Synesso♦

      1,751221




      1,751221




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          3
          down vote



          accepted










          I think the date that you used is in the future 1534550400 = Saturday, August 18, 2018 12:00:00 AM.



          if you want it to happen right away, just use the epoch as per the documentation it's 1970-01-01T00:00:00Z






          share|improve this answer




















          • Thank you. That makes sense. I changed it to one minute in the future as a test and it updated correctly at the right time.
            – Synesso♦
            Aug 17 at 22:48







          • 1




            Update to docs to clarify that param. github.com/stellar/stellar-core/pull/1759
            – Synesso♦
            Aug 17 at 23:00










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "686"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          noCode: true, onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );








           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstellar.stackexchange.com%2fquestions%2f1474%2fupgrading-core-protocol-version-docker-quickstart-standalone%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          3
          down vote



          accepted










          I think the date that you used is in the future 1534550400 = Saturday, August 18, 2018 12:00:00 AM.



          if you want it to happen right away, just use the epoch as per the documentation it's 1970-01-01T00:00:00Z






          share|improve this answer




















          • Thank you. That makes sense. I changed it to one minute in the future as a test and it updated correctly at the right time.
            – Synesso♦
            Aug 17 at 22:48







          • 1




            Update to docs to clarify that param. github.com/stellar/stellar-core/pull/1759
            – Synesso♦
            Aug 17 at 23:00














          up vote
          3
          down vote



          accepted










          I think the date that you used is in the future 1534550400 = Saturday, August 18, 2018 12:00:00 AM.



          if you want it to happen right away, just use the epoch as per the documentation it's 1970-01-01T00:00:00Z






          share|improve this answer




















          • Thank you. That makes sense. I changed it to one minute in the future as a test and it updated correctly at the right time.
            – Synesso♦
            Aug 17 at 22:48







          • 1




            Update to docs to clarify that param. github.com/stellar/stellar-core/pull/1759
            – Synesso♦
            Aug 17 at 23:00












          up vote
          3
          down vote



          accepted







          up vote
          3
          down vote



          accepted






          I think the date that you used is in the future 1534550400 = Saturday, August 18, 2018 12:00:00 AM.



          if you want it to happen right away, just use the epoch as per the documentation it's 1970-01-01T00:00:00Z






          share|improve this answer












          I think the date that you used is in the future 1534550400 = Saturday, August 18, 2018 12:00:00 AM.



          if you want it to happen right away, just use the epoch as per the documentation it's 1970-01-01T00:00:00Z







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Aug 17 at 22:43









          MonsieurNicolas

          1,633514




          1,633514











          • Thank you. That makes sense. I changed it to one minute in the future as a test and it updated correctly at the right time.
            – Synesso♦
            Aug 17 at 22:48







          • 1




            Update to docs to clarify that param. github.com/stellar/stellar-core/pull/1759
            – Synesso♦
            Aug 17 at 23:00
















          • Thank you. That makes sense. I changed it to one minute in the future as a test and it updated correctly at the right time.
            – Synesso♦
            Aug 17 at 22:48







          • 1




            Update to docs to clarify that param. github.com/stellar/stellar-core/pull/1759
            – Synesso♦
            Aug 17 at 23:00















          Thank you. That makes sense. I changed it to one minute in the future as a test and it updated correctly at the right time.
          – Synesso♦
          Aug 17 at 22:48





          Thank you. That makes sense. I changed it to one minute in the future as a test and it updated correctly at the right time.
          – Synesso♦
          Aug 17 at 22:48





          1




          1




          Update to docs to clarify that param. github.com/stellar/stellar-core/pull/1759
          – Synesso♦
          Aug 17 at 23:00




          Update to docs to clarify that param. github.com/stellar/stellar-core/pull/1759
          – Synesso♦
          Aug 17 at 23:00












           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstellar.stackexchange.com%2fquestions%2f1474%2fupgrading-core-protocol-version-docker-quickstart-standalone%23new-answer', 'question_page');

          );

          Post as a guest













































































          這個網誌中的熱門文章

          How to combine Bézier curves to a surface?

          Mutual Information Always Non-negative

          Why am i infinitely getting the same tweet with the Twitter Search API?