Linux 64 error code 22

Author	Message
Kalessin Volunteer tester Send message Joined: 19 Jan 06 International SETI.Germany Credit: 44,825.1 RAC: 0.00 Joined: Jan 19, 2006 Verified: Jan 11, 2009 Dubloons: 3 Pieces of Eight: 7 Punishment: Mess Duty	Message 6579 - Posted: 27 Sep 2007 \| 20:59:56 UTC
Me as well as one of my teammates have a problem with our Linux 64 PCs. All results error out with code 22 He has 5.10.8, and i have 5.8.15 Does anyone know? ____________ Dragons can fly because they don't fit into pirate ships
ID: 6579 \| Rating: 0 \| rate: / Reply Quote

Wormholio Captain Send message Joined: 6 Jun 04 United States Away Credit: 4,009.8 RAC: 0.00 Joined: Jun 6, 2004 Verified: Mar 13, 2008 Dubloons: 3 Pieces of Eight: 10 Punishment: Aztec curse	Message 6589 - Posted: 29 Sep 2007 \| 12:27:14 UTC
Can you point to some Results, so we can look at the error logs? ____________ -- Eric Myers "Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats
ID: 6589 \| Rating: 0 \| rate: / Reply Quote

Ageless Chief Petty Officer Volunteer tester Send message Joined: 20 Jul 04 Netherlands Machinae Supremacy Credit: 1,295.9 RAC: 0.00 Joined: Jul 20, 2004 Verified: Jul 9, 2011 Dubloons: 3 Pieces of Eight: 7 Punishment: Cat o' Nine Tails	Message 6591 - Posted: 29 Sep 2007 \| 16:40:40 UTC Last modified: 29 Sep 2007 \| 16:41:40 UTC
Fom my FAQs: When running a 64-bit Linux on a project that sends 32-bit applications only, you can run into results erroring out with process exited with code 22. The explanation for this is that 32-bit binaries don't just work on every 64-bit Linux. If for example you install a fresh Ubuntu 6.10 or 7.04, 32-bit binaries won't work. They are not even recognized as valid executables. You first have to install the ia32 package and dependent packages. Further, for programs that link with the graphic library, you will manually have to copy a 32-bit libglut library to the usr/lib32 directory. If after this you still get client errors, post on the forums of the project that you have this problem and ran ldd on the executable in the projects directory to see what libraries are missing. Post which libraries these are and ask for instructions on how to get them. You do know that BOINC 5.8.x doesn't get 32bit applications, even if the project updated its server code to send 32bit apps to 64bit clients? You need a 5.10 BOINC for that. ____________ Jord. The BOINC FAQ Service.
ID: 6591 \| Rating: 0 \| rate: / Reply Quote

Wormholio Captain Send message Joined: 6 Jun 04 United States Away Credit: 4,009.8 RAC: 0.00 Joined: Jun 6, 2004 Verified: Mar 13, 2008 Dubloons: 3 Pieces of Eight: 10 Punishment: Aztec curse	Message 6593 - Posted: 30 Sep 2007 \| 1:41:38 UTC
And in other news, I'm building a 64-bit Linux box (for MythTV), and I should be able to use it to build real 64-bit apps. ____________ -- Eric Myers "Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats
ID: 6593 \| Rating: 0 \| rate: / Reply Quote

Kalessin Volunteer tester Send message Joined: 19 Jan 06 International SETI.Germany Credit: 44,825.1 RAC: 0.00 Joined: Jan 19, 2006 Verified: Jan 11, 2009 Dubloons: 3 Pieces of Eight: 7 Punishment: Mess Duty	Message 6598 - Posted: 4 Oct 2007 \| 18:15:51 UTC - in response to Message 6589.
Wormholio wrote: Can you point to some Results, so we can look at the error logs? I'll try: mine (5.8.15) 557105 557104 557098 557097 556118 556117 two of michael's (5.10.8) 557696 557697 Stainless Cutlass wrote: When running a 64-bit Linux on a project that sends 32-bit applications only, you can run into results erroring out with process exited with code 22. The explanation for this is that 32-bit binaries don't just work on every 64-bit Linux. If for example you install a fresh Ubuntu 6.10 or 7.04, 32-bit binaries won't work. They are not even recognized as valid executables. I think that was the problem, as we both had a Ubuntu 7.04 I just read under applications that there was one for 64bit and didn't understand that it was a 32bit app. which was sent out to 64bit machines as well. Stainless Cutlass wrote: You do know that BOINC 5.8.x doesn't get 32bit applications, even if the project updated its server code to send 32bit apps to 64bit clients? You need a 5.10 BOINC for that. No I didn't know, and thats probably not the whole truth, as I received WUs. But I was running the 5.8.15 from Augustine, perhaps this explaines why I received WUs regardless of the 5.8.xxx Wormholio wrote: And in other news, I'm building a 64-bit Linux box (for MythTV), and I should be able to use it to build real 64-bit apps. And that I will gladly test again with my linux-crunchgnome! ____________ Dragons can fly because they don't fit into pirate ships
ID: 6598 \| Rating: 0 \| rate: / Reply Quote

Ageless Chief Petty Officer Volunteer tester Send message Joined: 20 Jul 04 Netherlands Machinae Supremacy Credit: 1,295.9 RAC: 0.00 Joined: Jul 20, 2004 Verified: Jul 9, 2011 Dubloons: 3 Pieces of Eight: 7 Punishment: Cat o' Nine Tails	Message 6599 - Posted: 4 Oct 2007 \| 21:21:15 UTC - in response to Message 6598.
Kalessin wrote: Stainless Cutlass wrote: You do know that BOINC 5.8.x doesn't get 32bit applications, even if the project updated its server code to send 32bit apps to 64bit clients? You need a 5.10 BOINC for that. No I didn't know, and thats probably not the whole truth, as I received WUs. But I was running the 5.8.15 from Augustine, perhaps this explaines why I received WUs regardless of the 5.8.xxx If you check here you'll see that there are no Berkeley built 64 bit 5.8 versions. If I remember correctly Agustine ported a 5.8 version to 64 bit. And even if he used later code, by editing versions.h before compiling it you can give it any number you like. When Berkeley started releasing its 5.9.4+ clients for the 64 bit platform the whole fight started on what the platform name ought to be, the one used by Augustine (windows_amd64), or the one used by BOINC (windows_x86_64). ;-) ____________ Jord. The BOINC FAQ Service.
ID: 6599 \| Rating: 0 \| rate: / Reply Quote

Author

Message

Kalessin
Volunteer tester
Avatar

Send message
Joined: 19 Jan 06

International
SETI.Germany
Credit: 44,825.1
RAC: 0.00

Joined: Jan 19, 2006
Verified: Jan 11, 2009
Dubloons: 3
Pieces of Eight: 7
Punishment: Mess Duty

Me as well as one of my teammates have a problem with our Linux 64 PCs.
All results error out with code 22
He has 5.10.8, and i have 5.8.15

Does anyone know?
____________
Dragons can fly because they don't fit into pirate ships

ID: 6579 | Rating: 0 | rate:

Reply Quote

Wormholio
Captain
Avatar

Send message
Joined: 6 Jun 04

United States
Away
Credit: 4,009.8
RAC: 0.00

Joined: Jun 6, 2004
Verified: Mar 13, 2008
Dubloons: 3
Pieces of Eight: 10
Punishment: Aztec curse

Can you point to some Results, so we can look at the error logs?

____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

ID: 6589 | Rating: 0 | rate:

Reply Quote

Ageless
Chief Petty Officer
Volunteer tester
Avatar

Send message
Joined: 20 Jul 04

Netherlands
Machinae Supremacy
Credit: 1,295.9
RAC: 0.00

Joined: Jul 20, 2004
Verified: Jul 9, 2011
Dubloons: 3
Pieces of Eight: 7
Punishment: Cat o' Nine Tails

Fom my FAQs:

When running a 64-bit Linux on a project that sends 32-bit applications only, you can run into results erroring out with process exited with code 22.

The explanation for this is that 32-bit binaries don't just work on every 64-bit Linux. If for example you install a fresh Ubuntu 6.10 or 7.04, 32-bit binaries won't work. They are not even recognized as valid executables. You first have to install the ia32 package and dependent packages. Further, for programs that link with the graphic library, you will manually have to copy a 32-bit libglut library to the usr/lib32 directory.

If after this you still get client errors, post on the forums of the project that you have this problem and ran ldd on the executable in the projects directory to see what libraries are missing. Post which libraries these are and ask for instructions on how to get them.

You do know that BOINC 5.8.x doesn't get 32bit applications, even if the project updated its server code to send 32bit apps to 64bit clients? You need a 5.10 BOINC for that.
____________
Jord.

The BOINC FAQ Service.

ID: 6591 | Rating: 0 | rate:

Reply Quote

Wormholio
Captain
Avatar

Send message
Joined: 6 Jun 04

United States
Away
Credit: 4,009.8
RAC: 0.00

Joined: Jun 6, 2004
Verified: Mar 13, 2008
Dubloons: 3
Pieces of Eight: 10
Punishment: Aztec curse

And in other news, I'm building a 64-bit Linux box (for MythTV), and I should be able to use it to build real 64-bit apps.

____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

ID: 6593 | Rating: 0 | rate:

Reply Quote

Kalessin
Volunteer tester
Avatar

Send message
Joined: 19 Jan 06

International
SETI.Germany
Credit: 44,825.1
RAC: 0.00

Joined: Jan 19, 2006
Verified: Jan 11, 2009
Dubloons: 3
Pieces of Eight: 7
Punishment: Mess Duty

Wormholio wrote:

Can you point to some Results, so we can look at the error logs?

I'll try:

mine (5.8.15)
557105
557104
557098
557097
556118
556117

two of michael's (5.10.8)
557696
557697

Stainless Cutlass wrote:

When running a 64-bit Linux on a project that sends 32-bit applications only, you can run into results erroring out with process exited with code 22.
The explanation for this is that 32-bit binaries don't just work on every 64-bit Linux. If for example you install a fresh Ubuntu 6.10 or 7.04, 32-bit binaries won't work. They are not even recognized as valid executables.

I think that was the problem, as we both had a Ubuntu 7.04
I just read under applications that there was one for 64bit and didn't understand that it was a 32bit app. which was sent out to 64bit machines as well.

Stainless Cutlass wrote:

You do know that BOINC 5.8.x doesn't get 32bit applications, even if the project updated its server code to send 32bit apps to 64bit clients? You need a 5.10 BOINC for that.

No I didn't know, and thats probably not the whole truth, as I received WUs. But I was running the 5.8.15 from Augustine, perhaps this explaines why I received WUs regardless of the 5.8.xxx

Wormholio wrote:

And in other news, I'm building a 64-bit Linux box (for MythTV), and I should be able to use it to build real 64-bit apps.

And that I will gladly test again with my linux-crunchgnome!

____________
Dragons can fly because they don't fit into pirate ships

ID: 6598 | Rating: 0 | rate:

Reply Quote

Ageless
Chief Petty Officer
Volunteer tester
Avatar

Send message
Joined: 20 Jul 04

Netherlands
Machinae Supremacy
Credit: 1,295.9
RAC: 0.00

Joined: Jul 20, 2004
Verified: Jul 9, 2011
Dubloons: 3
Pieces of Eight: 7
Punishment: Cat o' Nine Tails

Kalessin wrote:

Stainless Cutlass wrote:
You do know that BOINC 5.8.x doesn't get 32bit applications, even if the project updated its server code to send 32bit apps to 64bit clients? You need a 5.10 BOINC for that.

No I didn't know, and thats probably not the whole truth, as I received WUs. But I was running the 5.8.15 from Augustine, perhaps this explaines why I received WUs regardless of the 5.8.xxx

If you check here you'll see that there are no Berkeley built 64 bit 5.8 versions. If I remember correctly Agustine ported a 5.8 version to 64 bit. And even if he used later code, by editing versions.h before compiling it you can give it any number you like.

When Berkeley started releasing its 5.9.4+ clients for the 64 bit platform the whole fight started on what the platform name ought to be, the one used by Augustine (windows_amd64), or the one used by BOINC (windows_x86_64). ;-)

____________
Jord.

The BOINC FAQ Service.

ID: 6599 | Rating: 0 | rate:

Reply Quote

Post to thread

@

Linux 64 error code 22