I pulled out my network cable a few times and the app carried on. But the difference is this time the manager didn't hang even when I did a scheduler rpc with the network down. So slightly inconclusive? The morning I had issues, the manager was completely unresponsive. And if it's important, I don't run the manager all the time. I start it from the terminal when I need to check on something I can't see with `tail` on the logs.
I pulled out my network cable a few times and the app carried on. But the difference is this time the manager didn't hang even when I did a scheduler rpc with the network down. So slightly inconclusive? The morning I had issues, the manager was completely unresponsive. And if it's important, I don't run the manager all the time. I start it from the terminal when I need to check on something I can't see with `tail` on the logs.
I have the same experiece , it does not happen every time (far from) I happen to loose the "net". The problem is that when it happens I can't open the manager to se the logs :(
No clue. The one on the webpage is correct on the server side and when downloading it to my local machine.
Quote:
The app works, but I still get the error message "missing application file einstein_S5R3_4.02_ ..."
Surprises me a bit, but good to know. Just for the records: which Client version are you using? It's just a warning anyway.
Bernd, I've just downloaded the new package to my other linux box, that had 4.24 allready running from yesterday. The md5sum matches now, you are right (I will try to see why it does not match in my laptop) but the warning about 4.02 missing remains the same in both systems. One of them uses BOINC 5.8.16 and the other one BOINC 5.10.28
In app_info.xml I see the following section:
einstein_S5R3
402
einstein_S5R3_4.02_i686-pc-linux-gnu
einstein_S5R3_4.02_i686-pc-linux-gnu.so
I know it's only a warning, so it does not really matter.
But I think there should be a link to 4.24 app file after
I've attached 5 AMD hosts using 64b linux and using the "beta" app. I've also attached one AMD host using windows. These machines (except the windows only laptop) are dual boot. (note: while running linux they are equal share with Rosie and Boincsimap as well)
Hi Brian
If I were to record data from my work here, what bits of the "Task ID" (old result ID) would I need to extract and record to cover nearly any examination I might do later? I see one really long string in the res ID about different freqs. Do I need them all? etc etc
The last time I was here, I hit my 200K goal before moving on. It's good to see Bernd posting again. Last time I was here, it was pretty quiet, if I remember properly.
I've attached 5 AMD hosts using 64b linux and using the "beta" app. I've also attached one AMD host using windows. These machines (except the windows only laptop) are dual boot. (note: while running linux they are equal share with Rosie and Boincsimap as well)
Hi Brian
If I were to record data from my work here, what bits of the "Task ID" (old result ID) would I need to extract and record to cover nearly any examination I might do later? I see one really long string in the res ID about different freqs. Do I need them all? etc etc
The last time I was here, I hit my 200K goal before moving on. It's good to see Bernd posting again. Last time I was here, it was pretty quiet, if I remember properly.
thanks
tony
A couple of threads to whet your appetite:
S5R3 - cyclical variation in runtime for different tasks in the same block. Visualization of S5R2 / S5R3 difference - tools for seeing what you've found in your own results.
With regard to the name - I would pull out h1_0785.85_S5R2__303_S5R3a_1 as two separate fields. You'll find that the red number is slow-changing - you'll do many tasks from the same block - and the green field is quick-changing - if you work hard at it, you can even get a sequential range for comparisons.
As to recording data of WU you process, I now use a modified version of the lightweight, open source "Muffin" web proxy to intercept communication between the boinc core clients in my LAN and the projects sites, so if you are into JAVA programming it's easy to extend "Muffin" to implement whatever data recording you want. E.g. I use it to dump the results itself , see the Visualization threat mentioned above. This is an alternative to parsing the projects' web pages.
Bernd: Apparently, with the ancient core client, I have no more app restarts. It also seems to have fixed the annoying "signal 6 on boot-up" error that has been affecting this box for a while (with Einstein online, but it still seems to have been a core client issue).
The app works, but I still get the error message "missing application file einstein_S5R3_4.02_ ..."
I believe this is because there are still references to the 4.02 files in the latest app_info.xml.
If you look at the original version you will see that there are two places where 4.02 is referred to. The first is between ... tags. The second is a little later between ... tags. In the latest version of app_info.xml only the first of the above two instances has been removed. Before I fired up the 4.24 version, I removed both of the above instances and I didn't subsequently get any 4.02 warning messages.
I pulled out my network cable
)
I pulled out my network cable a few times and the app carried on. But the difference is this time the manager didn't hang even when I did a scheduler rpc with the network down. So slightly inconclusive? The morning I had issues, the manager was completely unresponsive. And if it's important, I don't run the manager all the time. I start it from the terminal when I need to check on something I can't see with `tail` on the logs.
Kathryn :o)
Einstein@Home Moderator
RE: I pulled out my network
)
I have the same experiece , it does not happen every time (far from) I happen to loose the "net". The problem is that when it happens I can't open the manager to se the logs :(
Anders n
RE: md5sum does not match
)
No clue. The one on the webpage is correct on the server side and when downloading it to my local machine.
Surprises me a bit, but good to know. Just for the records: which Client version are you using? It's just a warning anyway.
Thanks for the report.
BM
BM
RE: The problem is that
)
The logs are plain text files in the BOINC directory (stdoutdae.txt and stderrdae.txt); you don't need to use the manager.
BM
BM
RE: No clue. The one on
)
Bernd, I've just downloaded the new package to my other linux box, that had 4.24 allready running from yesterday. The md5sum matches now, you are right (I will try to see why it does not match in my laptop) but the warning about 4.02 missing remains the same in both systems. One of them uses BOINC 5.8.16 and the other one BOINC 5.10.28
In app_info.xml I see the following section:
einstein_S5R3
402
einstein_S5R3_4.02_i686-pc-linux-gnu
einstein_S5R3_4.02_i686-pc-linux-gnu.so
I know it's only a warning, so it does not really matter.
But I think there should be a link to 4.24 app file after
I've attached 5 AMD hosts
)
I've attached 5 AMD hosts using 64b linux and using the "beta" app. I've also attached one AMD host using windows. These machines (except the windows only laptop) are dual boot. (note: while running linux they are equal share with Rosie and Boincsimap as well)
Hi Brian
If I were to record data from my work here, what bits of the "Task ID" (old result ID) would I need to extract and record to cover nearly any examination I might do later? I see one really long string in the res ID about different freqs. Do I need them all? etc etc
The last time I was here, I hit my 200K goal before moving on. It's good to see Bernd posting again. Last time I was here, it was pretty quiet, if I remember properly.
thanks
tony
RE: I've attached 5 AMD
)
A couple of threads to whet your appetite:
S5R3 - cyclical variation in runtime for different tasks in the same block.
Visualization of S5R2 / S5R3 difference - tools for seeing what you've found in your own results.
With regard to the name - I would pull out h1_0785.85_S5R2__303_S5R3a_1 as two separate fields. You'll find that the red number is slow-changing - you'll do many tasks from the same block - and the green field is quick-changing - if you work hard at it, you can even get a sequential range for comparisons.
Hi Astro, Welcome (back)
)
Hi Astro,
Welcome (back) to E@H. Having read about your early Pentium experiments on Seti@Home, I guess this thread might be of interest for you as well:
Vintage Computers and Einstein@Home
As to recording data of WU you process, I now use a modified version of the lightweight, open source "Muffin" web proxy to intercept communication between the boinc core clients in my LAN and the projects sites, so if you are into JAVA programming it's easy to extend "Muffin" to implement whatever data recording you want. E.g. I use it to dump the results itself , see the Visualization threat mentioned above. This is an alternative to parsing the projects' web pages.
CU
Bikeman
Bernd: Apparently, with the
)
Bernd: Apparently, with the ancient core client, I have no more app restarts. It also seems to have fixed the annoying "signal 6 on boot-up" error that has been affecting this box for a while (with Einstein online, but it still seems to have been a core client issue).
Josep
)
Josep wrote:-
I believe this is because there are still references to the 4.02 files in the latest app_info.xml.
If you look at the original version you will see that there are two places where 4.02 is referred to. The first is between ... tags. The second is a little later between ... tags. In the latest version of app_info.xml only the first of the above two instances has been removed. Before I fired up the 4.24 version, I removed both of the above instances and I didn't subsequently get any 4.02 warning messages.
In any case, the warnings are quite harmless.
Cheers,
Gary.