Re: BOINC again !? -- I give up.
Mike Evans wrote: For machines with a wired connection I have been in the habit of disabling NM and using the good old network service. Works like a dream and doesn't need tampering with. You can do that through the Admin-services gui if you don't like fiddling with the links in the init directories. But most people nowadays use a WiFi connection, at least on laptops, so the advice to use the good old network service is not much help. as the network service is much, much worse than NM with WiFi in my experience. Both are completely undocumented, so one is in the world of magic. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
Hi; I give up. I am filing a bug. On Sat, 2008-06-28 at 09:48 -0600, Tom Weniger wrote: On Sat, Jun 28, 2008 at 7:50 AM, William Case [EMAIL PROTECTED] wrote: But... Any suggestions on how I get my boinc working. -- Greetings William, I have used the following site to get my boinc going: http://www.gaztronics.net/rc/boinc.php Hope this helps I have followed all of the advice given here. I greatly appreciate everyone's effort to help. However, I still have the original problem. When I yum erase boinc-client and boincmgr and start over with a fresh yum install -- boinc works. It is finding all my projects and running them successfully. Boincmgr reports accurately what boinc is doing and responds to my commands. It is now running in the background. If I where to shutdown my computer and restart, boinc won't restart even though service boinc is running. I can't be more definite than that because I don't have a clue what the problem is. I am not a complete beginner, and no package should be this difficult (two days now) to analyze and get running. The only solution is to file a Fedora bug on boinc and put up with being seared at by the packagers and maintainers. -- Regards Bill; Fedora 9, Gnome 2.22.2 Evo.2.22.2, Emacs 22.2.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
On Sat, 2008-06-28 at 14:30 -0400, William Case wrote: Hi; I give up. I am filing a bug. On Sat, 2008-06-28 at 09:48 -0600, Tom Weniger wrote: On Sat, Jun 28, 2008 at 7:50 AM, William Case [EMAIL PROTECTED] wrote: But... Any suggestions on how I get my boinc working. -- Greetings William, I have used the following site to get my boinc going: http://www.gaztronics.net/rc/boinc.php Hope this helps I have followed all of the advice given here. I greatly appreciate everyone's effort to help. However, I still have the original problem. When I yum erase boinc-client and boincmgr and start over with a fresh yum install -- boinc works. It is finding all my projects and running them successfully. Boincmgr reports accurately what boinc is doing and responds to my commands. It is now running in the background. If I where to shutdown my computer and restart, boinc won't restart even though service boinc is running. I can't be more definite than that because I don't have a clue what the problem is. I am not a complete beginner, and no package should be this difficult (two days now) to analyze and get running. The only solution is to file a Fedora bug on boinc and put up with being seared at by the packagers and maintainers. I believe that what Patrick was trying to tell you is that if you are using NetworkManager, then it's entirely possible that networking isn't fully operational when boinc service starts at bootup which would cause it to fail. That can probably be verified by merely issuing '/sbin/service boinc restart' (assuming that restart is an option for the boinc sysv script). If that works, then it might just be easier to put that command in /etc/rc.d/rc.local (/sbin/service boinc restart) Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
On Sat, 2008-06-28 at 12:51 -0700, Craig White wrote: On Sat, 2008-06-28 at 14:30 -0400, William Case wrote: Hi; I give up. I am filing a bug. On Sat, 2008-06-28 at 09:48 -0600, Tom Weniger wrote: On Sat, Jun 28, 2008 at 7:50 AM, William Case [EMAIL PROTECTED] wrote: But... Any suggestions on how I get my boinc working. -- Greetings William, I have used the following site to get my boinc going: http://www.gaztronics.net/rc/boinc.php Hope this helps I have followed all of the advice given here. I greatly appreciate everyone's effort to help. However, I still have the original problem. When I yum erase boinc-client and boincmgr and start over with a fresh yum install -- boinc works. It is finding all my projects and running them successfully. Boincmgr reports accurately what boinc is doing and responds to my commands. It is now running in the background. If I where to shutdown my computer and restart, boinc won't restart even though service boinc is running. I can't be more definite than that because I don't have a clue what the problem is. I am not a complete beginner, and no package should be this difficult (two days now) to analyze and get running. The only solution is to file a Fedora bug on boinc and put up with being seared at by the packagers and maintainers. I believe that what Patrick was trying to tell you is that if you are using NetworkManager, then it's entirely possible that networking isn't fully operational when boinc service starts at bootup which would cause it to fail. That can probably be verified by merely issuing '/sbin/service boinc restart' (assuming that restart is an option for the boinc sysv script). If that works, then it might just be easier to put that command in /etc/rc.d/rc.local (/sbin/service boinc restart) Exactly. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
Hi Craig; On Sat, 2008-06-28 at 12:51 -0700, Craig White wrote: On Sat, 2008-06-28 at 14:30 -0400, William Case wrote: Hi; I give up. I am filing a bug. On Sat, 2008-06-28 at 09:48 -0600, Tom Weniger wrote: On Sat, Jun 28, 2008 at 7:50 AM, William Case [EMAIL PROTECTED] wrote: But... Any suggestions on how I get my boinc working. -- I believe that what Patrick was trying to tell you is that if you are using NetworkManager, then it's entirely possible that networking isn't fully operational when boinc service starts at bootup which would cause it to fail. That can probably be verified by merely issuing '/sbin/service boinc restart' (assuming that restart is an option for the boinc sysv script). If that works, then it might just be easier to put that command in /etc/rc.d/rc.local (/sbin/service boinc restart) Craig Yes, I am using NetworkManager. I have tried one last test. I removed and re-installed boinc. With that, boinc was able to connect to WCG and download 2 more work units. Boinc has only been able to connect to WCG to get work units on a new install -- never after a re-boot. Boinc is processing those work units now. I have since shut down my computer and rebooted. Since the work units are on my machine, my computer is continuing to process those units. It will take approximately 6 hrs to finish processing them. I am waiting to see if then it can automagically re-connect to WCG and obtain further work units. If it can't I will try Patrick's Network Manager solution. If that works, I then have to decide whether this is a Network Manager bug; a Boinc bug; or both. Of course, if boincmgr does successfully reconnect to WCG and download additional work units, I will write the whole thing off as my screwing around too much while Boinc was just trying to do its thing. -- Regards Bill; Fedora 9, Gnome 2.22.2 Evo.2.22.2, Emacs 22.2.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up. --correction
[snip] If that works, I then have to decide whether this is a Network Manager bug; a Boinc bug; or both. Of course, if boincmgr does successfully bug; a Boinc bug; or both. Of course, if boinc-clent does successfully reconnect to WCG and download additional work units, I will write the whole thing off as my screwing around too much while Boinc was just trying to do its thing. -- Regards Bill; Fedora 9, Gnome 2.22.2 Evo.2.22.2, Emacs 22.2.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
On Sat, 2008-06-28 at 16:19 -0400, William Case wrote: If it can't I will try Patrick's Network Manager solution. If that works, I then have to decide whether this is a Network Manager bug; a Boinc bug; or both. Of course, if boincmgr does successfully reconnect to WCG and download additional work units, I will write the whole thing off as my screwing around too much while Boinc was just trying to do its thing. service boinc restart a relatively simple fix. If you were to file a bug report, I would file it against NetworkManager as this would mean that boinc works when networking is fully functional. Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
On Sun, 2008-06-29 at 06:48 +0800, Ed Greshko wrote: Craig White wrote: On Sat, 2008-06-28 at 16:19 -0400, William Case wrote: If it can't I will try Patrick's Network Manager solution. If that works, I then have to decide whether this is a Network Manager bug; a Boinc bug; or both. Of course, if boincmgr does successfully reconnect to WCG and download additional work units, I will write the whole thing off as my screwing around too much while Boinc was just trying to do its thing. service boinc restart a relatively simple fix. If you were to file a bug report, I would file it against NetworkManager as this would mean that boinc works when networking is fully functional. If the analysis of NM starting too late in the boot process is correct, wouldn't one of these make life a bit more tolerable? Keeping in mind that I don't use F9, NM, or BOINC. :-) 1. Change the script number in /etc/init.d of NM to a lower number than BOINC or change BOINC number to one higher than NM. 2.Do not configure BOINC to start a boot time in the usual manner but add a server boinc start to rc.local. I too don't use NM or BOINC but I do use F9 On F8, this clearly was a problem... # grep chkconfig /etc/init.d/NetworkManager # chkconfig: - 98 02 but on F9, I would have thought that this would have solved some of these issues... # grep chkconfig /etc/init.d/NetworkManager # chkconfig: - 27 84 which would have it start up much earlier (of course if this was an upgrade instead of clean install, I don't know if the sequences are adjusted when the upgrade is accomplished). I don't have BOINC installed but I have to believe that the startup sequence number would already have it loading after NM. I would think that moving it up from 98 to 27 would have solved many of the reported issues but perhaps not...I just don't know and as you say, I don't personally use NM. My own personal preference would be to leave NM enabled at boot time and put '/sbin/server boinc restart' in rc.local only because sometimes I look at boot time services and would want to know that the 'intent' was to start it up. Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
On Sun, 2008-06-29 at 06:48 +0800, Ed Greshko wrote: If the analysis of NM starting too late in the boot process is correct, wouldn't one of these make life a bit more tolerable? Keeping in mind that I don't use F9, NM, or BOINC. :-) 1. Change the script number in /etc/init.d of NM to a lower number than BOINC or change BOINC number to one higher than NM. While I don't use BOINC, I've had had similar issues with other programs, and moving network manager's start up position has helped with some, but not with others. Moving those other things start up position further back has helped with a few more, but not all. I have two concerns with doing that sort of thing: I shouldn't have to do so much mangling to get things to work that are expected to work in their current configuration. And I might have to keep on fiddling around if updates undo my mangling. 2.Do not configure BOINC to start a boot time in the usual manner but add a server boinc start to rc.local. I've had to do something similar. It strikes me that something is *really* broken with Network Manager. Other services wait until they start before returning to the next item in the startup sequence. Network Manager seems to be returning as ready, before it is, and buggering up other things that follow. -- [EMAIL PROTECTED] ~]$ uname -r 2.6.25.6-55.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
On Sun, 2008-06-29 at 14:10 +0930, Tim wrote: It strikes me that something is *really* broken with Network Manager. Other services wait until they start before returning to the next item in the startup sequence. Network Manager seems to be returning as ready, before it is, and buggering up other things that follow. I think that they've been intensely focused on quick startup from boot times. Damn the torpedoes...full speed ahead. That's why it's so important to bugzilla these things. Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
