On Problem 1. i just started to download Ethereal (will last about an hour on dial-up). Maybe this tool will be able to give some hints what is happening at ''No schedulers responded'' messages.

Ethereal only works with network cards, if you connect with a modem, Ethereal won't find any devices to hook into.

EDIT:
If your modem is actually on a different computer, and you connect to that thru a network adapter on your PC, then Ethereal should work OK.

There is a program that traces PPP activity, but I forget where I saw it.

On Problem 1. i just started to download Ethereal (will last about an hour on dial-up). Maybe this tool will be able to give some hints what is happening at ''No schedulers responded'' messages.

Ethereal only works with network cards, if you connect with a modem, Ethereal won't find any devices to hook into.

EDIT:
If your modem is actually on a different computer, and you connect to that thru a network adapter on your PC, then Ethereal should work OK.

There is a program that traces PPP activity, but I forget where I saw it.

You can get an evaluation copy of sniff-em here

EDIT:

The trial version only captures data received, but thats just whats needed.

The network problem he is having seems to be on one computer. So, there seems to me if I understand all Iknow about this is that we have several computers using the same linkages, but one of them does not connect right and now has run out of work ...

I know there are weird things with networking , like one of my comptuers cannot seem to be addressed by its name, only by IP address ... yet the name is in the DHCP server page (linksys router) ... so ... I am at a loss still ...

---

Hi,

the download of Ethereal finished in time. I'm now ready to test how this tool works on the other host (hostid 997552). Before here is what my network looks like:

external dial-up modem with Ethernet-Connection to a Router. That Router has a fast ethernet switch build in that is extended by an other fast ethernet switch. At max. there are 9 machines and a printserver connected via that network.
DHCP, DNS are internal set to automatic, DNS externally, too.

This configuration seems to work fine, so far.

---

_\|/_
U r s

Ethereal worked fine. Here is the server answer during a 500-error(it is shortened for the public). The first shows the stdout during that session. Like you can see, the next request after that session was successful and all my hosts are back crunching (yipie).

2005-06-27 22:13:34 [---] Resuming network activity
2005-06-27 22:13:34 [SETI@home] Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-06-27 22:13:34 [SETI@home] Requesting 0 seconds of work, returning 32 results
2005-06-27 22:13:40 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-06-27 22:13:40 [SETI@home] No schedulers responded
2005-06-27 22:13:41 [SETI@home] Deferring communication with project for 12 minutes and 12 seconds
2005-06-27 22:13:41 [---] Insufficient work; requesting more
2005-06-27 22:25:54 [SETI@home] Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-06-27 22:25:54 [SETI@home] Requesting 0 seconds of work, returning 32 results
2005-06-27 22:26:02 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded


Arrival Time: Jun 27, 2005 22:13:40.025381000
...
-!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"-
-HTML--HEAD-
-TITLE-500 Internal Server Error-/TITLE-
-/HEAD--BODY-
-H1-Internal Server Error-/H1-
The server encountered an internal error or
misconfiguration and was unable to complete
your request.-P-
Please contact the server administrator,
boincadm@ssl.berkeley.edu and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.-P-
More information about this error may be available
in the server error log.-P-
-HR-
-ADDRESS-Apache/1.3.31 Server at setiboincdata.ssl.berkeley.edu Port 80-/ADDRESS-
-/BODY--/HTML-


Paul D. Buck you got mail.

---

_\|/_
U r s

Now all I have to do is to run down to UCB and break into the server room to look at the logs ... :)

Rom, should be able to look ... and with luck if he can make sense out of it we can hope he will drop us a note ... history shows he is pretty good about that ...

---

Well, the good thing is that it's working for you again.

Your 500 response is not much different to the one I posted here.

Although I did expect this line to be different:

-ADDRESS-Apache/1.3.31 Server at setiboincdata.ssl.berkeley.edu Port 80-/ADDRESS-

The server reported is the data server, on which the scheduler is supposed to be turned off. So I did a bit of checking, but drew a blank because scheduler requests to that server return a 404, not a 500. Likely a typo/leftover in the 500 html file, or httpd.conf.

Looks like the only way to determine what is going on with these 500 errors is for someone to trawl the apache error logs.

Email to Rom is on its way. Maybe he answers one of the next days.

---

_\|/_
U r s

Hi,

Rom answered today and requested some more of my data (dumps and xml's). Now it is his turn.

---

_\|/_
U r s

Cool, maybe we are making progress ... :)

---