work , but not for my host

Author	Message
littleBouncer Send message Joined: 23 Oct 04 Posts: 358 Credit: 1,439,205 RAC: 0	Message 20514 - Posted: 24 Sep 2008, 22:26:22 UTC Last modified: 24 Sep 2008, 22:49:12 UTC There is work, but none for me Why? seee the messages (I let work the Bmgr5.10.45 at itself....) 24.09.2008 23:59:09\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 24.09.2008 23:59:14\|lhcathome\|Scheduler request succeeded: got 0 new tasks 25.09.2008 00:01:14\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 00:01:19\|lhcathome\|Scheduler request succeeded: got 0 new tasks 25.09.2008 00:16:29\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 00:16:34\|lhcathome\|Scheduler request succeeded: got 0 new tasks 25.09.2008 00:47:00\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 00:47:05\|lhcathome\|Scheduler request succeeded: got 0 new tasks greetz littleBouncer ID: 20514 · Reply Quote

littleBouncer Send message Joined: 23 Oct 04 Posts: 358 Credit: 1,439,205 RAC: 0	Message 20516 - Posted: 25 Sep 2008, 1:29:30 UTC Last modified: 25 Sep 2008, 1:33:54 UTC and this !!! 25.09.2008 02:12:03\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 1 completed tasks 25.09.2008 02:12:10\|\|Project communication failed: attempting access to reference site 25.09.2008 02:12:11\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:12:13\|lhcathome\|Scheduler request failed: Couldn\'t connect to server 25.09.2008 02:13:13\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 1 completed tasks 25.09.2008 02:13:28\|lhcathome\|Scheduler request succeeded: got 0 new tasks 25.09.2008 02:28:38\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:28:45\|\|Project communication failed: attempting access to reference site 25.09.2008 02:28:46\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:28:48\|lhcathome\|Scheduler request failed: Couldn\'t connect to server 25.09.2008 02:32:18\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:32:25\|\|Project communication failed: attempting access to reference site 25.09.2008 02:32:26\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:32:28\|lhcathome\|Scheduler request failed: Couldn\'t connect to server 25.09.2008 02:32:53\|lhcathome\|Sending scheduler request: Requested by user. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:33:38\|lhcathome\|Scheduler request succeeded: got 0 new tasks 25.09.2008 02:33:43\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:33:48\|lhcathome\|Scheduler request succeeded: got 0 new tasks 25.09.2008 02:34:53\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:35:00\|\|Project communication failed: attempting access to reference site 25.09.2008 02:35:01\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:35:03\|lhcathome\|Scheduler request failed: Couldn\'t connect to server 25.09.2008 02:35:13\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:35:20\|\|Project communication failed: attempting access to reference site 25.09.2008 02:35:21\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:35:23\|lhcathome\|Scheduler request failed: Couldn\'t connect to server 25.09.2008 02:35:33\|lhcathome\|Fetching scheduler list 25.09.2008 02:35:40\|\|Project communication failed: attempting access to reference site 25.09.2008 02:35:41\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:36:43\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:36:50\|\|Project communication failed: attempting access to reference site 25.09.2008 02:36:51\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:36:53\|lhcathome\|Scheduler request failed: Couldn\'t connect to server 25.09.2008 02:37:03\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:37:10\|\|Project communication failed: attempting access to reference site 25.09.2008 02:37:11\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:37:13\|lhcathome\|Scheduler request failed: Couldn\'t connect to server 25.09.2008 02:38:14\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:38:21\|\|Project communication failed: attempting access to reference site 25.09.2008 02:38:22\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:38:24\|lhcathome\|Scheduler request failed: Couldn\'t connect to server 25.09.2008 02:39:44\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:39:51\|\|Project communication failed: attempting access to reference site 25.09.2008 02:39:52\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:39:54\|lhcathome\|Scheduler request failed: Couldn\'t connect to server 25.09.2008 02:39:59\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:40:05\|\|Project communication failed: attempting access to reference site 25.09.2008 02:40:06\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:40:09\|lhcathome\|Scheduler request failed: Couldn\'t connect to server 25.09.2008 02:40:14\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:40:39\|lhcathome\|Scheduler request succeeded: got 0 new tasks 25.09.2008 02:40:54\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:41:57\|\|Running CPU benchmarks 25.09.2008 02:41:57\|\|Suspending computation - running CPU benchmarks 25.09.2008 02:42:28\|\|Benchmark results: 25.09.2008 02:42:28\|\| Number of CPUs: 2 25.09.2008 02:42:28\|\| 1446 floating point MIPS (Whetstone) per CPU 25.09.2008 02:42:28\|\| 2716 integer MIPS (Dhrystone) per CPU 25.09.2008 02:42:29\|\|Resuming computation 25.09.2008 02:44:27\|\|Project communication failed: attempting access to reference site 25.09.2008 02:44:28\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:44:29\|lhcathome\|Scheduler request failed: Server returned nothing (no headers, no data) 25.09.2008 02:44:59\|lhcathome\|Sending scheduler request: Requested by user. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:48:57\|\|Project communication failed: attempting access to reference site 25.09.2008 02:48:58\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:48:59\|lhcathome\|Scheduler request failed: Server returned nothing (no headers, no data) 25.09.2008 02:49:24\|lhcathome\|Sending scheduler request: Requested by user. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:49:30\|\|Project communication failed: attempting access to reference site 25.09.2008 02:49:31\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:49:34\|lhcathome\|Scheduler request failed: Couldn\'t connect to server 25.09.2008 02:50:34\|lhcathome\|Fetching scheduler list 25.09.2008 02:50:41\|\|Project communication failed: attempting access to reference site 25.09.2008 02:50:42\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:50:59\|lhcathome\|Fetching scheduler list 25.09.2008 02:51:06\|\|Project communication failed: attempting access to reference site 25.09.2008 02:51:07\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:51:34\|lhcathome\|Fetching scheduler list 25.09.2008 02:51:41\|\|Project communication failed: attempting access to reference site 25.09.2008 02:51:42\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:51:59\|lhcathome\|Fetching scheduler list 25.09.2008 02:52:05\|\|Project communication failed: attempting access to reference site 25.09.2008 02:52:06\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:52:14\|lhcathome\|Fetching scheduler list 25.09.2008 02:52:21\|\|Project communication failed: attempting access to reference site 25.09.2008 02:52:22\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:52:49\|lhcathome\|Fetching scheduler list 25.09.2008 02:52:56\|\|Project communication failed: attempting access to reference site 25.09.2008 02:52:57\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 02:53:09\|lhcathome\|Fetching scheduler list 25.09.2008 02:53:29\|lhcathome\|Master file download succeeded 25.09.2008 02:53:34\|lhcathome\|Sending scheduler request: Requested by user. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 02:53:39\|lhcathome\|Scheduler request succeeded: got 0 new tasks 25.09.2008 03:01:14\|climateprediction.net\|Sending scheduler request: To send trickle-up message. Requesting 0 seconds of work, reporting 0 completed tasks 25.09.2008 03:01:19\|climateprediction.net\|Scheduler request succeeded: got 0 new tasks 25.09.2008 03:08:49\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 03:08:56\|\|Project communication failed: attempting access to reference site 25.09.2008 03:08:57\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 03:08:59\|lhcathome\|Scheduler request failed: Couldn\'t connect to server 25.09.2008 03:10:00\|lhcathome\|Sending scheduler request: To fetch work. Requesting 345600 seconds of work, reporting 0 completed tasks 25.09.2008 03:10:06\|\|Project communication failed: attempting access to reference site 25.09.2008 03:10:07\|\|Access to reference site succeeded - project servers may be temporarily down. 25.09.2008 03:10:10\|lhcathome\|Scheduler request failed: Couldn\'t connect to server What a shity project............... ID: 20516 · Reply Quote

dr_mabuse Send message Joined: 30 Dec 05 Posts: 57 Credit: 835,284 RAC: 0	Message 20517 - Posted: 25 Sep 2008, 1:41:22 UTC What a childish staement, my little Bouncer ! ID: 20517 · Reply Quote

Brian Silvers Send message Joined: 3 Jan 07 Posts: 124 Credit: 7,065 RAC: 0	Message 20523 - Posted: 25 Sep 2008, 10:54:12 UTC To clarify, if there was work available for other hosts, you will be told that there was work available for other platforms in the response message from the scheduler. There are tasks \"in progress\" right now, but no tasks needing to be sent out. This project is at least fairly reliable when it comes to sending correct messages to BOINC hosts when there is no work, unlike the major problems being encountered over at Cosmology. Also, bear in mind that the actual LHC device is down until sometime next year, so there may not be any work available for a few months. ID: 20523 · Reply Quote

Brian Silvers Send message Joined: 3 Jan 07 Posts: 124 Credit: 7,065 RAC: 0	Message 20530 - Posted: 25 Sep 2008, 19:00:43 UTC - in response to Message 20526. To clarify, if there was work available for other hosts, you will be told that there was work available for other platforms in the response message from the scheduler. Close, except littleBouncer\\\'s hosts are Intel and AMD processors running on WinXP. A non-supported platform is not the issue here. The thread title is a tad misleading for the uninitiated. I wasn\'t talking about a user of a non-supported OS platform, but was thinking more about the issue that Cosmology is having with their HR implementation. Since LHC does not use HR (to my knowledge), then I\'ll agree that I was using either a poor example or did not explain myself enough. I quickly typed out that message earlier as I was waiting for my turn in the bathroom so I could finish getting ready for work... As for the sched_op_debug thing, I thought that it would still tell you the HR-related messages, but since I do not use the newer versions of BOINC, I could very well be mistaken. ID: 20530 · Reply Quote

Brian Silvers Send message Joined: 3 Jan 07 Posts: 124 Credit: 7,065 RAC: 0	Message 20533 - Posted: 25 Sep 2008, 21:40:11 UTC - in response to Message 20531. I think LHC@home does not use HR. I have primarily Linux hosts. I have not received LHC work for quite some time but if I recall correctly they were almost always grouped with Windows hosts so heterogenous redundancy seems to be in effect here. That is the case. My line of thinking this moring was related to being involved in a Homogeneous Redunancy project that currently has a very severe problem with HR (Cosmology). I was in a bit of a rush, and have something else on my mind too (death of someone I grew up with), so I was a bit...terse (and perhaps tense) this morning... Anyway, I noticed after posting that the status box listed the project as \"down\", but with work available. I didn\'t have the time to go back to clarify... As for the newer versions of BOINC, I\'m still not convinced to try even 5.10.45, let alone 6.x.x. Many things are for Vista, which I don\'t have and don\'t plan to have anytime soon. As for the non-Vista stuff, most of that seems to be geared towards making the messages more palitable for \"non-technical\" users that might stumble across them. I think it also has some fix for NTLM proxies, but since I don\'t use one, that\'s not an issue I need fixed. ID: 20533 · Reply Quote

Brian Silvers Send message Joined: 3 Jan 07 Posts: 124 Credit: 7,065 RAC: 0	Message 20541 - Posted: 26 Sep 2008, 14:32:41 UTC - in response to Message 20538. Anyway, I noticed after posting that the status box listed the project as \\\"down\\\", but with work available. I didn\\\'t have the time to go back to clarify... Actually the scheduler was down but everything else was running. There were several thousands results available but if the scheduler was down then the results won\\\'t get sent when hosts request work. When I looked, the only things running were the data-driven web pages and the upload/download server, i.e. the top two entries on the server status page. Everything else had a status of \"not running\". This is getting into minutae though... Since we (you, me, and littlebouncer) all looked at the situation at different times, the conditions most likely were different for all 3 of us, even if only slightly. Bottom line is, if the scheduler is down, nobody is getting work. I recall you saying you tried to install 5.1.x but it did not go well, crashed or something. I vaguely recall one release in the early 5.x series which was quickly withdrawn because it caused a lot of grief. Perhaps you were unlucky enough to try that one. It was 5.10.28 that blew up on me. I tell you what. When David Anderson and/or Eric Korpela make 5.10.45 the minimum version that will get work from SETI instead of allowing 3.x and 4.x clients to continue to download work, then I\'ll consider it. The \"fear\" of not forcing a newer version is that people were behind NTLM proxies and they would be \"cut off\" and that those people MIGHT be sponsors and that they just absolutely could not \"cut off\" a sponsor, nor could they even ask any of the sponsors if they were having that problem or if they knew people who did have problems, nor could they contact a sponsor and ask them to update. Meanwhile, knowing all this, they did not do testing of the newest science applications there under those versions of BOINC. That\'s what I call \"shameful\"... ID: 20541 · Reply Quote

Brian Silvers Send message Joined: 3 Jan 07 Posts: 124 Credit: 7,065 RAC: 0	Message 20545 - Posted: 26 Sep 2008, 18:54:48 UTC - in response to Message 20544. Last modified: 26 Sep 2008, 18:56:27 UTC Now, from your latest post I'm getting a different picture. I could be all wrong but it sounds like maybe you are trying to make a political statement by not upgrading. No, I just mentioned that because I do think that they have their priorities out of order and that they knew that there were older clients downloading tasks, yet either they did not test that scenario or they did and considered 0-credit as "A-OK" so long as it returned a valid result. IOW, they speak with forked tongue in regards to the value of credit parity. Anyway, my primary reasons for not going for any newer versions are, in order: The installer blowing up and leaving BOINC in a non-functioning state that took multiple reinstalls of 5.8.16 to fully correct. No real need for any of the newer features. The bugs of the newer versions (apppears to be sloppy testing and/or poor judgement on "go / no go" decisions to me). Only when this project started doing the cancels did I have a \"need\", but since I do not run this project very often, and considering that when I do I run it exclusively until I've cleared out the work, then I can manually abort tasks just as easily. ID: 20545 · Reply Quote

Brian Silvers Send message Joined: 3 Jan 07 Posts: 124 Credit: 7,065 RAC: 0	Message 20548 - Posted: 26 Sep 2008, 22:46:33 UTC - in response to Message 20547. Last modified: 26 Sep 2008, 22:56:04 UTC I'm confused. What am I missing here? The understanding that I have no life, for one... LOL I'm one of several new hires where I work. The boss had a sit-down meeting with each of us new hires individually today. What he told me was that he felt that I was not shy and that I have a self-deprecating sense of humor. I laugh at myself. It may not come across here, which is why I scoffed at a certain suggestion... Text-only personas may not reflect actual personalities... To abort redundant tasks manually one must first go to the LHC website and see which of his unstarted tasks have reached quorum then abort them in the manager. I don't see how that is just as easy as letting the software cancel the tasks for you. Furthermore, if you run a version that will comply with server requests to check in, for example every hour, then you can have redundant tasks canceled even while you are away at work or on vacation or whatever, assuming the server is configured to ask hosts to check in every hour. Well, if I do "miss one" (or several of the shorter tasks), it is typically because I've been sleeping or am not at home. I do see the merit in doing what you're talking about, but I have seen problems with not having a network connection with various 5.10.x versions. Things have gotten better for me lately, but a while back my cable modem would drop at random times. Setting to NNT (or suspending network) would have been something I would've needed to do, which would defeat the purpose. I'll think about it... ID: 20548 · Reply Quote

LHC@home