What happens when you try to open a second manager instance? (when the first won't connect)

Usually the second will connect, but not always. It hasn't happened lately, but it did a couple of days ago. What I did was start the client while my system was still loading services, which caused a conflict in some fashion. When I wait for the system to fully load, I don't have a problem. A little too eager on my part I guess.

:-)

I would still use boincview even if you only have one machine. :)

---

Fear will keep the local systems in line. Fear of this battle station. - Grand Moff Tarkin

What happens when you try to open a second manager instance? (when the first won't connect)

Usually the second will connect, but not always. It hasn't happened lately, but it did a couple of days ago. What I did was start the client while my system was still loading services, which caused a conflict in some fashion. When I wait for the system to fully load, I don't have a problem. A little too eager on my part I guess.

---

Hopper, your computers are hidden, so I can't see the OS. On my tiny fleet of four diverse machines, I see the "can't connect to localhost" fairly frequently on a Win98SE machine, less often on another, seldom if ever on two WinXPPro machines.

Just one system, running XP.

What happens when you try to open a second manager instance? (when the first won't connect)

---

Fear will keep the local systems in line. Fear of this battle station. - Grand Moff Tarkin

Hopper, your computers are hidden, so I can't see the OS. On my tiny fleet of four diverse machines, I see the "can't connect to localhost" fairly frequently on a Win98SE machine, less often on another, seldom if ever on two WinXPPro machines.

Just one system, running XP.

---

My win2k system does this sometimes. I usually right click on the manager icon on the system tray and open it again and it connects. Sometimes I have to click the icon and launch it again. Not sure why the first instance won't connect, but the second one usually does.

I haven't used the manager much anymore though after installing "boincview". Its a nice tool and you can manage all of your clients from one interface.

---

Fear will keep the local systems in line. Fear of this battle station. - Grand Moff Tarkin

I was talking about the manager, wouldn't connect to localhost i.e. client.

Hopper, your computers are hidden, so I can't see the OS. On my tiny fleet of four diverse machines, I see the "can't connect to localhost" fairly frequently on a Win98SE machine, less often on another, seldom if ever on two WinXPPro machines.

Sometimes it goes to this state in mid-run, but more often it wakes up from a reboot in this state. (yes, I reboot my Win98SE machines several times a week on average--not usually because they have crashed, but for other cautious reasons).

As to kitchen remedies, once in a while just exiting BOINCmgr, checking to assure neither boinc.exe nor an science application was running, and restarting BOINCmgr from the Start|run command has worked.

At least a few times, I've instead hand-started boinc.exe, then BOINCmgr. I think this has appeared to work at least sometimes.

Also I've used full system reboots--not, however, always successfully.

I've not yet given up and reinstalled.

Lastly, I agree that from a volunteer's point of view, this is a painfully unreliable system.

---

Well, I'll bet that the trux version you're using is based on an older boinc version. Older boinc versions use port 1043 as the "loopback" address. MS has chosen to use 1043 on some programs, even though that port was assigned to boinc by ICANN. If the MS program loads first at start up it grabs 1043 and boinc won't work. The later "developemental" builds of boinc have switched to port 31416 to get rid of this issue. You'll either have to run a Developemental version of boinc to fix this, Wait a few more days until the new "Recommended" release comes out (5.4.x), or wait for one of the optimizers to optimize the new recommended version with their "enhancements".

When BIONIC went loopy, I was using the 'official' version. I dumped the install and re-did it, twice to no avail. I doubt very much it was port issue since it was running peachy up to the day of the update. The Trux version I'm using now is on port 31416, which means it's not on the older BIONIC dev.

Regardless, I'm back up and running.

---

Well, I'll bet that the trux version you're using is based on an older boinc version. Older boinc versions use port 1043 as the "loopback" address. MS has chosen to use 1043 on some programs, even though that port was assigned to boinc by ICANN. If the MS program loads first at start up it grabs 1043 and boinc won't work. The later "developemental" builds of boinc have switched to port 31416 to get rid of this issue. You'll either have to run a Developemental version of boinc to fix this, Wait a few more days until the new "Recommended" release comes out (5.4.x), or wait for one of the optimizers to optimize the new recommended version with their "enhancements".

tony

4/10/06 11:03:19 PM||Starting BOINC client version 5.3.12.tx36 for windows_intelx86
4/10/06 11:03:20 PM||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
4/10/06 11:03:20 PM||Data directory: D:\\PROGRAM FILES\\BOINC
4/10/06 11:03:20 PM|SETI@home|Found app_info.xml; using anonymous platform
4/10/06 11:03:20 PM||Processor: 1 AuthenticAMD AMD Athlon(tm) XP 3000+
4/10/06 11:03:20 PM||General prefs: no separate prefs for home; using your defaults
4/10/06 11:03:20 PM||Remote control not allowed
4/10/06 11:03:20 PM||Listening on port 31416

This version of Trux's client uses port 31416 by default
:)

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

And God said"Let there be light."But then the program crashed because he was trying to access the 'light' property of a NULL universe pointer.

Unfortunately, simple would also have meant dead. The only reason Seti still exist is that it is the test bed for Boinc. The DC concept had been proven successful with Seti, but the only way to get more money was to show the expanded capability that Boinc represents. Seti itself has virtually no funding since the government cut NASA funding and in turn NASA stopped funding Seti.

NASA cut SETI's funding because the mathamatical probability of finding a signal from another planet is so remote it's not worth pumping money into. It's a big sky.

If I'm not mistaken, SETI@HOME was never funded by NASA.

It still remains that SETI Classic is a victim of its own success. At a minimum, Classic had to have the ability to update the "science" part without user intervention (or block users running old screen savers).

We're also now in a world where most computers have lots of security software running on them.

... and as Tony points out, Microsoft uses ports without registering them first with IANA.

You aren't supposed to just "pick" a port and use it, but because of software that misbehaves and does just that, BOINC has to do the same.

---

I switched to an optimized client when I re-installed. I went with Trux and Crunch3rs old AMD SSE2 set. My CPU is a little picky on which ones would scream (SSE2 & SSE3) and which wouldn't, I tried 4.

Thanks for the help, I appreciate it.

Re: mmciastro, I was talking about the manager, wouldn't connect to localhost i.e. client. All this new lingo, in the old days it was a nice little GUI, you started it and it ran, simple no fuss. Now we have to have a Manager to handle the communication between the client & server. Simple is always best, SETI could stand to take a sheet out of distrubted.net's song book.

Well, I'll bet that the trux version you're using is based on an older boinc version. Older boinc versions use port 1043 as the "loopback" address. MS has chosen to use 1043 on some programs, even though that port was assigned to boinc by ICANN. If the MS program loads first at start up it grabs 1043 and boinc won't work. The later "developemental" builds of boinc have switched to port 31416 to get rid of this issue. You'll either have to run a Developemental version of boinc to fix this, Wait a few more days until the new "Recommended" release comes out (5.4.x), or wait for one of the optimizers to optimize the new recommended version with their "enhancements".

tony

---

Unfortunately, simple would also have meant dead. The only reason Seti still exist is that it is the test bed for Boinc. The DC concept had been proven successful with Seti, but the only way to get more money was to show the expanded capability that Boinc represents. Seti itself has virtually no funding since the government cut NASA funding and in turn NASA stopped funding Seti.

NASA cut SETI's funding because the mathamatical probability of finding a signal from another planet is so remote it's not worth pumping money into. It's a big sky.

SETI is not the first distributed computing effort nor is it the only unfunded. Distributed.net was the first, which I mentioned earlier. Go download their client, you can run it either as command line or if you like watching the CPU make wavey lines, you can switch to GUI. However, you can run more than 1 type of project from this interface, right now it's RC5-72 & OGRp2.

Regardless, I'm for a simple piece of software that you don't have to tweak to get it to run like a bat out of h*ll.

---

I switched to an optimized client when I re-installed. I went with Trux and Crunch3rs old AMD SSE2 set. My CPU is a little picky on which ones would scream (SSE2 & SSE3) and which wouldn't, I tried 4.

Thanks for the help, I appreciate it.

Re: mmciastro, I was talking about the manager, wouldn't connect to localhost i.e. client. All this new lingo, in the old days it was a nice little GUI, you started it and it ran, simple no fuss. Now we have to have a Manager to handle the communication between the client & server. Simple is always best, SETI could stand to take a sheet out of distrubted.net's song book.

Unfortunately, simple would also have meant dead. The only reason Seti still exist is that it is the test bed for Boinc. The DC concept had been proven successful with Seti, but the only way to get more money was to show the expanded capability that Boinc represents. Seti itself has virtually no funding since the government cut NASA funding and in turn NASA stopped funding Seti.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

I switched to an optimized client when I re-installed. I went with Trux and Crunch3rs old AMD SSE2 set. My CPU is a little picky on which ones would scream (SSE2 & SSE3) and which wouldn't, I tried 4.

Thanks for the help, I appreciate it.

Re: mmciastro, I was talking about the manager, wouldn't connect to localhost i.e. client. All this new lingo, in the old days it was a nice little GUI, you started it and it ran, simple no fuss. Now we have to have a Manager to handle the communication between the client & server. Simple is always best, SETI could stand to take a sheet out of distrubted.net's song book.

---

I had to re-install. Now with this crap client I can't reload the work I was doing before it went AWOL. Oh well at least it's running again.

Well, if you didn't back up the BOINC directory, you lost those WU's. Nothing to worry about, they will be re-issued.

Every client I've used has been fine. I currently use Trux's Calibrating Client, it raises your benchmarks a bit, as well as calibrates your WU's so you get a more "fair" claimed credit. He also has some Optimized clients, however many use Crunch3rs Seti App which has proven to seriously cut back times on crunching.

I'm happy your running again. Any other problems just post them. I hope this helps you out.

Jeremy

---

Which crap boinc client are you running and what isn't connecting to what? Are you talking manager to daemon? Daemon to download server?

I had to re-install. Now with this crap client I can't reload the work I was doing before it went AWOL. Oh well at least it's running again.

---

I haven't ever had this problem. Have you tried exiting and restarting boinc? Re-boot? Try that and let us know how it goes.

Jeremy

---

Who's having a problem getting BIONIC to hook up with the client? I haven't gotten it to work all freaking day. I know they were down for a memory upgrade. I hate BIONIC sooooooooooo much. Grrrrrr!!

---