 |
|
Message boards :
Number crunching :
Message from server: Error in request message: fgets() failed
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 10 Dec 05 Posts: 3 Credit: 10,433,042 RAC: 296 |
Hi, not sure if this is the correct place to post but here I go (let me know the right place if this isn't and I'll repost) Since Sep-16 none of my computers have been able to communicate. Getting the error message: "Message from server: Error in request message: fgets() failed" I have search the board and not found anything related. Not sure if proper to post my User ID or if that will do any help. Thanks in advance, E.A.R. |
 astroWXSend message Joined: 5 Aug 04 Posts: 1496 Credit: 95,522,203 RAC: 0 |
Your computers are hidden, so I can only guess 'Linux' -- something I gave-up a few years ago. Your error message differs from mine -- but they smell the same. I can only relay my experience. Until your message, I thought I was the only snake-bit participant. I tried everything I could think of but nothing worked. Then, staff posted that there was a day-long heavy-duty script running looking for .oucs. entries. Shortly before that, I edited my "client_state" files, changing .oucs. to .oerc. in the url for this project. Whether my edit or staff's script did the trick, I have no clue. Whatever, the boxes that were heretofore unable to communicate miraculously did so afterward. Given that you still have the problem, I suspect that the edit did the trick. If you are comfortable messing with control files, in boinc's client-state file, in this section (after shutting-down CPDN and boinc): <project> <master_url>http://climateprediction.net/</master_url> near the end of the block (about half a screen), find this entry: <scheduler_url>http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi</scheduler_url> Change "oucs" to "oerc" and save the file. Restart boinc and you should be good to go. It worked for me; I hope it works for you. "We have met the enemy and he is us." -- Pogo Greetings from coastal Washington state, the scenic US Pacific Northwest. |
|
Send message Joined: 10 Dec 05 Posts: 3 Credit: 10,433,042 RAC: 296 |
Thanks. Mostly WinXPs here. I will give a try to change the "client_state" files and wil be back. |
|
Send message Joined: 10 Dec 05 Posts: 3 Credit: 10,433,042 RAC: 296 |
It works!, I'm a happy camper even though I would need to change about a dozen hosts ;-) P.S. I got a "new venue" message |
|
Send message Joined: 14 Jan 09 Posts: 1 Credit: 1,722,128 RAC: 0 |
The change oucs -> oerc solved my problem. Thanks. Martin |
|
astroWX Send message Joined: 5 Aug 04 Posts: 1496 Credit: 95,522,203 RAC: 0 |
It works!, I'm a happy camper even though I would need to change about a dozen hosts ;-) None of the machines I tweaked produced the "new venue" message; I can't explain it. Good to see that the tweak worked for you and Martin. Thanks for posting your results. "We have met the enemy and he is us." -- Pogo Greetings from coastal Washington state, the scenic US Pacific Northwest. |
|
Send message Joined: 6 Aug 04 Posts: 195 Credit: 28,261,218 RAC: 10,511 |
Coincident in time (16th September) with the server name change from oucs to oerc that Jonathan advised ? |
|
Ananas Send message Joined: 31 Oct 04 Posts: 336 Credit: 3,316,482 RAC: 0 |
The venue thing is easy to explain : When the "host" part of the sched_reply.xml (especially "host_venue") is empty or missing, the core client sets the host venue to "default". When the next contact contains a properly formed host section, it depends on the setting on your account : If the host venue for this host is "default" anyway, there is no change and you will not receive a "new venue" message If the host venue for this host is supposed to be a specific one, the core client changes his venue and you will receive the "new venue" message edit : I forgot to mention ... this behaviour is a bug in BOINC of course, the missing XML tag should not trigger a change, the core client should just keep the old venue. |
|
Send message Joined: 3 Jan 06 Posts: 4 Credit: 9,039,254 RAC: 7,131 |
I got the same problem! HAve no idea what to do. |
|
Send message Joined: 5 Sep 04 Posts: 7629 Credit: 24,240,330 RAC: 0 |
|
|
Send message Joined: 3 Jan 06 Posts: 4 Credit: 9,039,254 RAC: 7,131 |
Thanks, I ll give a try! |
|
Send message Joined: 3 Jan 06 Posts: 4 Credit: 9,039,254 RAC: 7,131 |
Hi, I detached from the project and cannot attach again. What can I do? |
|
Dave Jackson Send message Joined: 15 May 09 Posts: 4533 Credit: 18,852,303 RAC: 21,641 |
[Hi, I detached from the project and cannot attach again. What can I do?] What message do you get when you try and attach again? You should just need to supply your user name and password. Dave[/quote] |
|
Iain Inglis Send message Joined: 16 Jan 10 Posts: 1084 Credit: 7,768,923 RAC: 4,633 |
Hi, I detached from the project and cannot attach again. What can I do? Don't forget to to take the 'existing user' option ... |
|
Send message Joined: 15 Feb 06 Posts: 1 Credit: 1,328,575 RAC: 0 |
"Message from server: Error in request message: fgets() failed" The solution posted in message 42952 worked for me. Thanks astroWX. Neil |
|
astroWX Send message Joined: 5 Aug 04 Posts: 1496 Credit: 95,522,203 RAC: 0 |
"Message from server: Error in request message: fgets() failed" Apologies for the response delay, Neil --> I was away from home for a few days. I had to use the "fix" again about a week ago on a few machines, after the server hard-drive replacement, including two machines that were "fixed" per my original post. (I have no clue as to how they went belly-up again -- e.g., no restored backups.) I'm glad you found the tweak helpful. Thanks for posting your result. "We have met the enemy and he is us." -- Pogo Greetings from coastal Washington state, the scenic US Pacific Northwest. |
©2024 cpdn.org
