| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 17
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I was having the same problem on some of my machines and I believe it was due to a port conflict with the mail client. What I did was stop the mail client, start BOINC and then restart mail. I haven't had a problem since. It seemed to happen right after an install of BOINC. I can't remeber the port numbers right now but i used the netstat command under dos to see the problem. Hope this helps
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks, Doneske. Teletran -- let us know if this clears the problem for you. If it doesn't, I will see if I can get one of the WCG techs in here to work with you on it.
|
||
|
|
teletran
Senior Cruncher Joined: Jul 27, 2005 Post Count: 378 Status: Offline |
Doneske,
----------------------------------------Could you provide a little more detail on what you mean by a conflict with the mail client? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
What seemed to happen to me was the mail client on my machine had registered on port 1043 (I think that was the port). It seemed when BOINC started it was waiting for 1043. With the netstat -o command I could see that I had PIDs on the same port. When I stopped the mail client, it released the port and BOINC started using it. The next time I started the mail client it registered on another port and I didn't have any other problems after that. It happened on 3 out of 7 machines. On your machine it could be another piece of software that happened to register on that port. I don't know if BOINC has to use that port or if that is just the one it happened to pick. I wish I could be more specific but once it started working I didn't look into it anymore.
Best regards |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges:
|
This is a known issue and will be resolved with the next release of the BOINC agent (due sometime within the next couple of weeks). BOINC will start using port 31416 (pi) instead of 1043.
If you are adventurous you can try the development version of the BOINC agent and see if that resolves your problem. It is available at http://boinc.berkeley.edu/download.php?dev=1 However - this is a development build so there might be a few quirks. |
||
|
|
teletran
Senior Cruncher Joined: Jul 27, 2005 Post Count: 378 Status: Offline |
knreed,
----------------------------------------I'll let the UD software run for now and try the new client when it's released. Then I'll post back with results. Thanks to everyone who helped out. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have the same trouble. I ran Microsofts Bootvis tool which lays out the files to be loaded at start up in a better manner and it helped out alot.
I didn't notice any difference tho when updated to the experimental client. So you may try the Bootvis tool and see if that helps. Tom ![]() |
||
|
|
|