I started the server, but it doesn't work anymore (KOR:서버를 실행시켰는데 더이상 진행이 되지 않습니다)

Mining
1

Hello.

I started the server through the following command, but it goes up to the source below and does not proceed any further.
docker-compose -f .\Server\docker-compose.yaml up

Are there any additional settings or changes that need to be made?

Please help.
Thank you.

안녕하세요.

다음 명령어를 통해 서버를 실행시켰는데 아래 소스까지 지행되고 더이상 진행이 안됩니다.
docker-compose -f .\Server\docker-compose.yaml up

추가적인 세팅이나 변경해야 할 내용이 있을까요?

도움 부탁드립니다.
감사합니다.

PS C:\Creditcoin\CreditcoinDockerCompose-Mainnet-dev> docker-compose -f .\Server\docker-compose.yaml up
[+] Running 6/6

  • Network server_default Created 0.0s
  • Container creditcoin-gateway Created 3.2s
  • Container sawtooth-validator-default Created 3.1s
  • Container sawtooth-settings-tp-default Created 0.1s
  • Container sawtooth-rest-api-default Created 1.5s
  • Container creditcoin-processor Created 1.4s
    Attaching to creditcoin-gateway, creditcoin-processor, sawtooth-rest-api-default, sawtooth-settings-tp-default, sawtooth-validator-default
    sawtooth-validator-default | [2021-11-22 06:51:34.094 WARNING cli] Network key pair is not configured, Network communications between validators will not be authenticated or encrypted.
    creditcoin-processor | Connecting to tcp://validator:4004
    creditcoin-processor | Using gateway URL: tcp://gateway:55555
    creditcoin-processor | 9 [0x7f585ba29780] DEBUG sawtooth.TransactionProcessor null - signal handler initializedcreditcoin-processor | 10 [0x7f585ba29780] DEBUG sawtooth.TransactionProcessor null - TransactionProcessor::RegisterHandler
    creditcoin-processor | Running
    creditcoin-processor | 10 [0x7f585ba29780] DEBUG sawtooth.TransactionProcessor null - Connect to inproc://request_queue
    creditcoin-processor | 10 [0x7f585ba29780] INFO sawtooth.TransactionProcessor null - Connect to: tcp://validator:4004
    creditcoin-processor | 10 [0x7f585ba29780] INFO sawtooth.MessageDispatcher null - Connecting to tcp://validator:4004
    creditcoin-processor | 11 [0x7f5856751700] INFO sawtooth.MessageDispatcher null - Server connection state changed to: CONNECTED
    creditcoin-processor | 11 [0x7f585ba29780] INFO sawtooth.TransactionProcessor null - TransactionProcessor::Run : Server connected
    creditcoin-processor | 12 [0x7f585ba29780] DEBUG sawtooth.TransactionProcessor null - TransactionProcessor::Register: CREDITCOIN
    creditcoin-processor | 12 [0x7f585ba29780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.0
    creditcoin-processor | 19 [0x7f5856751700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
    creditcoin-processor | 19 [0x7f585ba29780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.1
    creditcoin-processor | 23 [0x7f5856751700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
    creditcoin-processor | 23 [0x7f585ba29780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.2
    creditcoin-processor | 26 [0x7f5856751700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
    creditcoin-processor | 27 [0x7f585ba29780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.3
    creditcoin-processor | 30 [0x7f5856751700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
    creditcoin-processor | 30 [0x7f585ba29780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.4
    creditcoin-processor | 32 [0x7f5856751700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
    creditcoin-processor | 32 [0x7f585ba29780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.5
    creditcoin-processor | 33 [0x7f5856751700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
    creditcoin-processor | 33 [0x7f585ba29780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.6
    creditcoin-processor | 35 [0x7f5856751700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
    creditcoin-processor | 35 [0x7f585ba29780] DEBUG sawtooth.TransactionProcessor null - Register Handler: CREDITCOIN Version: 1.7
    creditcoin-processor | 37 [0x7f5856751700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 5
    creditcoin-processor | 38 [0x7f5856751700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 2
    creditcoin-processor | Applicator::Apply
    creditcoin-processor | 40 [0x7f5856751700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 8
    creditcoin-processor | 6015 [0x7f5856751700] DEBUG sawtooth.MessageDispatcher null - ReceiveMessage MessageType: 117
    [2021-11-22 07:07:10.184 WARNING handlers] Received AuthorizationViolation from d65cbfd0559b52c2c864a7151934846d17a0a68d586af9f9a800ef26debf2fd4c4bb30db82749abf62f05f0e62ce4e5435c8ef8b607312dd1582aa96edd575f6
    [2021-11-22 07:58:24.840 WARNING handlers] Received AuthorizationViolation from 06e145d2ce2202d49b89061950f881650fc2807c5c35c749f5eb760caa76266c8f7a5ccf556d303927a201d09959763ff77ec5c4b847c85e2c2b0fb61a71ef38
1 Like
2

You need to wait until your server’s block height reaches the latest block. Please check the following link and you can find how to check your server’s block height.
https://community.creditcoin.org/t/simple-script-for-mining-maintenance-in-korean/52

3

Thank you for your reply.

I am using ‘Docker’ and ‘Windows PowerShell’.

I made the ‘cccomand.sh’ file, but it doesn’t work.
I executed that in the Windows PowerShell.
Please let me know how can I execute the file.

image
image790×418 11.4 KB

And
Does it work like the screenshot below? Is this the process of finding the final block location? Do you know how many hours it takes?

image
image959×709 12.3 KB

Thank you very very much for your help!

4

Powershell script (‘.ps’ file type) is different from Linux’s bash script (‘.sh’ file type). You can use ‘.sh’ on Linux only. You need to rewrite the bash script as a Powershell script. Otherwise, you can run the code line by line.

If you want to check your block height, run the following line.

docker exec -it creditcoin-client ./ccclient tip

Yes. My log prints the same message as in the screenshot. You can think of it as the process of updating blocks on the ledger. When the block height reaches the latest block, the server mines a new block. If you started from the latest snapshot, it can take a day or a few days.

Ps. Docker setup on Windows is tricky. If you know how to use Linux, I recommend using Linux.

5

Thank you for your kindness!
Wow, I’ll have to turn the computer on for a few days.

Thank you again!