Changed servers from a cloud to a bare metal (2 CPUs to E3-1270v6 Processor - 4 Cores / 8 Threads) - no problem installing, configuring, and using on the cloud but the bare metal returns “Segmentation fault (core dumped)” on verifying the version after install. From what I understand, this means restic is in a part of the memory I can’t reach… OK, now what???
No, this just means that restic tried to read from or write to a memory address that isn’t mapped. This could indicate any number of things, including (but not limited to) a bug in restic, a bug in the Go compiler, a bug in one of restic’s dependencies, or a hardware issue.
The most likely culprit, in the absence of other diagnostic information, is a bad memory module. Consider running memtest on the machine to rule that out.
2 Likes
Thanks CD… after posting this, we ran into other issues with the server so we ditched it, and started anew on a new one… working just fine. Was too late to run memtest…
2 Likes
Ah, yeah, most likely hardware issues then.
2 Likes