figurestudios / community-golem-docs

Collection of community-created documentation for Golem

👋

👋

👋

👋

👋

community-golem-docs's Issues

new article tech overview

golemsp fails to run on vmware Fusion in Mac "vmrt: error: failed to set MSR 0x48d to 0x5600000016"

Hello,

I am trying to run golemsp on Ubuntu 20.04, virtualised through VMware Fusion on a MacBook Pro.
Unfortunately I keep on getting the same error all over again.
Am working in tech Support and found a few hints already, unfortunately none helped to resolve the issue.

Error: runtime test failure

Caused by:
    [2021-08-05T19:25:48Z INFO  ya_runtime_vm::guest_agent_comm] Waiting for Guest Agent socket ...
    vmrt: error: failed to set MSR 0x48d to 0x5600000016
    vmrt: /qemu/target/i386/kvm.c:2713: kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
    thread 'main' panicked at 'Failed to start runtime: Connection refused (os error 111)', runtime/src/main.rs:421:10
    note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
    
[2021-08-05T19:25:49Z ERROR golemsp::service] child provider exited too early: Ok(ExitStatus(ExitStatus(256)))
[2021-08-05T19:25:49Z WARN  golemsp::service] provider exited with: Custom { kind: Other, error: "process exited too early" }

Any help is highly appreciated.

Cheers, Joerg

javascript/docker implementation

here https://github.com/figurestudios/community-golem-docs/blob/main/developing/creating-your-first-app.md

new article maximize income

Golemsp Status - Service is not running

golemsp status
┌───────────────────────────────┐
│ Status │
│ │
│ Service is not running │
│ Version 0.9.2 │
│ Commit d4a24786 │
│ Date 2022-01-10 │
│ Build 191 │
│ │
│ Node Name TempName │
│ Subnet public-beta │
│ VM valid │
└───────────────────────────────┘

System: Ubuntu 20.04 Server - fresh install
virtualization enabled
I may have missed something, not sure... I am getting an error:
WARN ya_net::central::service] Failed to bind handlers: Operation timed out (os error 110);
Is there something I am missing?
I appreciate any help.

Node shows Offline on Network Stats page

This appears to be a recurring problem. I'm on Ubuntu 20.04.6, and followed the linux guide for installation. My server's uptime is 21 days and the Golem's service shows up for 3 weeks. I have UDP port 11500 forwarded to the host, but it often shows offline after any period of time in the Network Stats page, and if I don't intervene, there doesn't appear to be any Activities with Earnings processed when it is in that state. It seems that if I restart the service, the node comes back Online and starts processing requests again. Is there anything in the logs I should be looking for? Any help would be appreciated. For now, I just setup a cron job to restart the service nightly.

┌─────────────────────────────┬──────────────────────────────────────────────────┬─────────────────────────────┐
│  Status                     │  Wallet                                          │  Tasks                      │
│                             │  0x964cffd7f02044e66d60f00c95adc122a7545309      │                             │
│  Service    is running      │                                                  │  last 1h processed     0    │
│  Version    0.12.3          │  network               mainnet                   │  last 1h in progress   0    │
│  Commit     9de9778d        │  amount (total)        0.034011284233813344 GLM  │  total processed       116  │
│  Date       2023-08-01      │      (on-chain)        0 GLM                     │  (including failures)       │
│  Build      309             │      (polygon)         0.034011284233813344 GLM  │                             │
│                             │      (zksync)          0 GLM                     │                             │
│  Node Name  cesspool.cc.01  │                                                  │                             │
│  Subnet     public          │  pending               0 GLM (0)                 │                             │
│  VM         valid           │  issued                0 GLM (0)                 │                             │
└─────────────────────────────┴──────────────────────────────────────────────────┴─────────────────────────────┘

     Loaded: loaded (/etc/systemd/system/golem.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2023-10-22 19:41:35 CDT; 3 weeks 0 days ago
   Main PID: 1200 (golemsp)
      Tasks: 136 (limit: 28785)
     Memory: 3.9G
     CGroup: /system.slice/golem.service
             ├─1200 /home/golem/.local/bin/golemsp run
             ├─1320 /home/golem/.local/share/ya-installer/bundles/golem-provider-linux-v0.12.3/yagna service run
             └─1591 /home/golem/.local/share/ya-installer/bundles/golem-provider-linux-v0.12.3/ya-provider run --payment-network mainnet --payment-network polygon

Nov 13 08:22:52 glm-prv-node-01 golemsp[1320]: [2023-11-13T08:22:52.056-0600 INFO  ya_relay_client::expire] Closing session 99c6af67bff04c958c0dcb1a807bf5d4 (92.85.13.12:12808) not responding to ping.
Nov 13 08:22:54 glm-prv-node-01 golemsp[1320]: [2023-11-13T08:22:54.458-0600 INFO  ya_relay_client::expire] Closing session 99c6af67bff04c958c0dcb1a807bf5d4 (92.85.13.12:12808) not responding to ping.
Nov 13 08:22:56 glm-prv-node-01 golemsp[1320]: [2023-11-13T08:22:56.863-0600 INFO  ya_relay_client::expire] Closing session 99c6af67bff04c958c0dcb1a807bf5d4 (92.85.13.12:12808) not responding to ping.
Nov 13 08:22:59 glm-prv-node-01 golemsp[1320]: [2023-11-13T08:22:59.266-0600 INFO  ya_relay_client::expire] Closing session 99c6af67bff04c958c0dcb1a807bf5d4 (92.85.13.12:12808) not responding to ping.
Nov 13 08:23:01 glm-prv-node-01 golemsp[1320]: [2023-11-13T08:23:01.668-0600 INFO  ya_relay_client::expire] Closing session 99c6af67bff04c958c0dcb1a807bf5d4 (92.85.13.12:12808) not responding to ping.
Nov 13 08:23:04 glm-prv-node-01 golemsp[1320]: [2023-11-13T08:23:04.071-0600 INFO  ya_relay_client::expire] Closing session 99c6af67bff04c958c0dcb1a807bf5d4 (92.85.13.12:12808) not responding to ping.
Nov 13 08:23:06 glm-prv-node-01 golemsp[1320]: [2023-11-13T08:23:06.473-0600 INFO  ya_relay_client::expire] Closing session 99c6af67bff04c958c0dcb1a807bf5d4 (92.85.13.12:12808) not responding to ping.
Nov 13 08:23:08 glm-prv-node-01 golemsp[1320]: [2023-11-13T08:23:08.889-0600 INFO  ya_relay_client::expire] Closing session 99c6af67bff04c958c0dcb1a807bf5d4 (92.85.13.12:12808) not responding to ping.
Nov 13 08:23:11 glm-prv-node-01 golemsp[1320]: [2023-11-13T08:23:11.291-0600 INFO  ya_relay_client::expire] Closing session 99c6af67bff04c958c0dcb1a807bf5d4 (92.85.13.12:12808) not responding to ping.
Nov 13 08:23:13 glm-prv-node-01 golemsp[1320]: [2023-11-13T08:23:13.695-0600 INFO  ya_relay_client::expire] Closing session 99c6af67bff04c958c0dcb1a807bf5d4 (92.85.13.12:12808) not responding to ping.
Nov 13 08:23:16 glm-prv-node-01 golemsp[1320]: [2023-11-13T08:23:16.097-0600 INFO  ya_relay_client::expire] Closing session 99c6af67bff04c958c0dcb1a807bf5d4 (92.85.13.12:12808) not responding to ping.

sudo netstat -anp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      1134/systemd-resolv
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1310/sshd: /usr/sbi
tcp        0      0 127.0.0.1:7465          0.0.0.0:*               LISTEN      1320/yagna
tcp        0      0 127.0.0.1:32768         127.0.0.1:7465          TIME_WAIT   -
tcp        0    208 192.168.252.154:22      192.168.252.124:62000   ESTABLISHED 1140244/sshd: root@
tcp        0      0 127.0.0.1:58632         127.0.0.1:7465          ESTABLISHED 1591/ya-provider
tcp        0      0 127.0.0.1:36148         127.0.0.1:7465          TIME_WAIT   -
tcp        0      0 127.0.0.1:58648         127.0.0.1:7465          ESTABLISHED 1591/ya-provider
tcp        0      0 127.0.0.1:7465          127.0.0.1:35440         ESTABLISHED 1320/yagna
tcp        0      0 127.0.0.1:7465          127.0.0.1:58648         ESTABLISHED 1320/yagna
tcp        0      0 127.0.0.1:7465          127.0.0.1:58632         ESTABLISHED 1320/yagna
tcp        0      0 127.0.0.1:58096         127.0.0.1:7465          TIME_WAIT   -
tcp        0      0 127.0.0.1:7465          127.0.0.1:35454         ESTABLISHED 1320/yagna
tcp        0      0 127.0.0.1:60996         127.0.0.1:7465          TIME_WAIT   -
tcp        0      0 127.0.0.1:34458         127.0.0.1:7465          ESTABLISHED 1591/ya-provider
tcp        0      0 127.0.0.1:58650         127.0.0.1:7465          ESTABLISHED 1591/ya-provider
tcp        0      0 127.0.0.1:7465          127.0.0.1:58650         ESTABLISHED 1320/yagna
tcp        0      0 127.0.0.1:35454         127.0.0.1:7465          ESTABLISHED 1591/ya-provider
tcp        0      0 127.0.0.1:35440         127.0.0.1:7465          ESTABLISHED 1591/ya-provider
tcp        0      0 192.168.252.154:55356   146.59.81.198:9092      ESTABLISHED 1320/yagna
tcp        0      0 127.0.0.1:7465          127.0.0.1:34458         ESTABLISHED 1320/yagna
tcp6       0      0 :::22                   :::*                    LISTEN      1310/sshd: /usr/sbi
udp        0      0 0.0.0.0:11500           0.0.0.0:*                           1320/yagna
udp        0      0 127.0.0.53:53           0.0.0.0:*                           1134/systemd-resolv
udp        0      0 192.168.252.154:68      0.0.0.0:*                           857/systemd-network
raw6       0      0 :::58                   :::*                    7           857/systemd-network

add python/normal development walkthroughs

Change Wallet/Create New

I set up a couple of nodes, and on the second, I put in the same wallet address that was created on the first node, but then realized I can't look the second up online if it's sharing an address. I tried rerunning the initial installer, but wasn't sure how to make it create a new wallet, as the previous address is listed in there. I tried entering in "default=Internal Golem wallet", but received the following message.

Invalid ethereum address, is should be 20-byte hex (example 0xB1974E1F44EAD2d22bB995167A709b89Fc466B6c): NodeId default=Internal Golem wallet` parsing error: expected length is 42 chars