Over the past few days we've been trying to get our download server (penguin) onto a new network. All kinds of confusing issues as this involves two new routers under our control (one here at the lab, one down at the PAIX), and several third parties along the way. The map of the route, currently on the dry erase board by my desk, is a bit, well, complicated. The question "why are we doing this" will be answered once we are successful. Currently, while one of our web servers is on this network, we can't do much else. The download server is hitting a bottleneck somewhere along the way that has yet to be discovered.

Meanwhile, kryten is still being a whiny baby. Last night I cranked up the number of apache listener processes to help quicken the pace of outage recovery, but I never had to resort to this before. Another mystery.

As I write this, things are a bit off, and we know this, but we are trying to collect some more diagnostic data about the new network before "falling back" for the rest of the weekend. More surgery come monday.

- 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

Good luck Matt!

---

yes good

and need to have a few beers.

---

What nfs product are you using?

---

Is this why despite all up and running I cannot upload anything for the past couple of days (happening on both computers). I miss you tech page which usually would inform us noncomputer people about why we are having problems. Thanks for any info/help you can give me. Been doing this for almost 8 years now.

robin

---

I'm guessing this to be the case here and as I have multiple projects running, shutting off all network activity is overkill. I simply suspended SETI on my workstations for now.

Is this why despite all up and running I cannot upload anything for the past couple of days (happening on both computers). I miss you tech page which usually would inform us noncomputer people about why we are having problems. Thanks for any info/help you can give me. Been doing this for almost 8 years now.

robin

---

I haven't been able to up or download since Tuesday on 2 of my computers, while a third seems to have no trouble. Any ideas?

---

I haven't been able to up or download since Tuesday on 2 of my computers, while a third seems to have no trouble. Any ideas?

I too am having this same problem.....4 PCs running BOINC with no problems
and number 5 who refuses to upload or download. No changes of any kind
made to said PC in months....and it has internet connectivity....
transfers files from anywhere else just fine....just not with BOINC......

---

I haven't been able to up or download since Tuesday on 2 of my computers, while a third seems to have no trouble. Any ideas?

I too am having this same problem.....4 PCs running BOINC with no problems
and number 5 who refuses to upload or download. No changes of any kind
made to said PC in months....and it has internet connectivity....
transfers files from anywhere else just fine....just not with BOINC......

Hi guys,

Try restarting the BOINC service. Berkeley is making changes to its network, causing some IP addresses to change. A restart should do the trick, but if it doesn't, flush your DNS cache and restart the BOINC service. To do so, if you're using a windows box, open a command prompt and type ipconfig /flushdns.

Regards,
Wander

---

I haven't been able to up or download since Tuesday on 2 of my computers, while a third seems to have no trouble. Any ideas?

I too am having this same problem.....4 PCs running BOINC with no problems
and number 5 who refuses to upload or download. No changes of any kind
made to said PC in months....and it has internet connectivity....
transfers files from anywhere else just fine....just not with BOINC......

Hi guys,

Try restarting the BOINC service. Berkeley is making changes to its network, causing some IP addresses to change. A restart should do the trick, but if it doesn't, flush your DNS cache and restart the BOINC service. To do so, if you're using a windows box, open a command prompt and type ipconfig /flushdns.

Regards,
Wander

Well I did these before but heck I'll try them again - cant hurt :]........
Tried these things but still no joy.......cant get anything to download from
BOINC.....and unless they made changes today - it worked last night....
Curious

---

I haven't been able to up or download since Tuesday on 2 of my computers, while a third seems to have no trouble. Any ideas?

I too am having this same problem.....4 PCs running BOINC with no problems
and number 5 who refuses to upload or download. No changes of any kind
made to said PC in months....and it has internet connectivity....
transfers files from anywhere else just fine....just not with BOINC......

Hi guys,

Try restarting the BOINC service. Berkeley is making changes to its network, causing some IP addresses to change. A restart should do the trick, but if it doesn't, flush your DNS cache and restart the BOINC service. To do so, if you're using a windows box, open a command prompt and type ipconfig /flushdns.

Regards,
Wander

Well I did these before but heck I'll try them again - cant hurt :]........
Tried these things but still no joy.......cant get anything to download from
BOINC.....and unless they made changes today - it worked last night....
Curious

i was able to down load about 8 new units last night

---

Restarting BOINC did enable the one computer to down and upload, but I have had to restart it a few times in the last few days to get it to work. A little odd, since it is only the one, but workable.

I haven't been able to up or download since Tuesday on 2 of my computers, while a third seems to have no trouble. Any ideas?

I too am having this same problem.....4 PCs running BOINC with no problems
and number 5 who refuses to upload or download. No changes of any kind
made to said PC in months....and it has internet connectivity....
transfers files from anywhere else just fine....just not with BOINC......

Hi guys,

Try restarting the BOINC service. Berkeley is making changes to its network, causing some IP addresses to change. A restart should do the trick, but if it doesn't, flush your DNS cache and restart the BOINC service. To do so, if you're using a windows box, open a command prompt and type ipconfig /flushdns.

Regards,
Wander

Well I did these before but heck I'll try them again - cant hurt :]........
Tried these things but still no joy.......cant get anything to download from
BOINC.....and unless they made changes today - it worked last night....
Curious

i was able to down load about 8 new units last night

---

Flushing the DNS and restarting boinc did not cure my inability to upload completed work.

Although I am really enjoying seeing all the tech posts by the SETI team in the new section of the message boards.

Flushing the DNS and restarting boinc did not cure my inability to upload completed work.
...

I tried it twice on my MBP with no success either. Then I rebooted, and everything worked fine.

C

---

Join Team MacNN

Flushing the DNS and restarting boinc did not cure my inability to upload completed work.
...

I tried it twice on my MBP with no success either. Then I rebooted, and everything worked fine.

C

Sometimes a DNS cache is held by routers/high speed modems, etc. Rebooting usually tells the router to check DNS again as the OS reinitializes itself with the router upon coming up.

With as many brands of hardware, firmwares, etc. that are out there, not everyone uses the same logic.

---

My movie https://vimeo.com/manage/videos/502242