Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 6
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 2233 times and has 5 replies Next Thread
Nortnarg
Senior Cruncher
U.S.A.
Joined: Nov 23, 2007
Post Count: 185
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
confused Linux Machine Errors on Beta units

I have one linux machine running Ubuntu Hardy Heron, and it seems all the Beta units are coming out with errors.

Should I take this machine off Beta work??


Result Log

<core_client_version>5.10.45</core_client_version>
<![CDATA[
<message>
process got signal 4
</message>
<stderr_txt>

</stderr_txt>
]]>

UPDATE: The following result log was from a CMD unit from the same device, so not just Beta units. Only have one error on CMD and the rest on Beta. Not sure what these results mean, but identical. I can post messages if needed.


Result Log

<core_client_version>5.10.45</core_client_version>
<![CDATA[
<message>
process got signal 4
</message>
<stderr_txt>

</stderr_txt>
]]>
----------------------------------------

----------------------------------------
[Edit 1 times, last edit by Nortnarg at May 24, 2009 3:34:50 AM]
[May 24, 2009 3:24:31 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Linux Machine Errors on Beta units

Signal 4 = illegal instruction. Have a look at this thread. If you are running a P3/Athlon, the new betas should have addressed the problem, but HCMD2 WUs will fail.
----------------------------------------
[Edit 1 times, last edit by Former Member at May 24, 2009 4:44:57 AM]
[May 24, 2009 4:44:20 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Nortnarg
Senior Cruncher
U.S.A.
Joined: Nov 23, 2007
Post Count: 185
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Linux Machine Errors on Beta units

Thanks Kremmen.

I had no idea this mess existed. I guess I will see about a new profile for my Linux machines to isolate them from HCMD work units. Sheesh!
----------------------------------------

[May 24, 2009 12:31:24 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: Linux Machine Errors on Beta units

The failing of HCMD2 on P3/Athlon under Linux and the reasons has been openly discussed. Setting up a separate profile to attach these devices to is the recommended PTW.

edit: insert recommended
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
----------------------------------------
[Edit 1 times, last edit by Sekerob at May 24, 2009 12:47:35 PM]
[May 24, 2009 12:46:33 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Nortnarg
Senior Cruncher
U.S.A.
Joined: Nov 23, 2007
Post Count: 185
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Linux Machine Errors on Beta units

Thanks,
I was not aware of the situation. Profile created for Linux, so that should work around for now. coffee
----------------------------------------

[May 24, 2009 12:59:20 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Linux Machine Errors on Beta units

The failing of HCMD2 on P3/Athlon under Linux and the reasons has been openly discussed. Setting up a separate profile to attach these devices to is the recommended PTW.


Only in the HCMD2 forum. Lots of users seldom delve into the forums in detail, which is understandable given the large number of threads.

Seems to me that this problem should have been posted in the Known Issues forum as soon as it was discovered. That would have made it far more likely that irregular visitors to the forums would find it quickly. I'll bet there are large numbers of users gradually including HCMD2 in their profiles without ever knowing that some of their machines will consistently error out and, if you have a range of CPU types running a variety of WUs, the reason is not initially obvious.
[May 25, 2009 3:56:21 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread