Process exited with code 193


log in

Advanced search

Questions and Answers : Unix/Linux : Process exited with code 193

Previous · 1 · 2
Author Message
Profile Ex
Volunteer moderator
Volunteer tester
Avatar
Send message
Joined: 12 Mar 12
Posts: 2895
Credit: 1,730,660
RAC: 1,158
United States
Message 1247571 - Posted: 17 Jun 2012, 19:47:08 UTC

Thank you for your interest in pushing the Ubuntu team to fix that repository package!

Basically, all you can do is complain at launchpad.

This is the current bug I have opened BEGGING them to make a change to that broken version, no one seems to give a damn....

https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1009536

Go there ^ and sign up if you wish, click "this bug affects me", and feel free to leave a comment asking them what you've asked us.

Thanks.
____________
-Dave #2

3.2.0-33

Profile Markus Klyver
Send message
Joined: 1 Jul 11
Posts: 8
Credit: 309,614
RAC: 0
Sweden
Message 1247671 - Posted: 17 Jun 2012, 22:15:38 UTC - in response to Message 1247571.
Last modified: 17 Jun 2012, 22:18:07 UTC

It seems to also affect LHC@Home, so it is not only SETI, but Milkyway@Home and Einstein@Home works fine.
____________

Profile David Anderson (not *that* DA)Project donor
Avatar
Send message
Joined: 5 Dec 09
Posts: 107
Credit: 22,861,428
RAC: 6,180
United States
Message 1247963 - Posted: 18 Jun 2012, 16:56:50 UTC

I registered as one having the bug, and I also installed the ppa
version (boinc 7.0.27)
and restarted boinc. Then told boinc to get and run seti again
(using boinc-mgr). Picked up one seti task and it is running
ok for a few minutes so far AFAICT.
Once I know if things are really ok I will
add a note to the bug report. This task did not error
off immediately, so that is a good start.

Profile Ex
Volunteer moderator
Volunteer tester
Avatar
Send message
Joined: 12 Mar 12
Posts: 2895
Credit: 1,730,660
RAC: 1,158
United States
Message 1248004 - Posted: 18 Jun 2012, 18:01:42 UTC - in response to Message 1247963.
Last modified: 18 Jun 2012, 18:04:29 UTC

I registered as one having the bug, and I also installed the ppa
version (boinc 7.0.27)
and restarted boinc. Then told boinc to get and run seti again
(using boinc-mgr). Picked up one seti task and it is running
ok for a few minutes so far AFAICT.
Once I know if things are really ok I will
add a note to the bug report. This task did not error
off immediately, so that is a good start.


Which PPA? the "pkg-boinc/ppa". That one (7.0.27) should be fine. It's the version that should be placed into the standard repository, so maybe some positive feedback will in fact help.

...they need to change the 12.04 repository package. PPA's are a great alternative, but they still have a broken Boinc package (7.0.24 w/bad patches) in the 12.04 repository. :-(
____________
-Dave #2

3.2.0-33

Profile David Anderson (not *that* DA)Project donor
Avatar
Send message
Joined: 5 Dec 09
Posts: 107
Credit: 22,861,428
RAC: 6,180
United States
Message 1248049 - Posted: 18 Jun 2012, 19:14:11 UTC
Last modified: 18 Jun 2012, 19:16:21 UTC

The 7.0.27 PPA on Precise (12.04) completed
WU 1013689114 on system 5208384
(task 2490450527) successfully it appears.
Waiting on a wingman for confirmation.

I filed a note on the launchpad bug report (1009536) on this success.
Edit: Hoping this success report will help get them to push
7.0.27 to the regular repository.

ZoSo
Send message
Joined: 27 Jun 12
Posts: 1
Credit: 0
RAC: 0
United States
Message 1252309 - Posted: 27 Jun 2012, 22:13:30 UTC - in response to Message 1247671.

It seems to also affect LHC@Home, so it is not only SETI, but Milkyway@Home and Einstein@Home works fine.


It affects Docking@Home (which uses the Charmm application, I think), too.
That means it likely affects WCG, also, because they run at least two active tasks using Charmm.

<core_client_version>7.0.24</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
Stack trace (11 frames):
/usr/bin/boinc(boinc_catch_signal+0x65)[0x48f675]
/lib/x86_64-linux-gnu/libc.so.6(+0x364c0)[0x7f5a717984c0]
/lib/x86_64-linux-gnu/libc.so.6(__strcat_chk+0x39)[0x7f5a71868db9]
/usr/bin/boinc[0x412a34]
/usr/bin/boinc[0x412b00]
/usr/bin/boinc[0x43163d]
/usr/bin/boinc[0x431adb]
/usr/bin/boinc[0x41a728]
/usr/bin/boinc[0x4712a4]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f5a7178376d]
/usr/bin/boinc[0x406a65]

</stderr_txt>
]]>


7.0.24 is still the latest available in Synaptic.
Guess I'll go register there and add another whine. ;-)

Profile Ex
Volunteer moderator
Volunteer tester
Avatar
Send message
Joined: 12 Mar 12
Posts: 2895
Credit: 1,730,660
RAC: 1,158
United States
Message 1252395 - Posted: 28 Jun 2012, 0:18:03 UTC
Last modified: 28 Jun 2012, 0:27:17 UTC

Guess I'll go register there and add another whine. ;-)


Thank you...


I tried starting the SRU process, but I'm just a computer geek, not a developer, and hence the SRU process is wayyy over my head. Eventually someone over there will make it happen.


Edit, I see things in place for a replacement package. The SRU process is underway. There is one being built for a proposed SRU, if it builds properly, once it's tested, we could finally see a change in the repository. we'll see how it goes, but finally some good progress.
____________
-Dave #2

3.2.0-33

Previous · 1 · 2

Questions and Answers : Unix/Linux : Process exited with code 193

Copyright © 2014 University of California