process died
29 Nov 2009 18:24:02 UTC
Topic 194642
(moderation:
Hello!
I tried today to set up boinc on my vserver. Connecting to the einstein page, it gets various tasks, but immediately reports errors.
The message box reports something like:
...computation for task ... finished
...output file ... absent
The message appears several times, finishing with "reached daily qouta".
When I look at the process overview on the vserver, I see some defunct einstein processes. Seems they died.
It's an opteron (2376 HE) system running debian lenny.
Any suggestions?
thx & rgds!
process died
)
Check that the BOINC user has sufficient access rights on all BOINC directories and that all executables have the x-bit set.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Thx for response! Actually
)
Thx for response!
Actually I did the thing twice within an hour: once on my home server (without any problems) and once on the vserver (with prpblems described). Both systems debian lenny.
I just run apt-get install, updated the host/pwd for remote administration, logged in via the windows noinc gui and the rest was done automatically by boing.
Which files shall I check and which options? Preferences (override file) tells me 2GB/4GB ram and 9GB disk usage.
Thx again.
The error messages tell that
)
The error messages tell that the tasks did not just encounter an error but didn't even start to run, hence the "output file absent" message. That hints at the points I mentioned, but I can't give you more detailed advice, since it's been a long time that I used unix. There are other threads here with more info and links to readmes.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: Actually I did the
)
Your two linux hosts have quite different kernels. It looks like your AMD Turion may have a 32 bit OS whilst your Opteron has a 64 bit one. Einstein apps are 32 bit apps and will run just fine on a 64 bit OS as long as that OS has the necessary 32 bit compatibility libs installed. Some distros (eg Ubuntu) apparently don't have those libs installed automatically. I don't know if this is your problem or not.
Try reviewing this page. There is a section on 64 bit considerations near the bottom. There are also links to information about installing on various distros including Debian. Perhaps something there might help.
Cheers,
Gary.
Yesterday I had some time to
)
Yesterday I had some time to check the problem again. I looked up the Einstein binaries and tried to run them manually. As expected, they did not (bash throwing strange errors).
Since I wasn't aware that the einstein binaries are 32bit, which do not run on 64 bit linux natively, I did as suggested and installed the 32bit compatibility package, and now it runs like a kitten. :-)
All actually to be done on Debian is "apt-get install ia32-libs".
Thank you Gary!
btw: this kind of problem is described here in the forum:
http://einsteinathome.org/node/193701
RE: ... installed the 32bit
)
I'm glad that sorted things out for you.
Yes, if you do a search for 'compatibility lib' (over 12 months) you will probably find quite a few hits as this problem does come up reasonably regularly. I think it may have been Bikeman who first sorted it out and that thread you identified may well have been when he did it. From previous instances of this problem, I knew that at least Ubuntu and Fedora were affected and since Ubuntu is based on Debian, I guessed that your problem may have had the same cause.
Cheers,
Gary.