just upgraded one host to ubuntu 12.04 and now this happens:

<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)[0x7fe8e7dbc4c0]
/lib/x86_64-linux-gnu/libc.so.6(__strcat_chk+0x39)[0x7fe8e7e8cdb9]
/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)[0x7fe8e7da776d]
/usr/bin/boinc[0x406a65]

</stderr_txt>


any ideas?

---

It looks like there is a problem with your libc.so.6

The apps for NumberFields are static (ldd confirms this) so they don't rely on any libc library (dynamically at least). Might the client depend on libc.so.6?

Does this happen with other projects also, or just NumberFields?

Looks like the boinc client is bombing. Can you run under strace or gdb?

It looks like there is a problem with your libc.so.6

The apps for NumberFields are static (ldd confirms this) so they don't rely on any libc library (dynamically at least). Might the client depend on libc.so.6?

the client itself works - it's just the numberfields app which crash right away.
distrtgen and wuprop still work.

but maybe other projects will be affected also.

i'll try to check tomorrow. maybe the upgrade process turned out very bright and got rid of some of the libs. :(

but i'm a windows-guy and only a linux user.. :|

---

It looks like there is a problem with your libc.so.6

The apps for NumberFields are static (ldd confirms this) so they don't rely on any libc library (dynamically at least). Might the client depend on libc.so.6?

the client itself works - it's just the numberfields app which crash right away.
distrtgen and wuprop still work.

but maybe other projects will be affected also.

i'll try to check tomorrow. maybe the upgrade process turned out very bright and got rid of some of the libs. :(

but i'm a windows-guy and only a linux user.. :|

Did you also upgrade the boinc client? If so, maybe it's the newer client that's the problem???

Did you also upgrade the boinc client? If so, maybe it's the newer client that's the problem???

the newer client came with the upgrade. but the client does work, it's just some projects which are showing the same error.

this defintely looks like they fouled up something inside the reposetory. some non-boinc apps are affected also.

this defintely looks like they fouled up something inside the reposetory. some non-boinc apps are affected also.

Did you ever figure out what the problem was with this, or find a work-around?

I ask because another user is getting the exact same error message.

this defintely looks like they fouled up something inside the reposetory. some non-boinc apps are affected also.

Did you ever figure out what the problem was with this, or find a work-around?

I ask because another user is getting the exact same error message.

2 things: several problems with libc6 all over the place and 2nd, boinc 7.0.25 is one of the apps.

no cure available right now, but it's probably just a matter of time.

at least it seems there is nothing you can do about it.

Hi Fellow Users:

I just wanted to write to say that I am also getting errors but on a different Version---BOINC version 7.0.24

It is affecting all Projects that I signed up for, not only in number fields.

If I apply for a new project it does the same output file error.

The error is saying missing output file before erroring out.

It runs for about a second before showing error.

I went through 10 errors before I noticed it and stopped the computer from running any more.

I then tried adding another project and it happened the same. Same error message.

This is only happening for the only computer that I upgraded to Ubuntu 12.04 yesterday.

The upgraded computer, I took offline runnig Boinc until I hear that a fix is there to add or that it is in the update manager to be fix with.

I have not looked into it lately, but to me it is similar to a problem I had when I first started in 2010 when a lib I did not install correctly was causing the output file to be absent after trying to run.

I do not remember what lib file it was but I do remember that I found that I needed it in a thread in Einstein@Home. I will be looking to find that thread again and looking at all the list of needed files and in making sure I still have them all.

If I do not have all the needed files then reloading them back into the system. Then try running it again. If I have success I will post the list of missing files for other to look into and see if it helps them.

I agree that the upgrade may have removed needed and necessary files on the Boinc Project and that the main Boinc page should recomend that if they upgrade a users system by using the desktop ubuntu 12.04 amd64.iso that there will be reported problems until fixed.

Thanks.....post if you find an answer to this before I do or hear of a fix.


Domain name timothy-AcerPower-S280
Local Standard Time UTC -5 hours
Name timothy-AcerPower-S280
Created 3 May 2012 | 22:02:30 UTC
Total credit 0
Average credit 0.00
Cross project credit
CPU type GenuineIntel
Intel(R) Celeron(R) CPU 3.06GHz [Family 15 Model 4 Stepping 9]
Number of processors 1
Coprocessors ---
Operating System Linux
3.2.0-24-generic
BOINC version 7.0.24
Memory 869.46 MB
Cache 256 KB
Swap space 894 MB
Total disk space 13.98 GB
Free Disk Space 7.61 GB
Measured floating point speed 1667.38 million ops/sec
Measured integer speed 5010.6 million ops/sec
Average upload rate 16.73 KB/sec
Average download rate 708.19 KB/sec
Average turnaround time 0 days
Application details Show
Tasks 18
Number of times client has contacted server 6
Last time contacted server 4 May 2012 | 0:47:09 UTC
% of time BOINC is running 99.9656 %
While BOINC running, % of time work is allowed 99.9815 %


Thanks,

Timothy

---

Thanks for the info Timothy. Please let us know if you learn anything new.

I had a similar problem a few weeks ago when I installed BOINC on a virtual machine running fedora core 16. My work around was to install an older version of the boinc client/manager. Version 6.10.58 works great for me.

I just checked the latest results being returned and there are now at least 2 other users with this exact same problem. They too are using version 7.0.24 of the client.

I'm in the process of updating to Ubuntu 12.04 so I don't know if this fix actually works.

Edit added:

It seems like there's always trouble with the Linux builds. The builds from the BOINC site work *only* on the version of Ubuntu the BOINC devs use. They use only the current LTS version. The repositories are usually several months behind the recommended BOINC version. Well I've had enough of that nonsense so I'm going to learn how to build BOINC myself, write up the procedure and make it available to all.

This message from the T4T forum has a link to instructions for compiling on Fedora. The instructions are in French but they translate well at online translators. They explain how to get the latest source, how to setup the directories and run the compiler. Someone in the thread has tried the instructions on Ubuntu with some success, got the client to compile but not the manager. I've tried and get the same results, client compiles but not manager. Does anybody know what one has to do to get the manager to compile?

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux

I'm in the process of updating to Ubuntu 12.04 so I don't know if this fix actually works.

Edit added:

It seems like there's always trouble with the Linux builds. The builds from the BOINC site work *only* on the version of Ubuntu the BOINC devs use. They use only the current LTS version. The repositories are usually several months behind the recommended BOINC version. Well I've had enough of that nonsense so I'm going to learn how to build BOINC myself, write up the procedure and make it available to all.

YES - complete nonsense.

12.04 IS the current LTS.

so once again they have pushed out untested crap.

but 7.0.27 seems to work..