Segmentation fault (core dumped) when starting xlarig

[sascha08-15]

Ubuntu 20.10 running

Executing the xlarig 5.2.2 receives: Segmentation fault (core dumped) when starting xlarig

My suspicions: are you trying to use/set wrsmr? Not executing as root (obviously, and not planning to do so).

Any advices?

[Teredic]

Could you please tell me what kind of cpu you are using ?

[boner-cmd]

From the build instructions:

Since Raspbian is a 32 bit OS and XLArig is a 64 bit miner, you'll need to be on a 64-bit container if you don't want to get a segmentation fault after starting it.

Any chance you're on a 32 bit OS?

[sascha08-15]

Thanks for the reply. Yes sure. I am using an Intel 9900k

[sascha08-15]

It's 64 bit for sure. Kernel 5.8.0-50-generic

[ViralWeaponry]

Im also having this issue but I'm on a VM with Ubuntu on a Ryzen 5 laptop

[Teredic]

Could you please try this build i just made ?

[ViralWeaponry]

Hi,

Thank you! I just tried it but got the same error. I am using a VM in VirtualBox but I was able to run xmrig without issues, I'm guessing this miner is similar, please correct me if I'm wrong.

[image: image.png]

Sincerely,

Inartaly Valentin

On Tue, Apr 27, 2021 at 12:51 PM Teredic @.***> wrote:

Could you please try this build i just made : https://github.com/scala-network/XLArig/releases/download/v5.2.2/XLArig-v5.2.2-linux-x86_64_alt.zip ?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/scala-network/XLArig/issues/38#issuecomment-827757330, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQHCXFMHYTULCWASE5BA273TK3TRLANCNFSM43P7KMZA .

[Teredic]

Ok. I created a new VM under Ubuntu 20.04 and recompiled the miner. here's the result :

https://github.com/scala-network/XLArig/releases/download/v5.2.2/XLArig-v5.2.2-linux-x86_64_v3.zip

Does it work with this build ?

[ViralWeaponry]

Yes it does! Thank you for your help and time. Much appreciated.

Sincerely,

Inartaly Valentin

On Tue, Apr 27, 2021 at 3:29 PM Teredic @.***> wrote:

Ok. I created a cleaned VM under Ubuntu 20.04 and here's the result :

https://github.com/scala-network/XLArig/releases/download/v5.2.2/XLArig-v5.2.2-linux-x86_64_v3.zip

Does it work with this build ?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/scala-network/XLArig/issues/38#issuecomment-827861475, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQHCXFNXCA2SQ7ISUYT7AA3TK4GDBANCNFSM43P7KMZA .

[boner-cmd]

@sascha08-15 did the VM build help? Also, are there any other messages? When setting up mine on 20.10 any time I had bad configuration options it would seg fault. Even things like an incorrect pool port. Is there something above the seg fault to give more info?

[ViralWeaponry]

Teredic reached out to me and fixed the issue with a new build.

Thank you,

Inartaly Valentin

On Tue, Apr 27, 2021 at 4:23 PM Dimelo Waterson @.***> wrote:

@sascha08-15 https://github.com/sascha08-15 did the VM build help? Also, are there any other messages? When setting up mine on 20.10 any time I had bad configuration options it would seg fault. Even things like an incorrect pool port. Is there something above the seg fault to give more info?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/scala-network/XLArig/issues/38#issuecomment-827904797, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQHCXFJUVR7YQDV2TX4OWODTK4MLXANCNFSM43P7KMZA .

[boner-cmd]

I was asking Sascha, the original poster who opened the issue 😅 and who wasn't necessarily using a VM to experience it

[ViralWeaponry]

sorry, i got confused, for some reason I got an email with your question. :)

[sascha08-15]

Nice! Yes, the VM build works like a charm! May I ask, what did you change in the codebase?

[Teredic]

Nice! Yes, the VM build works like a charm! May I ask, what did you change in the codebase?

Nothing. I compiled the same way, as I usually do. However all my previous build were compiled under Debian 10, so perhaps there's a bug somewhere.