Having lost of error log and slow plot warning on 3H

Centny_Wen · February 1, 2024, 2:41am

Issue Report

Environment

Operating System:Ubuntu 22.04.3 LTS
Docker:gemini-3h-2024-jan-31-2

Problem

server-s00/s06: lost of error
server-s01~s05: slow warning, but cpu is not full, disk is low

image1920×1232 335 KB

CPU

s00

Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         43 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  48
  On-line CPU(s) list:   0-47
Vendor ID:               AuthenticAMD
  Model name:            AMD EPYC 7402 24-Core Processor
    CPU family:          23
    Model:               49
    Thread(s) per core:  2
    Core(s) per socket:  24
    Socket(s):           1
    Stepping:            0
    Frequency boost:     enabled
    CPU max MHz:         2800.0000
    CPU min MHz:         1500.0000
    BogoMIPS:            5599.82
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl p
                         ni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_
                         nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc
                         cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd amd_ppin arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl u
                         mip rdpid overflow_recov succor smca sme sev sev_es
Virtualization features:
  Virtualization:        AMD-V
Caches (sum of all):
  L1d:                   768 KiB (24 instances)
  L1i:                   768 KiB (24 instances)
  L2:                    12 MiB (24 instances)
  L3:                    128 MiB (8 instances)
NUMA:
  NUMA node(s):          4
  NUMA node0 CPU(s):     0-5,24-29
  NUMA node1 CPU(s):     6-11,30-35
  NUMA node2 CPU(s):     12-17,36-41
  NUMA node3 CPU(s):     18-23,42-47
Vulnerabilities:
  Itlb multihit:         Not affected
  L1tf:                  Not affected
  Mds:                   Not affected
  Meltdown:              Not affected
  Mmio stale data:       Not affected
  Retbleed:              Mitigation; untrained return thunk; SMT enabled with STIBP protection
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl and seccomp
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:            Mitigation; Retpolines, IBPB conditional, STIBP always-on, RSB filling, PBRSB-eIBRS Not affected
  Srbds:                 Not affected
  Tsx async abort:       Not affected

s01~s05

Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         43 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  64
  On-line CPU(s) list:   0-63
Vendor ID:               AuthenticAMD
  Model name:            AMD EPYC 7F52 16-Core Processor
    CPU family:          23
    Model:               49
    Thread(s) per core:  2
    Core(s) per socket:  16
    Socket(s):           2
    Stepping:            0
    Frequency boost:     enabled
    CPU max MHz:         3500.0000
    CPU min MHz:         2500.0000
    BogoMIPS:            6999.81
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl p
                         ni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_
                         nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm
                         _total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd amd_ppin arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip rdp
                         id overflow_recov succor smca sme sev sev_es
Virtualization features:
  Virtualization:        AMD-V
Caches (sum of all):
  L1d:                   1 MiB (32 instances)
  L1i:                   1 MiB (32 instances)
  L2:                    16 MiB (32 instances)
  L3:                    512 MiB (32 instances)
NUMA:
  NUMA node(s):          2
  NUMA node0 CPU(s):     0-15,32-47
  NUMA node1 CPU(s):     16-31,48-63
Vulnerabilities:
  Gather data sampling:  Not affected
  Itlb multihit:         Not affected
  L1tf:                  Not affected
  Mds:                   Not affected
  Meltdown:              Not affected
  Mmio stale data:       Not affected
  Retbleed:              Mitigation; untrained return thunk; SMT enabled with STIBP protection
  Spec rstack overflow:  Mitigation; safe RET
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl and seccomp
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:            Mitigation; Retpolines, IBPB conditional, STIBP always-on, RSB filling, PBRSB-eIBRS Not affected
  Srbds:                 Not affected
  Tsx async abort:       Not affected

s06

Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         46 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  56
  On-line CPU(s) list:   0-55
Vendor ID:               GenuineIntel
  Model name:            Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz
    CPU family:          6
    Model:               79
    Thread(s) per core:  2
    Core(s) per socket:  14
    Socket(s):           2
    Stepping:            1
    CPU max MHz:         3300.0000
    CPU min MHz:         1200.0000
    BogoMIPS:            4788.64
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
                         cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_f
                         ault epb cat_l3 cdp_l3 invpcid_single pti intel_ppin ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdt_a rdseed adx smap intel_pt xsave
                         opt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts md_clear flush_l1d
Virtualization features:
  Virtualization:        VT-x
Caches (sum of all):
  L1d:                   896 KiB (28 instances)
  L1i:                   896 KiB (28 instances)
  L2:                    7 MiB (28 instances)
  L3:                    70 MiB (2 instances)
NUMA:
  NUMA node(s):          2
  NUMA node0 CPU(s):     0-13,28-41
  NUMA node1 CPU(s):     14-27,42-55
Vulnerabilities:
  Gather data sampling:  Not affected
  Itlb multihit:         KVM: Mitigation: VMX disabled
  L1tf:                  Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable
  Mds:                   Mitigation; Clear CPU buffers; SMT vulnerable
  Meltdown:              Mitigation; PTI
  Mmio stale data:       Mitigation; Clear CPU buffers; SMT vulnerable
  Retbleed:              Not affected
  Spec rstack overflow:  Not affected
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl and seccomp
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:            Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling, PBRSB-eIBRS Not affected
  Srbds:                 Not affected
  Tsx async abort:       Mitigation; Clear CPU buffers; SMT vulnerable

RUN

node

   docker run -d --name subspace-$1 --restart=always \
        --hostname sub-$target-$1 \
        --network local --ip 192.168.5.5 --ip6 240e:3b6:c71:d410::0505\
        -v /data/subspace/node:/var/subspace \
        xxx.com/subspace/node:3h \
        run \
        --chain gemini-3h \
        --base-path /var/subspace \
        --blocks-pruning 256 \
        --state-pruning archive-canonical \
        --listen-on /ip4/0.0.0.0/tcp/30333 --listen-on /ip4/0.0.0.0/udp/30333/quic-v1 --listen-on /ip6/::/tcp/30333 --listen-on /ip6/::/udp/30333/quic-v1 \
        --dsn-listen-on /ip4/0.0.0.0/udp/30433/quic-v1 \
        --dsn-listen-on /ip4/0.0.0.0/tcp/30433 \
        --rpc-cors all --rpc-methods unsafe --rpc-listen-on 0.0.0.0:9944 \
        --farmer --allow-private-ips \
        --name cny-sub-$target-$1

s00

    docker run -d --name subspace-$name --restart=always \
        --network local --ip 192.168.6.100 --ip6 240e:3b6:c71:d410::6100\
        -v /data/subspace/store:/var/subspace \
        xxx.com/subspace/farmer:3h \
        farm \
        --node-rpc-url ws://192.168.5.5:9944 \
        --listen-on /ip4/0.0.0.0/udp/30533/quic-v1 --listen-on /ip4/0.0.0.0/tcp/30533 \
        --reward-address stAy9rRkZaNa2fijHfH7Pn5KMfpbZCR89R2ri6YLpugLRYsU4 \
        path=/var/subspace/s00/p000,size=3563G \
        path=/var/subspace/s01/p000,size=3563G \
        path=/var/subspace/s02/p000,size=3563G

s01~s05

docker run -d --name subspace-$name --restart=always \
        --network local --ip 192.168.6.101 --ip6 240e:3b6:c71:d410::6101\
        -v /data/subspace/store:/var/subspace \
        xxx.com/subspace/farmer:3h \
        farm \
        --node-rpc-url ws://192.168.5.5:9944 \
        --listen-on /ip4/0.0.0.0/udp/30533/quic-v1 --listen-on /ip4/0.0.0.0/tcp/30533 \
        --reward-address stAy9rRkZaNa2fijHfH7Pn5KMfpbZCR89R2ri6YLpugLRYsU4 \
        path=/var/subspace/s00/p000,size=543G \
        path=/var/subspace/s00/p001,size=543G \
        path=/var/subspace/s00/p002,size=543G \
        path=/var/subspace/s00/p003,size=543G \
        path=/var/subspace/s00/p004,size=543G \
        path=/var/subspace/s00/p005,size=543G \
        path=/var/subspace/s01/p000,size=543G \
        path=/var/subspace/s01/p001,size=543G \
        path=/var/subspace/s01/p002,size=543G \
        path=/var/subspace/s01/p003,size=543G \
        path=/var/subspace/s01/p004,size=543G \
        path=/var/subspace/s01/p005,size=543G \
        path=/var/subspace/s02/p000,size=543G \
        path=/var/subspace/s02/p001,size=543G \
        path=/var/subspace/s02/p002,size=543G \
        path=/var/subspace/s02/p003,size=543G \
        path=/var/subspace/s02/p004,size=543G \
        path=/var/subspace/s02/p005,size=543G \
        path=/var/subspace/s03/p000,size=543G \
        path=/var/subspace/s03/p001,size=543G \
        path=/var/subspace/s03/p002,size=543G \
        path=/var/subspace/s03/p003,size=543G \
        path=/var/subspace/s03/p004,size=543G \
        path=/var/subspace/s03/p005,size=543G \
        path=/var/subspace/s04/p000,size=543G \
        path=/var/subspace/s04/p001,size=543G \
        path=/var/subspace/s04/p002,size=543G \
        path=/var/subspace/s04/p003,size=543G \
        path=/var/subspace/s04/p004,size=543G \
        path=/var/subspace/s04/p005,size=543G

LOG

log is uploaded to subspace

Emilios · February 1, 2024, 3:08am

Try using Docker:gemini-3h-2024-jan-31-2 version and let us know if the issue persists!

Centny_Wen · February 1, 2024, 3:13am

already using it
my docker file is, not change anything

FROM ghcr.io/subspace/node:gemini-3h-2024-jan-31-2
USER root
ENTRYPOINT ["/subspace-node"]

nazar-pc · February 1, 2024, 4:24am

It is proving that is slow due to wide solution range. You might want to disable farming for now

Centny_Wen · February 1, 2024, 5:35am

new running on 3h, not plan disable farming, how to fix it?

nazar-pc · February 1, 2024, 6:25am

No way to fix it without disabling farming until seeding is done and space race starts

z_W · February 1, 2024, 6:36am

If I ignore this warning, there should be no consequences, right?

nazar-pc · February 1, 2024, 6:48am

You’re just wasting a lot of CPU on proving for no reason, no other consequences

z_W · February 1, 2024, 6:52am

Approximately when can it be turned on?

Centny_Wen · February 1, 2024, 7:02am

the reason is not join space rate 14 hours ago (–pot-external-entropy 000000000000000000037bbc7fae1cd2c91dba8312b65f71352630e938cc4dda) ?
another question： having different reward for 10 * 4T ssd on single server vs 2 * 5 * 4T ssd on two server, the server is same cpu and memory.

nazar-pc · February 1, 2024, 7:09am

Your questions are unrelated to this topic, @Centny_Wen

user37 · February 1, 2024, 7:53am

Can you tell me if farming is pointless now, is it possible to turn it off?

Jim-Autonomys · February 1, 2024, 10:36am

At this stage of the Mini Space Race it is - farming is not enabled for anyone but the genesis farmer. This is explained in the forum post here.

To disable farming you can add --farm-during-initial-plotting false to your farmer parameters.

nazar-pc · February 2, 2024, 2:55pm

The reason for that error is the way we bootstrap the network.

Initial solution range is set to be equivalent to 1G space pledged. That is how much genesis farmer needs to seed the history.

Now those who start on Gemini 3h before farming is allowed for everyone will have A LOT of solutions on each slot once they plot a few sectors due to solution range being so wide, so with overwhelming probability farmer will not be able to prove all of those sectors in time (4s).

This error will go away once solution range becomes dynamic and anyone can farm at the beginning of the next phase of Gemini 3h.

Centny_Wen · February 4, 2024, 1:06pm

can farm now? having approximately time for next phase? still same resautl today
@nazar-pc @Jim-Autonomys

Jim-Autonomys · February 5, 2024, 11:35am

Not until phase 2 of the Mini Space Race. Please check out the forum post to understand the timings and join us on the community call on Wednesday. Gemini 3h and The Mini Space Race

Topic		Replies	Views
Plot is slow and cpu/disk is low Support gemini , farmer	6	298	January 30, 2024
Gemini-3h Plotting sector very very slow since Finished syncing piece cache to the latest history size Support farmer , plotting	6	165	April 15, 2024
Farmer starting error Support	1	292	April 24, 2023
Although node and farm start successfully, I get an error like this within a minute. Testing gemini-3d	1	223	July 12, 2023
Error plot on docker Support desktop-app , gemini , nodes , error , farmer	11	345	April 6, 2023

Having lost of error log and slow plot warning on 3H

Issue Report

Environment

Problem

CPU

RUN

LOG

Related topics