[BUG] harvester keeps crashing when running on python3.9 (Ubuntu 21.04)
See original GitHub issueharvester keeps crashing
ProblemType: Crash
Architecture: amd64
Date: Sun Apr 25 17:44:00 2021
DistroRelease: Ubuntu 21.04
ExecutablePath: /usr/bin/python3.9
ExecutableTimestamp: 1617565124
ProcCmdline: chia_harvester
ProcCwd: /home/speedster/dev
ProcEnviron:
ProcMaps:
[stacktrace hexdump contents redacted]
ProcStatus:
Name: chia_harvester
Umask: 0002
State: D (disk sleep)
Tgid: 15158
Ngid: 0
Pid: 15158
PPid: 14910
TracerPid: 0
Uid: 1000 1000 1000 1000
Gid: 1000 1000 1000 1000
FDSize: 64
Groups: 4 24 27 30 46 121 132 133 1000
NStgid: 15158
NSpid: 15158
NSpgid: 14891
NSsid: 14820
VmPeak: 2460356 kB
VmSize: 2427072 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM: 101600 kB
VmRSS: 101600 kB
RssAnon: 90672 kB
RssFile: 10928 kB
RssShmem: 0 kB
VmData: 390240 kB
VmStk: 132 kB
VmExe: 2628 kB
VmLib: 12760 kB
VmPTE: 532 kB
VmSwap: 0 kB
HugetlbPages: 0 kB
CoreDumping: 1
THP_enabled: 1
Threads: 33
SigQ: 0/31013
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000001001000
SigCgt: 0000000180004002
CapInh: 0000000000000000
CapPrm: 0000000000000000
CapEff: 0000000000000000
CapBnd: 000001ffffffffff
CapAmb: 0000000000000000
NoNewPrivs: 0
Seccomp: 0
Seccomp_filters: 0
Speculation_Store_Bypass: thread vulnerable
SpeculationIndirectBranch: always enabled
Cpus_allowed: f
Cpus_allowed_list: 0-3
Mems_allowed: 00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000001
Mems_allowed_list: 0
voluntary_ctxt_switches: 114106
nonvoluntary_ctxt_switches: 43557
Signal: 6
Uname: Linux 5.11.0-16-generic x86_64
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
CoreDump: base64
[crash hexdump contents redacted]
Farm has approx 1000 plots across 28 plot directories
I have full standard Ubuntu crashdump but suspect there may be private keys buried within it so not uploading. I can scrape any relevant info you want out of it as necessary if you can tell me what, if any, I need to redact out of the crashdump.
Thanks,
-=dave
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
[BUG] harvester can not reconnect after network problem #6047
I run a full-node farmer on one server and other harvester in diff server. After harvester Websocket exception, it stop work and not...
Read more >typecatcher crashes on launch - Launchpad Bugs
I recently upgraded to hirsute 21.04 and just discovered typecatcher doesn't launch. A couple of web searches implies some deprecated python ...
Read more >Unmet dependencies python3.9 - apt - Ask Ubuntu
Try 'apt --fix-broken install' with no packages (or specify a solution). So I run sudo apt --fix-broken install and get: Reading package lists.....
Read more >DebuggingSystemCrash - Community Help Wiki
If your system crashes when a particular action occurs, and this is repeatable every time, try to reproduce the crash on a text...
Read more >Python 3.9 crashes when using the interactive prompt with ...
This is likely a bug, since Python3.9 was just released today. · Do you create the virtual environment with virtualenv or with venv?...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I made the following 3 changes.
I am doing a staggered start on a single SSD. I also updated my bios of the MSI 490 A PRO motherboard. I replaced my 4tb ssd with 2x 2tb.
My ubuntu is no longer crashing. Most likely first 2 changes resolved my issue.
I provided the actionable info but no one is interested in investigating, so i’ll close this as i’m no longer interested either