In fact, the message "no heartbeat from core client" shows up all the time.
For whatever reason the Core Client doesn't respomd to the App. Prior this lead to a signal 11, now with the fixed App it's just a restart.
However with the App not being able to run more than 30 seconds you will hardly get any 'work' done at all. By default it checkpoints every minute; and depending on your machine the time for recovering from a checkpoint might well be more than that.
In any case I'd remove the debugger file (the sig11 has been fixed anyway) and try to find out why the Core Client is gets somewhat stuck on your machine. The task you mentioned apparently ran fine for the first 18 minutes - anything changed then you are aware of (started a particular program, updated the system, whatever)?
I'm not aware of doing a system update, afaik the laptop wasn't even online at that moment. Maybe that's it? Not being online == problems with the core client? I wonder. We discussed that possibility before, so I'll definitely keep the possibility in mind. As for starting up a new program, no, not that I'm aware of. But something odd I remember: I wanted to start up the BOINC manager to have a more comfortable look at my progress and just couldn't. It started to load and then simply hung up. I tried it at least half a dozen times. Nothing I haven't experienced before, but I think it only happens without internet connection. What would you recommend? A core client downgrade? Or just keep watching and collect data?
It looks like newer Core Clients become unresponsive when they loose network connection (probably for DNS timeouts), causing a missing 'hearbeat' on the App side. It's good to know that this is not limited to Linux. For the moment I'd suggest to use an older Core Client.
I downgraded to the old version you linked here. Got a minor flame about the format of my client_state.xml (it didn't like the network statistics section somehow) but otherwise transition went smoothly. Goodness, I forgot how bad my boxes used to benchmark with the older clients :-D
Anyway, we'll see how well crunching goes now.
It looks like newer Core Clients become unresponsive when they loose network connection (probably for DNS timeouts), causing a missing 'hearbeat' on the App side. It's good to know that this is not limited to Linux. For the moment I'd suggest to use an older Core Client.
BM
I was indeed slightly concerned about that with using the VM that I created. I periodically have problems with my cable modem losing sync for a minute or so. What I was finally able to get up and running well was 5.10.28, which from what I gather has the problem. I didn't lose sync for the entire duration of the 6 results that I did in the two different Ubuntu VMs, but I felt like I was taking a chance the whole time...
I've mostly made up my mind not to bother with the VM, as the overhead penalty was severe, but I may test the app if you feel it is needed...
My first 4.24 task that began as 4.14 validated normally. So far, so good. Doesn't look like much of a speedup from 4.14, although I cannot say definitively until there's a few more under the belt.
A couple of points about the app_info.xml file distributed in this package:-
* If you don't have the 4.02 executable and .so files in your project folder you will get harmless complaints about these files being missing. Is it still possible for anyone to still be using these old versions? Couldn't these be safely dropped now?
* The previous versions listed to be handled by 4.24 stop at 4.16. Shouldn't 4.20 also be included?
* There may also be people running the "power user" 4.21 version who want to give 4.24 a spin. Shouldn't you also prepare for that possibility?
A couple of points about the app_info.xml file distributed in this package:-
* If you don't have the 4.02 executable and .so files in your project folder you will get harmless complaints about these files being missing. Is it still possible for anyone to still be using these old versions? Couldn't these be safely dropped now?
* The previous versions listed to be handled by 4.24 stop at 4.16. Shouldn't 4.20 also be included?
* There may also be people running the "power user" 4.21 version who want to give 4.24 a spin. Shouldn't you also prepare for that possibility?
You're absolutely right. I updated the app_info.xml, the package and the md5sum again.
RE: In fact, the message
)
For whatever reason the Core Client doesn't respomd to the App. Prior this lead to a signal 11, now with the fixed App it's just a restart.
However with the App not being able to run more than 30 seconds you will hardly get any 'work' done at all. By default it checkpoints every minute; and depending on your machine the time for recovering from a checkpoint might well be more than that.
In any case I'd remove the debugger file (the sig11 has been fixed anyway) and try to find out why the Core Client is gets somewhat stuck on your machine. The task you mentioned apparently ran fine for the first 18 minutes - anything changed then you are aware of (started a particular program, updated the system, whatever)?
BM
BM
I'm not aware of doing a
)
I'm not aware of doing a system update, afaik the laptop wasn't even online at that moment. Maybe that's it? Not being online == problems with the core client? I wonder. We discussed that possibility before, so I'll definitely keep the possibility in mind. As for starting up a new program, no, not that I'm aware of. But something odd I remember: I wanted to start up the BOINC manager to have a more comfortable look at my progress and just couldn't. It started to load and then simply hung up. I tried it at least half a dozen times. Nothing I haven't experienced before, but I think it only happens without internet connection. What would you recommend? A core client downgrade? Or just keep watching and collect data?
This error is not from
)
This error is not from Linux.
But it is a error with lost internet connection.
Anders n
It looks like newer Core
)
It looks like newer Core Clients become unresponsive when they loose network connection (probably for DNS timeouts), causing a missing 'hearbeat' on the App side. It's good to know that this is not limited to Linux. For the moment I'd suggest to use an older Core Client.
BM
BM
I downgraded to the old
)
I downgraded to the old version you linked here. Got a minor flame about the format of my client_state.xml (it didn't like the network statistics section somehow) but otherwise transition went smoothly. Goodness, I forgot how bad my boxes used to benchmark with the older clients :-D
Anyway, we'll see how well crunching goes now.
RE: It looks like newer
)
I was indeed slightly concerned about that with using the VM that I created. I periodically have problems with my cable modem losing sync for a minute or so. What I was finally able to get up and running well was 5.10.28, which from what I gather has the problem. I didn't lose sync for the entire duration of the 6 results that I did in the two different Ubuntu VMs, but I felt like I was taking a chance the whole time...
I've mostly made up my mind not to bother with the VM, as the overhead penalty was severe, but I may test the app if you feel it is needed...
Brian
My first 4.24 task that began
)
My first 4.24 task that began as 4.14 validated normally. So far, so good. Doesn't look like much of a speedup from 4.14, although I cannot say definitively until there's a few more under the belt.
RE: A new Linux App is
)
A couple of points about the app_info.xml file distributed in this package:-
* The previous versions listed to be handled by 4.24 stop at 4.16. Shouldn't 4.20 also be included?
* There may also be people running the "power user" 4.21 version who want to give 4.24 a spin. Shouldn't you also prepare for that possibility?
Cheers,
Gary.
RE: RE: A new Linux App
)
You're absolutely right. I updated the app_info.xml, the package and the md5sum again.
Thanks,
BM
BM
md5sum does not match now for
)
md5sum does not match now for me (yesterday night it matched on another machine)
Now I'm getting:
56cb787158feb2d19af53e53cc169784
The app works, but I still get the error message "missing application file einstein_S5R3_4.02_ ..."