Boinc 4.40 cannot connect to anything

Forums › Problems and Bug Reports

ilyanep
ilyanep
Joined: 29 Apr 05
Posts: 39
Credit: 163891464
RAC: 31893
13 May 2005 3:59:00 UTC
Topic 189171
(moderation:
    )

    5/12/2005 10:56:15 PM|ProteinPredictorAtHome|Requesting 58210.10 seconds of work
    5/12/2005 10:56:15 PM|ProteinPredictorAtHome|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
    5/12/2005 10:56:15 PM|ProteinPredictorAtHome|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
    5/12/2005 10:56:16 PM|ProteinPredictorAtHome|Scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi failed
    5/12/2005 10:56:16 PM|ProteinPredictorAtHome|No schedulers responded
    5/12/2005 10:56:16 PM|ProteinPredictorAtHome|Deferring communication with project for 1 minutes and 0 seconds
    5/12/2005 10:56:26 PM||request_reschedule_cpus: project op
    5/12/2005 10:56:26 PM||schedule_cpus: must schedule
    5/12/2005 10:56:27 PM|SETI@home|Requesting 8997.32 seconds of work
    5/12/2005 10:56:27 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
    5/12/2005 10:56:27 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
    5/12/2005 10:56:31 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
    5/12/2005 10:56:31 PM|SETI@home|No schedulers responded
    5/12/2005 10:56:31 PM|SETI@home|Deferring communication with project for 1 minutes and 0 seconds
    5/12/2005 10:57:01 PM||request_reschedule_cpus: project op
    5/12/2005 10:57:01 PM||schedule_cpus: must schedule
    5/12/2005 10:57:01 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
    5/12/2005 10:57:02 PM|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed
    5/12/2005 10:57:02 PM|climateprediction.net|No schedulers responded
    5/12/2005 10:57:02 PM|climateprediction.net|Deferring communication with project for 1 minutes and 0 seconds
    5/12/2005 10:57:04 PM||request_reschedule_cpus: project op
    5/12/2005 10:57:04 PM||schedule_cpus: must schedule
    5/12/2005 10:57:04 PM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
    5/12/2005 10:57:06 PM|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
    5/12/2005 10:57:17 PM|ProteinPredictorAtHome|Requesting 58210.41 seconds of work
    5/12/2005 10:57:17 PM|ProteinPredictorAtHome|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
    5/12/2005 10:57:17 PM|ProteinPredictorAtHome|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
    5/12/2005 10:57:18 PM|ProteinPredictorAtHome|Scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi failed
    5/12/2005 10:57:18 PM|ProteinPredictorAtHome|No schedulers responded
    5/12/2005 10:57:18 PM|ProteinPredictorAtHome|Deferring communication with project for 1 minutes and 0 seconds
    5/12/2005 10:57:33 PM|SETI@home|Master file fetch failed
    5/12/2005 10:57:33 PM|SETI@home|Deferring communication with project for 1 minutes and 0 seconds
    5/12/2005 10:58:03 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
    5/12/2005 10:58:04 PM|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
    5/12/2005 10:58:18 PM|ProteinPredictorAtHome|Requesting 58210.76 seconds of work
    5/12/2005 10:58:18 PM|ProteinPredictorAtHome|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
    5/12/2005 10:58:18 PM|ProteinPredictorAtHome|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
    5/12/2005 10:58:20 PM|ProteinPredictorAtHome|Scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi failed
    5/12/2005 10:58:20 PM|ProteinPredictorAtHome|No schedulers responded
    5/12/2005 10:58:20 PM|ProteinPredictorAtHome|Deferring communication with project for 2 minutes and 9 seconds
    5/12/2005 10:58:20 PM||request_reschedule_cpus: project op
    5/12/2005 10:58:20 PM||schedule_cpus: must schedule
    5/12/2005 10:58:21 PM|SETI@home|Requesting 8998.45 seconds of work
    5/12/2005 10:58:21 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
    5/12/2005 10:58:21 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
    5/12/2005 10:58:22 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
    5/12/2005 10:58:22 PM|SETI@home|No schedulers responded
    5/12/2005 10:58:22 PM|SETI@home|Deferring communication with project for 1 minutes and 0 seconds

    it doesn't appear that most of these can connect. Is it due to the fact that the servers for these projects haven't been updated for the new version yet?

    Nalle
    Nalle
    Joined: 22 Jan 05
    Posts: 1
    Credit: 4747
    RAC: 0

    Boinc 4.40 cannot connect to anything

    13 May 2005 8:26:03 UTC
    Message 11613
    (moderation:
      )


      it doesn't appear that most of these can connect. Is it due to the fact that the servers for these projects haven't been updated for the new version yet?

      I'm experiencing this same thing with einstein and seti. proteinpredictor and lhc seem to get some work.

      Bruce Allen
      Bruce Allen
      Moderator
      Joined: 15 Oct 04
      Posts: 1119
      Credit: 172127663
      RAC: 0

      it doesn't appear that most

      13 May 2005 16:23:43 UTC
      Message 11614 in response to message 11613
      (moderation:
        )


        it doesn't appear that most of these can connect. Is it due to the fact that the servers for these projects haven't been updated for the new version yet?

        I'm experiencing this same thing with einstein and seti. proteinpredictor and lhc seem to get some work.

        The Einstein@Home server code is current (CVS HEAD) as of Friday May 13th. David Anderson tends to keep the SETI@Home server code at CVS HEAD as well. I think predictor and LHC are not as up-to-date.

        Bruce

        Director, Einstein@Home

        shivanraptor
        shivanraptor
        Joined: 7 Mar 05
        Posts: 1
        Credit: 4889580
        RAC: 0

        can't get connected with

        13 May 2005 17:45:16 UTC
        Message 11615
        (moderation:
          )

          can't get connected with version 4.38 , 4.39 and 4.40 . please help .
          4.25 is fine .

          ABT Chuck P
          ABT Chuck P
          Joined: 9 Feb 05
          Posts: 20
          Credit: 363204
          RAC: 0

          it doesn't appear that most

          14 May 2005 21:32:44 UTC
          Message 11616
          (moderation:
            )


            it doesn't appear that most of these can connect. Is it due to the fact that the servers for these projects haven't been updated for the new version yet?
            ======================
            The 4.40 cc has reintroduced an old bug for some people, where if you force an update or an auto update boinc.exe runs up to 99% or 50% on HT machines. You have to close Boinc out and restart to make the connection.


            ralic
            ralic
            Joined: 8 Nov 04
            Posts: 128
            Credit: 695810
            RAC: 0

            5/12/2005 10:56:15

            15 May 2005 16:50:19 UTC
            Message 11617
            (moderation:
              )

              5/12/2005 10:56:15 PM|ProteinPredictorAtHome|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
              5/12/2005 10:56:15 PM|ProteinPredictorAtHome|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
              5/12/2005 10:56:27 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
              5/12/2005 10:56:27 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi

              The key lies in the "double" requests being sent, as I've indicated above. A fix has been checked in and v4.41 has been released.

              I don't see any connection attempts to einstein, but if you look at the other projects, you'll most likely find that you have been assigned wu's that are not on your system. This is not a server fault. It was as a result of a bug in the v4.40 client.

              Unless there are features in the later clients that you absolutely must have, it's better to stay with the 4.25 recommended version. The later clients are not stable.

              ilyanep
              ilyanep
              Joined: 29 Apr 05
              Posts: 39
              Credit: 163891464
              RAC: 31893

              5/12/2005 10:56:15

              15 May 2005 16:53:03 UTC
              Message 11618 in response to message 11617
              (moderation:
                )

                5/12/2005 10:56:15 PM|ProteinPredictorAtHome|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
                5/12/2005 10:56:15 PM|ProteinPredictorAtHome|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
                5/12/2005 10:56:27 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
                5/12/2005 10:56:27 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi

                The key lies in the "double" requests being sent, as I've indicated above. A fix has been checked in and v4.41 has been released.

                I don't see any connection attempts to einstein, but if you look at the other projects, you'll most likely find that you have been assigned wu's that are not on your system. This is not a server fault. It was as a result of a bug in the v4.40 client.

                Unless there are features in the later clients that you absolutely must have, it's better to stay with the 4.25 recommended version. The later clients are not stable.

                I'm staying w/ 4.35 for the time being

                ralic
                ralic
                Joined: 8 Nov 04
                Posts: 128
                Credit: 695810
                RAC: 0

                I'm staying w/ 4.35 for the

                15 May 2005 17:00:38 UTC
                Message 11619 in response to message 11618
                (moderation:
                  )

                  I'm staying w/ 4.35 for the time being
                  As long as it works for you. :)
                  Although, having said that, there must have been problems with it or we wouldn't be on the road to v4.50...

                  ilyanep
                  ilyanep
                  Joined: 29 Apr 05
                  Posts: 39
                  Credit: 163891464
                  RAC: 31893

                  I'm staying w/ 4.35 for the

                  15 May 2005 17:54:20 UTC
                  Message 11620 in response to message 11619
                  (moderation:
                    )

                    I'm staying w/ 4.35 for the time being
                    As long as it works for you. :)
                    Although, having said that, there must have been problems with it or we wouldn't be on the road to v4.50...

                    Last time worked fine for me except for not getting new E@H wu's but I'm starting to think it was the server not my client.

                    Comment viewing options

                    Select your preferred way to display the comments and click "Save settings" to activate your changes.

                    Forums › Problems and Bug Reports