Error: setup Error: TypeError: Cannot read properties of undefined (reading 'mountpoint') #90
Comments
|
Could you try with v3.3.5? |
|
3.3.5 installed, same error. Installing RPC NODE & Validator. |
|
sh -c "$(curl -sSfL "https://storage.googleapis.com/epics-bucket/resource/solv/v3.3/install")" I tried this install script and worked. |
|
Hello, |
|
Any solutions to this. I am getting this also on Ubuntu 22.04 x64. Thx. |
|
same error,Is it because my computer hardware configuration is too low? For example, the configuration cannot reach epyc 7743 and 512G ram? solv@HL:~$ solv setup
Updated /home/solv/solv.config.json with new values.
Setting up Solana Validator ...
? Which solv types do you want to setup? RPC_NODE
? Enter your IP address to allow access to RPC NODE: 0.0.0.0
[sudo] password for solv:
✔️ Firewall updated!
Setting up RPC_NODE...
Error: setup Error: TypeError: Cannot read properties of undefined (reading 'mountpoint')
at setup (/home/solv/.local/share/pnpm/global/5/.pnpm/@epics-dao+solv@3.3.13/node_modules/@epics-dao/solv/dist/index.js:294:1613)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async t. (/home/solv/.local/share/pnpm/global/5/.pnpm/@epics-dao+solv@3.3.13/node_modules/@epics-dao/solv/dist/index.js:294:3291)
at async t.parseAsync (/home/solv/.local/share/pnpm/global/5/.pnpm/@epics-dao+solv@3.3.13/node_modules/@epics-dao/solv/dist/index.js:16:3980)
at async main (/home/solv/.local/share/pnpm/global/5/.pnpm/@epics-dao+solv@3.3.13/node_modules/@epics-dao/solv/dist/index.js:351:819)
|
|
Are you guys using VirtualBox? |
hello,my server is cloud server(vps). ubuntu 22.04 Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 48 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 3
On-line CPU(s) list: 0-2
Vendor ID: AuthenticAMD
Model name: AMD Ryzen 9 7950X 16-Core Processor
CPU family: 25
Model: 97
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 3
Stepping: 2
BogoMIPS: 8982.74
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mc
a cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx m
mxext fxsr_opt pdpe1gb rdtscp lm rep_good nopl cpuid ex
td_apicid tsc_known_freq pni pclmulqdq ssse3 fma cx16 s
se4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes
xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy sv
m cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw p
erfctr_core ssbd ibrs ibpb stibp vmmcall fsgsbase tsc_a
djust bmi1 avx2 smep bmi2 erms invpcid avx512f avx512dq
rdseed adx smap avx512ifma clflushopt clwb avx512cd sh
a_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves a
vx512_bf16 clzero xsaveerptr wbnoinvd arat npt lbrv nri
p_save tsc_scale vmcb_clean pausefilter pfthreshold v_v
msave_vmload vgif avx512vbmi umip pku ospke avx512_vbmi
2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512
_vpopcntdq rdpid fsrm arch_capabilities
Virtualization features:
Virtualization: AMD-V
Hypervisor vendor: KVM
Virtualization type: full
Caches (sum of all):
L1d: 96 KiB (3 instances)
L1i: 96 KiB (3 instances)
L2: 3 MiB (3 instances)
L3: 192 MiB (3 instances)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-2
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: Not affected
Spec rstack overflow: Mitigation; safe RET, no microcode
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, STIB
P disabled, RSB filling, PBRSB-eIBRS Not affected
Srbds: Not affected
Tsx async abort: Not affected
|
|
I am using AWS : m6i.12xlarge |
|
Same thing happenning running this in a clean ubuntu docker image: Setting up MAINNET_VALIDATOR... |
|
It looks like AWS has some problems. I think AWS's |
|
same here. Does anyone know how to solve it? |
|
Hey guys, so i'm having the same issue with a really large VM on VMware. The Problem seems to be the .disks array which is not getting populated. I've just added a console.log(is().disks) right before the error, and it returns [] (empty array). So there seems to be something wrong with the hdd detection i guess. |
|
since Now running that returns normal output: I'm guessing the following javascript magic boggles the array and thus misses the disk. |
|
I got it working by making my main volume with OS 800 GB. But I tried very power and expensive AWS server and was unable to catch-up. |
|
aaah, this could probably be the size check that follows if the disk is > 400gb or 850gb depending on what you're setting up. |
we came to the same conclusion :) mine is now working too. |
Were you able to catch-up yet? |
|
not yet |
|
After it reaches 100% run 'solv get catchup' it will then show you if you are staying up to date or falling behind. I was always falling behind. Thx. |
|
i'll keep you posted, currently at 95%, my guess is the disks are too slow (even tho i have sata ssd only storage) |
|
ah yeah, i need to add more cpus to the VM. [2024-04-19T12:53:47.414092964Z ERROR solana_validator] Failed to start validator: "PoH is slower than cluster target tick rate! mine: 767312631 cluster: 400000000." |
I went as high as 98 and still had trouble catching up |
adds a log message when the disk it too small, fixes EpicsDAO#90 by giving the users a warning
apparently it's just a missing log line. there is also no log line for 0 % :) |
Then operating a validator node might not be for you. it's a financial risk and 250$ is going to be the least of it. |
|
Operating validator nodes is not a scheme to make money. It's a way of supporting the Solana Ecosystem. Yes you get rewarded, but there are risks as there are with anything where you have to go money-first. |
and others
solv@ssdnodes:~$ solv setup
Updated /home/solv/solv.config.json with new values.
Setting up Solana Validator ...
? Which solv types do you want to setup? MAINNET_VALIDATOR
? Which mainnet mode do you want to setup? JitoMev
JITO MEV Setup Mode on!
? Enter commission bps 1000
? Select region Amsterdam
? What is your commission rate? You can change it later (default: 10%) 7
Setting up MAINNET_VALIDATOR...
Error: setup Error: TypeError: Cannot read properties of undefined (reading 'mountpoint')
at setup (/home/solv/.nodenv/versions/20.10.0/lib/node_modules/@epics-dao/solv/dist/index.js:288:1496)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async r. (/home/solv/.nodenv/versions/20.10.0/lib/node_modules/@epics-dao/solv/dist/index.js:288:3626)
at async r.parseAsync (/home/solv/.nodenv/versions/20.10.0/lib/node_modules/@epics-dao/solv/dist/index.js:16:3980)
at async main (/home/solv/.nodenv/versions/20.10.0/lib/node_modules/@epics-dao/solv/dist/index.js:336:831)
The text was updated successfully, but these errors were encountered: