No work for x86_64-pc-linux-gnu ?
4 Nov 2009 1:29:15 UTC
Topic 194609
(moderation:
I used to know how to fix this, but I am stuck now. I have 4 almost identical machines, 2 are fine, 2 get:
Message from server: platform 'x86_64-pc-linux-gnu' not found
and no work. Any help out there?
No work for x86_64-pc-linux-gnu ?
)
There's always help out there - somewhere :-).
All your linux machines now seem to have (quite recent) tasks on board. Has the problem now cleared itself up?
E@H doesn't have 64 bit apps. The 32 bit apps will run on a 64 bit OS as long as the 32 bit compatibility libs are installed. That shouldn't be your problem if the same installation exists on all 4 machines. Anyway, missing libs would give a runtime error rather than a refusal to send work. For the server to be unhappy with the platform, there must be some difference in how a 'problem' machine describes itself to the server. You could try examining the 'sched_request' and 'sched_reply' traffic between client and server to see what's different between a 'good' machine and a 'problem' machine. This traffic is contained in .xml files in your BOINC data directory and you can browse them with any suitable text editor. You should be able to find and tags that should give you a clue as to what's causing the problem.
Cheers,
Gary.
The two machines in question
)
The two machines in question are/were detached after I gave up on them.
The obvious difference in sched_request_einstein.phys.uwm.edu.xml
is that the ones that succeed have:
x86_64-pc-linux-gnu
i686-pc-linux-gnu
where the ones that fail do not have the entry.
* Just checked the client_state.xml file. Working machines have the tag the failing ones don't. Now to find out where that tag is generated..
* Final edit- Found it. Boinc Linux checks for 'file' in the the /usr/bin directory when it starts.
If it finds it, it assumes that it can run 32 bit apps.
The two machines in question did not have this utility installed.
They do now- and now I am getting work.
RE: Boinc Linux checks for
)
Well done on working that out! Are you sure it's just the presence or absence of 'file' that is tested? I would have thought that maybe 'file' gets used to test the type of some particular file and if that type is present, the tag can be used to indicate that 32 bit apps are OK.
'file' is a basic unix utility like 'cat' ot 'diff'. It must be rather unusual for it not to be there by default. Obviously the BOINC devs thought it was safe to assume it would always be present. Any idea of how/why it was missing?
Cheers,
Gary.
Perhaps ohiomike
)
Perhaps ohiomike misinterpreted `file xxxx` as 'file'.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: Perhaps ohiomike
)
I haven't checked the sources but maybe LINUX BOINC is doing
file /usr/bin/file
to see if it's 32 or 64 bit :-)...
CU
Bikeman