| Author |
Message |
|---|
 Matt LebofskyVolunteer moderator
Project administrator
Project developer
Project scientist
Send message
Joined: 1 Mar 99
Posts: 1375
Credit: 74,079
RAC: 0
|
|
Yesterday afternoon we had to reboot kryten/penguin to flush their pipes. Sigh. Bruno is well on its way towards becoming a full fledged upload server, but the sooner we get bruno to be the download server the better. The major gating item on that is the need for a new 24 port gigabit switch for our closet. Long story.
Meanwhile many clients are still connecting to kryten for uploads. This is thanks to the wacky unpredictable internet while trickles out DNS changes at surprisingly slow rates. While diagnosing this I wrote a script to show me a sample of the most recent client version types to connect to our servers. I then made it into a web page (there's a link on the server status page as well). Yup - we're dominated by Windows, but they're not to blame for any DNS-related issues. Anyway kryten will probably completely free of upload traffic within a week or so.
I just heard cheers from Jeff's desk - he compiled an assimilator on bruno. He's now working on the validator - linking issues.
Bob worked some magic and got sidious back on track today without having to do a full restore. So it's acting as a replica again. We're still not exactly sure why, but we found the MYD files zeroed out within the past week (and was only exercised upon stopping/restarting the database on Tuesday). Some research shows this may be a bug when replicating a mysql version 4.1 database to version 5.0, which is exactly what we're doing. We're planning on upgrading the 4.1 soon, so maybe this problem will disappear.
Oh yeah - there was a network blip this morning around 6am. Not us. It was campus working routers further up the pike. And we had a minor blip around noon. That was me screwing around trying to get the beta project working again. I think Eric is ironing out the last remaining details on that as I type.
There is some concern that results got munged during all this switching around. Probably so, and we're sorry if this happened to you. We'll try to clean it up and get people their credit as best we can.
- 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 |
|
|
|
|
Yesterday afternoon we had to reboot kryten/penguin to flush their pipes. Sigh. Bruno is well on its way towards becoming a full fledged upload server, but the sooner we get bruno to be the download server the better. The major gating item on that is the need for a new 24 port gigabit switch for our closet. Long story.
Meanwhile many clients are still connecting to kryten for uploads. This is thanks to the wacky unpredictable internet while trickles out DNS changes at surprisingly slow rates. While diagnosing this I wrote a script to show me a sample of the most recent client version types to connect to our servers. I then made it into a web page (there's a link on the server status page as well). Yup - we're dominated by Windows, but they're not to blame for any DNS-related issues. Anyway kryten will probably completely free of upload traffic within a week or so.
I just heard cheers from Jeff's desk - he compiled an assimilator on bruno. He's now working on the validator - linking issues.
Bob worked some magic and got sidious back on track today without having to do a full restore. So it's acting as a replica again. We're still not exactly sure why, but we found the MYD files zeroed out within the past week (and was only exercised upon stopping/restarting the database on Tuesday). Some research shows this may be a bug when replicating a mysql version 4.1 database to version 5.0, which is exactly what we're doing. We're planning on upgrading the 4.1 soon, so maybe this problem will disappear.
Oh yeah - there was a network blip this morning around 6am. Not us. It was campus working routers further up the pike. And we had a minor blip around noon. That was me screwing around trying to get the beta project working again. I think Eric is ironing out the last remaining details on that as I type.
There is some concern that results got munged during all this switching around. Probably so, and we're sorry if this happened to you. We'll try to clean it up and get people their credit as best we can.
- Matt
Great Work all around by Each of You @ Berkeley - and CONGRATULATIONS TOO . . .
'all's Well that end's well . . ." THanks for the Post Matt . . .
|
|
|
ML1Volunteer tester
Send message
Joined: 25 Nov 01
Posts: 7141
Credit: 3,686,839
RAC: 963
|
...The major gating item on that is the need for a new 24 port gigabit switch for our closet. Long story.
A story for another lunchbreak perchance?
(More seriously, the stories, insight and info are interesting, thanks. So is getting the science rolling along!)
... While diagnosing this I wrote a script to show me a sample of the most recent client version types to connect to our servers. I then made it into a web page (there's a link on the server status page as well). Yup - we're dominated by Windows,...
Don't forget that the unsupported types such as x86_64-pc-linux-gnu/x86_64-unknown-linux-gnu ( ;-) ) will be underrepresented being as they will not be pestering as much due to 1 day(?) deferrals.
Happy crunchin',
Regards,
Martin
____________
Mandriva Linux A user friendly OS!
See new freedom Mageia2
The Future is what We make IT (GPLv3) |
|
|
|
|
(More seriously, the stories, insight and info are interesting, thanks. So is getting the science rolling along!)
Agreed, Matt many of us don't post that often, but keep up on what is happening and find your missives on the ups and downs, frustrations and successes very interesting. It gives us great incite into how difficult it is to keep something like this going. Much appreciated. |
|
|
|
|
|
Fascinating list of the recent BOINC versions reporting in. I've done you a little graph (click to view):
(direct link)
Edit - it works better with a log scale:
(direct link) |
|
|
|
|
Yup - we're dominated by Windows, but they're not to blame for any DNS-related issues.
That would be a Misfit related issue. .o0(I also use Windows.)
____________
  |
|
|
|
|
Yup - we're dominated by Windows, but they're not to blame for any DNS-related issues.
That would be a Misfit related issue. .o0(I also use Windows.)
You use what You like Misfit, Nothing wrong with that. Ditto on the OS. :D
____________
BSG Anthem
My Facebook page
 |
|
|
|
|
Meanwhile many clients are still connecting to kryten for uploads. This is thanks to the wacky unpredictable internet while trickles out DNS changes at surprisingly slow rates. While diagnosing this I wrote a script to show me a sample of the most recent client version types to connect to our servers. I then made it into a web page (there's a link on the server status page as well). Yup - we're dominated by Windows, but they're not to blame for any DNS-related issues. Anyway kryten will probably completely free of upload traffic within a week or so.
A likely candidate to blame is the BOINC-client itself, BOINC alpha had many reports in January there DNS apparently is cached by libCurl used in the client, and only way to clean-out "bad" names is to re-start BOINC-client...
____________
"I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
|
|
|
|
|
Fascinating stats.
2644 (%26.93) windows_intelx86 5.4.11
1318 (%13.42) windows_intelx86 5.02
1258 (%12.81) windows_intelx86 5.8.15
666 (%6.78) windows_intelx86 5.4.9
573 (%5.84) windows_intelx86 5.8.11
552 (%5.62) windows_intelx86 4.45
424 (%4.32) windows_intelx86 5.8.8
281 (%2.86) i686-apple-darwin 5.4.9
202 (%2.06) windows_intelx86 5.5.0
153 (%1.56) i686-pc-linux-gnu 5.4.9
144 (%1.47) windows_intelx86 4.25
141 (%1.44) windows_intelx86 4.49
Any views as to why less than 13% of people are using the latest RECCOMMENDED Boinc client???
____________
Damsel Rescuer, Kitty Patron, Raccoon Friend, Uli Fan,
Julie Supporter, ES99 Admirer, PETA Member, 1st Childhood
   |
|
|
Volunteer tester
Send message
Joined: 9 Apr 02
Posts: 11987
Credit: 18,169,882
RAC: 56,126
|
Fascinating stats.
2644 (%26.93) windows_intelx86 5.4.11
1318 (%13.42) windows_intelx86 5.02
1258 (%12.81) windows_intelx86 5.8.15
666 (%6.78) windows_intelx86 5.4.9
573 (%5.84) windows_intelx86 5.8.11
552 (%5.62) windows_intelx86 4.45
424 (%4.32) windows_intelx86 5.8.8
281 (%2.86) i686-apple-darwin 5.4.9
202 (%2.06) windows_intelx86 5.5.0
153 (%1.56) i686-pc-linux-gnu 5.4.9
144 (%1.47) windows_intelx86 4.25
141 (%1.44) windows_intelx86 4.49
Any views as to why less than 13% of people are using the latest RECCOMMENDED Boinc client???
People install it and forget it.
____________
|
|
|
|
|
Fascinating stats.
2644 (%26.93) windows_intelx86 5.4.11
1318 (%13.42) windows_intelx86 5.02
1258 (%12.81) windows_intelx86 5.8.15
666 (%6.78) windows_intelx86 5.4.9
573 (%5.84) windows_intelx86 5.8.11
552 (%5.62) windows_intelx86 4.45
424 (%4.32) windows_intelx86 5.8.8
281 (%2.86) i686-apple-darwin 5.4.9
202 (%2.06) windows_intelx86 5.5.0
153 (%1.56) i686-pc-linux-gnu 5.4.9
144 (%1.47) windows_intelx86 4.25
141 (%1.44) windows_intelx86 4.49
Any views as to why less than 13% of people are using the latest RECCOMMENDED Boinc client???
People install it and forget it.
People Install and forget as they have busy lives, Some might even say lazy too.
____________
BSG Anthem
My Facebook page
|
|
|
|
|
Fascinating stats.
2644 (%26.93) windows_intelx86 5.4.11
1318 (%13.42) windows_intelx86 5.02
1258 (%12.81) windows_intelx86 5.8.15
666 (%6.78) windows_intelx86 5.4.9
573 (%5.84) windows_intelx86 5.8.11
552 (%5.62) windows_intelx86 4.45
424 (%4.32) windows_intelx86 5.8.8
281 (%2.86) i686-apple-darwin 5.4.9
202 (%2.06) windows_intelx86 5.5.0
153 (%1.56) i686-pc-linux-gnu 5.4.9
144 (%1.47) windows_intelx86 4.25
141 (%1.44) windows_intelx86 4.49
Any views as to why less than 13% of people are using the latest RECCOMMENDED Boinc client???
People install it and forget it.
Some people (I'm one...) subscribe to the "if it ain't broke, don't fix it" mentality, not realizing that 5.4.11 has at least one problem that 5.8.15 fixes... the 'no result file' (paraphrase) after doing a work unit. (yes, I upgraded) Also realize that upgrading the Boinc client involves downloading an 8 Mb file - some of us still use dial-up, and that takes about a ½ hour!
____________
.
  |
|
|
|
|
Fascinating stats.
2644 (%26.93) windows_intelx86 5.4.11
1318 (%13.42) windows_intelx86 5.02
1258 (%12.81) windows_intelx86 5.8.15
666 (%6.78) windows_intelx86 5.4.9
573 (%5.84) windows_intelx86 5.8.11
552 (%5.62) windows_intelx86 4.45
424 (%4.32) windows_intelx86 5.8.8
281 (%2.86) i686-apple-darwin 5.4.9
202 (%2.06) windows_intelx86 5.5.0
153 (%1.56) i686-pc-linux-gnu 5.4.9
144 (%1.47) windows_intelx86 4.25
141 (%1.44) windows_intelx86 4.49
Any views as to why less than 13% of people are using the latest RECCOMMENDED Boinc client???
People install it and forget it.
Some people (I'm one...) subscribe to the "if it ain't broke, don't fix it" mentality, not realizing that 5.4.11 has at least one problem that 5.8.15 fixes... the 'no result file' (paraphrase) after doing a work unit. (yes, I upgraded) Also realize that upgrading the Boinc client involves downloading an 8 Mb file - some of us still use dial-up, and that takes about a ½ hour!
Could also be most people don't know there is something better. This is the only thread I read so one day I looked at the release levels and discovered there was something newer I should be running. I suggest an E-mail to all users about the newer software level.
____________
|
|
|
|
|
I suggest an E-mail to all users about the newer software level.
No, I don´t think many want that! Just thinking of my fooded mailboxes...
Maybe some kind of message at startup..?
mic.
____________
mic.
 |
|
|
|
|
The major gating item on that is the need for a new 24 port gigabit switch for our closet. Long story.
Is this equipment available or are you in need of a donation?
____________
.. |
|
|
|
|
People install it and forget it.
Some people (I'm one...) subscribe to the "if it ain't broke, don't fix it" mentality, not realizing that 5.4.11 has at least one problem that 5.8.15 fixes... the 'no result file' (paraphrase) after doing a work unit. (yes, I upgraded) Also realize that upgrading the Boinc client involves downloading an 8 Mb file - some of us still use dial-up, and that takes about a ½ hour!
Could also be most people don't know there is something better. This is the only thread I read so one day I looked at the release levels and discovered there was something newer I should be running. I suggest an E-mail to all users about the newer software level.
Could also be that most people care enough to load BOINC, and probably don't even look at it -- they know work is being done, and that's it.
Some install BOINC and then move on to other jobs and can't update that machine.
... and since many people change E-Mail addresses frequently, SETI definitely can't reach a surprising number of participants.
____________
|
|
|
|
|
People install it and forget it.
Some people (I'm one...) subscribe to the "if it ain't broke, don't fix it" mentality, not realizing that 5.4.11 has at least one problem that 5.8.15 fixes... the 'no result file' (paraphrase) after doing a work unit. (yes, I upgraded) Also realize that upgrading the Boinc client involves downloading an 8 Mb file - some of us still use dial-up, and that takes about a ½ hour!
Could also be most people don't know there is something better. This is the only thread I read so one day I looked at the release levels and discovered there was something newer I should be running. I suggest an E-mail to all users about the newer software level.
Could also be that most people care enough to load BOINC, and probably don't even look at it -- they know work is being done, and that's it.
Some install BOINC and then move on to other jobs and can't update that machine.
... and since many people change E-Mail addresses frequently, SETI definitely can't reach a surprising number of participants.
Then how about a feature added to future releases that pops up a window that states NEWER RELEASE AVAILBLE - CLICK HERE TO DOWNLOAD.
____________
|
|
|
|
|
People install it and forget it.
Some people (I'm one...) subscribe to the "if it ain't broke, don't fix it" mentality, not realizing that 5.4.11 has at least one problem that 5.8.15 fixes... the 'no result file' (paraphrase) after doing a work unit. (yes, I upgraded) Also realize that upgrading the Boinc client involves downloading an 8 Mb file - some of us still use dial-up, and that takes about a ½ hour!
Could also be most people don't know there is something better. This is the only thread I read so one day I looked at the release levels and discovered there was something newer I should be running. I suggest an E-mail to all users about the newer software level.
Could also be that most people care enough to load BOINC, and probably don't even look at it -- they know work is being done, and that's it.
Some install BOINC and then move on to other jobs and can't update that machine.
... and since many people change E-Mail addresses frequently, SETI definitely can't reach a surprising number of participants.
Then how about a feature added to future releases that pops up a window that states NEWER RELEASE AVAILBLE - CLICK HERE TO DOWNLOAD.
Those who run Boinc on computers with whom they have questionable legal access to will object to any pop up window.
____________
Boinc....Boinc....Boinc....Boinc.... |
|
|
|
|
People install it and forget it.
Some people (I'm one...) subscribe to the "if it ain't broke, don't fix it" mentality, not realizing that 5.4.11 has at least one problem that 5.8.15 fixes... the 'no result file' (paraphrase) after doing a work unit. (yes, I upgraded) Also realize that upgrading the Boinc client involves downloading an 8 Mb file - some of us still use dial-up, and that takes about a ½ hour!
Could also be most people don't know there is something better. This is the only thread I read so one day I looked at the release levels and discovered there was something newer I should be running. I suggest an E-mail to all users about the newer software level.
Could also be that most people care enough to load BOINC, and probably don't even look at it -- they know work is being done, and that's it.
Some install BOINC and then move on to other jobs and can't update that machine.
... and since many people change E-Mail addresses frequently, SETI definitely can't reach a surprising number of participants.
Then how about a feature added to future releases that pops up a window that states NEWER RELEASE AVAILBLE - CLICK HERE TO DOWNLOAD.
Those who run Boinc on computers with whom they have questionable legal access to will object to any pop up window.
I wouldn't doubt that, As the PC user would then do something about Boinc on their PC, It'd be just deserts for the user who has added PCs without the permission of the PCs owner(s) in question. Sending a message to terminate the older classic versions through seti would have been nice but It's something that probably wasn't thought of, emails don't always work as explained already. I'd almost wonder is there anything that can be done? I know when classic was about to shut down a message was sent out and I saw it in the seti software, I don't know how It was done, But maybe this could be done as the seti classic software is expecting something, It's that or maybe shut down the ip address if that is possible at all. Otherwise I'm stumped.
____________
BSG Anthem
My Facebook page
|
|
|
|
|
People install it and forget it.
Some people (I'm one...) subscribe to the "if it ain't broke, don't fix it" mentality, not realizing that 5.4.11 has at least one problem that 5.8.15 fixes... the 'no result file' (paraphrase) after doing a work unit. (yes, I upgraded) Also realize that upgrading the Boinc client involves downloading an 8 Mb file - some of us still use dial-up, and that takes about a ½ hour!
Could also be most people don't know there is something better. This is the only thread I read so one day I looked at the release levels and discovered there was something newer I should be running. I suggest an E-mail to all users about the newer software level.
Could also be that most people care enough to load BOINC, and probably don't even look at it -- they know work is being done, and that's it.
Some install BOINC and then move on to other jobs and can't update that machine.
... and since many people change E-Mail addresses frequently, SETI definitely can't reach a surprising number of participants.
Then how about a feature added to future releases that pops up a window that states NEWER RELEASE AVAILBLE - CLICK HERE TO DOWNLOAD.
Those who run Boinc on computers with whom they have questionable legal access to will object to any pop up window.
I wouldn't doubt that, As the PC user would then do something about Boinc on their PC, It'd be just deserts for the user who has added PCs without the permission of the PCs owner(s) in question. Sending a message to terminate the older classic versions through seti would have been nice but It's something that probably wasn't thought of, emails don't always work as explained already. I'd almost wonder is there anything that can be done? I know when classic was about to shut down a message was sent out and I saw it in the seti software, I don't know how It was done, But maybe this could be done as the seti classic software is expecting something, It's that or maybe shut down the ip address if that is possible at all. Otherwise I'm stumped.
May be a dumb idea, but the SETI task is downloaded as needed. Could the code be put in there. I admit the other projects would also have to include the code in their task(s) but it would clean up problems for anyone who includes the code.
____________
|
|
|
