log in

Advanced search

Message boards : Number crunching : Always immediate segfault Native R v2.15.1 Application (Cross Platform) v1.10 (sse2)

Author Message
Carsten Milkau
Send message
Joined: 17 Mar 12
Posts: 5
Credit: 291,608
RAC: 0
Message 3863 - Posted: 17 Aug 2016, 14:53:37 UTC
Last modified: 17 Aug 2016, 14:53:51 UTC

Native R apps always crash immediately (0 secs CPU) with segmentation fault.

    - No work for other apps so couldn't test those
    - Other boinc projects run fine.
    - Ran a memtest on all cpus in parallel just to make sure it's not hardware. All fine.

For instance, see:
[1] http://mindmodeling.org/result.php?resultid=18736362
[2] http://mindmodeling.org/workunit.php?wuid=27278141

Profile Brandon
Project administrator
Project developer
Project tester
Avatar
Send message
Joined: 5 Jan 15
Posts: 250
Credit: 1,456,117
RAC: 0
Message 3866 - Posted: 17 Aug 2016, 20:12:08 UTC
Last modified: 17 Aug 2016, 20:12:08 UTC

Hello Carsten,

We will take a look at this issue for you.

Just one quick question for now.

Were workunits that ran these past few weeks being completed successfully and you just now noticed this error, or has this been happening for a while now?

As for a possible reason why, I suspect it could be an issue with a shared object on your system that we are attempting to reference that looks different than what we expected.

Thanks for your support and happy crunching,

Brandon

Carsten Milkau
Send message
Joined: 17 Mar 12
Posts: 5
Credit: 291,608
RAC: 0
Message 3867 - Posted: 18 Aug 2016, 8:21:15 UTC - in response to Message 3866.
Last modified: 18 Aug 2016, 8:21:15 UTC

I have no successfull tasks on this app, they all crahed with the same error. I dont know whether this app ever ran successfully on my system, I remember I always had problems with native R now and then, often disabling it.

The workunits that crashed also crashed for many other users, but never for all users. Seems a common problem.

Carsten Milkau
Send message
Joined: 17 Mar 12
Posts: 5
Credit: 291,608
RAC: 0
Message 3868 - Posted: 18 Aug 2016, 12:10:49 UTC
Last modified: 18 Aug 2016, 12:10:49 UTC

I noticed that some boinc applications require vsyscall emulation (this can be caused, for instance, by statically linking <glibc-2.14). If Mindmodelling is using such applications, that might be cause of the crash.

Currently, there are no tasks available so I cannot test whether that is the cause.

vsyscall has been deprecated for a long time, and even emulation still has some (small) impact on security. I'll disable native R apps for a while, and check back in later, in case a newer version might work.

Carsten Milkau
Send message
Joined: 17 Mar 12
Posts: 5
Credit: 291,608
RAC: 0
Message 3869 - Posted: 18 Aug 2016, 15:07:55 UTC - in response to Message 3868.
Last modified: 18 Aug 2016, 15:07:55 UTC

P.S. Got some tasks for testing. If vsyscall emulation is enabled, the tasks run properly. I'll finish those tasks, then disable native R apps and vsyscall.

Profile Brandon
Project administrator
Project developer
Project tester
Avatar
Send message
Joined: 5 Jan 15
Posts: 250
Credit: 1,456,117
RAC: 0
Message 3872 - Posted: 19 Aug 2016, 14:30:10 UTC
Last modified: 19 Aug 2016, 14:30:10 UTC

Thank you so much for the update.

We will take a look at vsyscall and see what we can do.

Thanks for supporting us and happy crunching,

Brandon

Message boards : Number crunching : Always immediate segfault Native R v2.15.1 Application (Cross Platform) v1.10 (sse2)


Main page · Your account · Message boards


Copyright © 2018 MindModeling.org