At the end of the day yesterday a simple cut-and-paste misinterpreted by a terminal window introduced an extra line feed to the /etc/exports file on our Network Appliance filer (which hosts our home accounts, web sites, /usr/local, etc.) which rendered its root (/) mount read-only. Of course, you need read-write access to update the exports file. This was a bit of a conundrum, with the added pressure of "mount rot" quickly creeping through our network and slowing machines to a crawl (hence the minor outage which very few seemed to notice). This sent me, Jeff, and Eric into a fit of head scratching, with Eric finally discovering that, even though we couldn't re-export "/" on the simple filer command line, we could freshly export "/." with read-write access to a machine that hadn't quite hung up yet, and fix the offending file. After some reboots to clean the pipes we were back to normal.

I think I fixed the weird "top computers" sorting problems. I believe somebody else made an update trying to optimize it during our recent database panic without realizing it broke the sort logic. Fair enough.

Other than that, Jeff and I worked to get the new server "bane" on line. Yup, we continue to stick with the darth naming convention for now. We made it a third public web server for a second there to test the plumbing, but took it back offline for now. We need to tighten some screws before making it a real production web server.

- Matt

____________
-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

At the end of the day yesterday a simple cut-and-paste misinterpreted by a terminal window introduced an extra line feed to the /etc/exports file on our Network Appliance filer (which hosts our home accounts, web sites, /usr/local, etc.) which rendered its root (/) mount read-only. Of course, you need read-write access to update the exports file. This was a bit of a conundrum, with the added pressure of "mount rot" quickly creeping through our network and slowing machines to a crawl (hence the minor outage which very few seemed to notice). This sent me, Jeff, and Eric into a fit of head scratching, with Eric finally discovering that, even though we couldn't re-export "/" on the simple filer command line, we could freshly export "/." with read-write access to a machine that hadn't quite hung up yet, and fix the offending file. After some reboots to clean the pipes we were back to normal.

I think I fixed the weird "top computers" sorting problems. I believe somebody else made an update trying to optimize it during our recent database panic without realizing it broke the sort logic. Fair enough.

Other than that, Jeff and I worked to get the new server "bane" on line. Yup, we continue to stick with the darth naming convention for now. We made it a third public web server for a second there to test the plumbing, but took it back offline for now. We need to tighten some screws before making it a real production web server.

- Matt

Friday again.
The sort fix for top computers that you made indeed worked for a while, but it didn't stick.
Have a restful weekend and remember that your goals in life have more patience than you do.
It seems to be broken again
____________
When we finally figure it all out, all the rules will change and we can start all over again.

The sort fix for top computers that you made indeed worked for a while, but it didn't stick.
Have a restful weekend and remember that your goals in life have more patience than you do.
It seems to be broken again

I have noticed since the download of the 5.10.7 that I have quite a few 'aborted' WUs; seventy (70) of them as a matter of interest. As well when I do an update I have noticed that two things happen. When the initial update is done there is an 'http error' then the seconds later a second update is done, successfully as per quoted text, save for those 'aborted by project'.

I have noticed since the download of the 5.10.7 that I have quite a few 'aborted' WUs; seventy (70) of them as a matter of interest. As well when I do an update I have noticed that two things happen. When the initial update is done there is an 'http error' then the seconds later a second update is done, successfully as per quoted text, save for those 'aborted by project'.

Why you get the HTTP error, I do not know. But assuming you are on Broadband, always on. If you set the connection interval to 0, and use the 'Maintain enough work for an additional x days' as your cache setting. The results will report immediately, saving the need to update.

The aborted results are because validation is already complete on that WU. To decrease the number of these that you get, then you would have to decrease your cache. At 0.5 days I've only had one in the last 48 hrs.

Why you get the HTTP error, I do not know. But assuming you are on Broadband, always on. If you set the connection interval to 0, and use the 'Maintain enough work for an additional x days' as your cache setting. The results will report immediately, saving the need to update.

The aborted results are because validation is already complete on that WU. To decrease the number of these that you get, then you would have to decrease your cache. At 0.5 days I've only had one in the last 48 hrs.

I also saw that HTTP error a little while ago on two machines. I thought it was because I was upgrading them to BOINC 5.10.7, but it seems to have stopped now. ???

I was getting that occasionally untill I upgraded to 5.10.7.
I have not seen it since.
Currious eh?
____________
When we finally figure it all out, all the rules will change and we can start all over again.

At the end of the day yesterday a simple cut-and-paste misinterpreted by a terminal window introduced an extra line feed to the /etc/exports file on our Network Appliance filer (which hosts our home accounts, web sites, /usr/local, etc.) which rendered its root (/) mount read-only. Of course, you need read-write access to update the exports file. This was a bit of a conundrum, with the added pressure of "mount rot" quickly creeping through our network and slowing machines to a crawl (hence the minor outage which very few seemed to notice). This sent me, Jeff, and Eric into a fit of head scratching, with Eric finally discovering that, even though we couldn't re-export "/" on the simple filer command line, we could freshly export "/." with read-write access to a machine that hadn't quite hung up yet, and fix the offending file. After some reboots to clean the pipes we were back to normal.

I think I fixed the weird "top computers" sorting problems. I believe somebody else made an update trying to optimize it during our recent database panic without realizing it broke the sort logic. Fair enough.

Other than that, Jeff and I worked to get the new server "bane" on line. Yup, we continue to stick with the darth naming convention for now. We made it a third public web server for a second there to test the plumbing, but took it back offline for now. We need to tighten some screws before making it a real production web server.

I also saw that HTTP error a little while ago on two machines. I thought it was because I was upgrading them to BOINC 5.10.7, but it seems to have stopped now. ???

I was getting that occasionally untill I upgraded to 5.10.7.
I have not seen it since.
Curious eh?

Curious indeed. Exactly half of my machines are now getting it on every communication, but it ALWAYS works on the (immediate) retry. All but one are now on 5.10.7. All else is working so I guess now problem, for now.

I also saw that HTTP error a little while ago on two machines. I thought it was because I was upgrading them to BOINC 5.10.7, but it seems to have stopped now. ???

I was getting that occasionally untill I upgraded to 5.10.7.
I have not seen it since.
Curious eh?

Curious indeed. Exactly half of my machines are now getting it on every communication, but it ALWAYS works on the (immediate) retry. All but one are now on 5.10.7. All else is working so I guess now problem, for now.

I'm getting this same problem with both 5.8.15 and 5.4.11 - so I think the problem is server-side, not client-side. (I.E. Berkeley's the one with the problem)
____________
.

I also saw that HTTP error a little while ago on two machines. I thought it was because I was upgrading them to BOINC 5.10.7, but it seems to have stopped now. ???

I was getting that occasionally untill I upgraded to 5.10.7.
I have not seen it since.
Curious eh?

Curious indeed. Exactly half of my machines are now getting it on every communication, but it ALWAYS works on the (immediate) retry. All but one are now on 5.10.7. All else is working so I guess now problem, for now.

I'm getting this same problem with both 5.8.15 and 5.4.11 - so I think the problem is server-side, not client-side. (I.E. Berkeley's the one with the problem)

My thoughts as well.
BTW, I meant to say ". . . no problem, for now" in my previous post.

At the end of the day yesterday a simple cut-and-paste misinterpreted by a terminal window introduced an extra line feed to the /etc/exports file on our Network Appliance filer (which hosts our home accounts, web sites, /usr/local, etc.) which rendered its root (/) mount read-only. Of course, you need read-write access to update the exports file. This was a bit of a conundrum, with the added pressure of "mount rot" quickly creeping through our network and slowing machines to a crawl (hence the minor outage which very few seemed to notice). This sent me, Jeff, and Eric into a fit of head scratching, with Eric finally discovering that, even though we couldn't re-export "/" on the simple filer command line, we could freshly export "/." with read-write access to a machine that hadn't quite hung up yet, and fix the offending file. After some reboots to clean the pipes we were back to normal.

I think I fixed the weird "top computers" sorting problems. I believe somebody else made an update trying to optimize it during our recent database panic without realizing it broke the sort logic. Fair enough.

Other than that, Jeff and I worked to get the new server "bane" on line. Yup, we continue to stick with the darth naming convention for now. We made it a third public web server for a second there to test the plumbing, but took it back offline for now. We need to tighten some screws before making it a real production web server.