No, the system never downloaded any WUs under 7.0.64, so I re-installed 7.0.28 and immediately downloaded WUs. I'm as much at a loss as everyone else as to why 7.0.64(x64) behaves so strangely on this system.

Since I was getting nowhere with 7.0.64(x64), I decided to re-install 7.0.28(x64) on May 5 and let it crunch until the Tuesday outage. At least the system was being productive. After everything had processed, uploaded and been reported, I tried installing 7.0.64(x64) once again and was still getting the "connecting to localhost" problem message. Remembering that some of the features that are in 7.0.64 began in version 7.0.40, I thought I'd install it even though it is buggy just to see what would happen. Lo and behold, 7.0.40(x64) immediately connected to localhost. At no time during this did I download any WUs. I then tried installing 7.0.41 and 7.0.42 with the same result. BOINC 7.0.43(x64) was stuck at "connecting to localhost" (just like 7.0.64) for several minutes until I killed it.

Was something changed between 7.0.42 and 7.0.43 that might have been the beginning of this glitch I've been experiencing? Just wondering...

Rich

Since I was getting nowhere with 7.0.64(x64), I decided to re-install 7.0.28(x64) on May 5 and let it crunch until the Tuesday outage. At least the system was being productive. After everything had processed, uploaded and been reported, I tried installing 7.0.64(x64) once again and was still getting the "connecting to localhost" problem message. Remembering that some of the features that are in 7.0.64 began in version 7.0.40, I thought I'd install it even though it is buggy just to see what would happen. Lo and behold, 7.0.40(x64) immediately connected to localhost. At no time during this did I download any WUs. I then tried installing 7.0.41 and 7.0.42 with the same result. BOINC 7.0.43(x64) was stuck at "connecting to localhost" (just like 7.0.64) for several minutes until I killed it.

Was something changed between 7.0.42 and 7.0.43 that might have been the beginning of this glitch I've been experiencing? Just wondering...

Rich

Loads of things changed between 7.0.42 and 7.0.43:

BOINC 7.0 Change Log and news

The first changeset's i'd suspect are:

client: disable remote access if
-> gui_rpc_auth.cfg is empty, or
-> it doesn't exist and we can't open it for writing, or
-> the write to it fails.

client: don't crash if GUI RPC password is too long (from RustyBSD) (change from max 256 chars to 512 chars).

client: if gui_rpc_auth.cfg is empty, print a warning but don't fail with an error; an empty GUI RPC password is allowed. (to error out is not a known verb, David...)

So i'd try removing the gui_rpc_auth.cfg from the Boinc Data directory as see if you can connect, (you shouldn't be able to)
then try putting a fresh one in there with at least some text in there (it's normally 32 characters), (keep your original one safe)

Claggy

Yesterday upgraded to 7.0.65 on Linux Ubuntu, using latest Gianfranco [Locutusofborg] build. Default the [Linux] gui_rpc_auth.cfg is empty, this distro or the standard repo of Ubuntu [still 7.0.27 in Raring 13.04] and indeed a warning is now printed. But, as I wrote few days ago, putting anything into that file and connecting the BM to the core client always fails [Not found why, certainly not ownership as return zero length restores connect ability]. Anyway, I've specified in remote_hosts what IPs can connect and put the UFW firewall up... nothing gets through except the specified IPs.

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

The first changeset's i'd suspect are:


client: disable remote access if
-> gui_rpc_auth.cfg is empty, or
-> it doesn't exist and we can't open it for writing, or
-> the write to it fails.

client: don't crash if GUI RPC password is too long (from RustyBSD) (change from max 256 chars to 512 chars).

client: if gui_rpc_auth.cfg is empty, print a warning but don't fail with an error; an empty GUI RPC password is allowed. (to error out is not a known verb, David...)


So i'd try removing the gui_rpc_auth.cfg from the Boinc Data directory as see if you can connect, (you shouldn't be able to)
then try putting a fresh one in there with at least some text in there (it's normally 32 characters), (keep your original one safe)

After making sure the original files were safely backed up elsewhere, I again re-installed 7.0.64(x64), removed the gui_rpc_auth.cfg from the BOINC Data directory and you were correct - wasn't able to connect to localhost.

Then I tried putting a fresh gui_rpc_auth.cfg in there. Still no joy.
After removing the fresh gui_rpc_auth.cfg, I even tried doing a Repair install of 7.0.64(x64) without success. Still stuck at "connecting to localhost" at the bottom of the BM window. Any other thoughts/ideas?

Would it be worth the effort (or just wasting my time) to install 7.0.40 (or .41 or .42) since I know they will immediately "connect to localhost", run a few WUs and then try installing 7.0.64? I know 7.0.40, .41 and .42 are buggy, but would running a few WUs through it change a BOINC file or setting that might allow an easier transition to 7.0.64 rather than going directly from 7.0.28? I'm grasping at straws here trying to figure out how to get 7.0.64 to work.

Rich

Can you try making a file called remote_hosts.cfg in the Boinc Data directory, and in it put your host name or internal up address, I think you need to restart Boinc after that.

Claggy

Hey,

I have the exact problem with the 7.0.64(couple previous versions tested too)

The only working solution that worked for the connecting to localhost was to install it as service.
I've tried to install it multiple times with different option compinations...
but nothing worked, in other words every option can be checked, but as service must be in order it to work.

Too bad can't use the GPU cause of it...

Hopefully this helps.

---

System:

Windows 7 Professional x64 SP1
DirectX11
ATI/AMD Catalyst 13.1

Asus M4A79XTD EVO
AMD Phenom II X6 1075T 3,00GH
8GB SDRAM
ATI Radeon HD4870

Can you post the Boinc startup log for one of those failed attempts of starting Boinc 7.0.64, you'll find the log in the following directory (assuming you installed it in the default location):

C:\ProgramData\BOINC

the directory is a hidden directory, so you'll need to unhide it or paste the directory straight into explorer, the file you need is stdoutdae.txt (older entries are in stdoutdae.old), the first 30 lines will do.

Claggy

I had this exact problem. It turns out that I had been running BOINC as a service in the prior versions, and this is now disabled by default in 6.0.64. I didn't notice that at first. Thus my install into an admin account worked fine, but my normal user account couldn't contact the localhost, and would crash.

The unusual thing is that if I tried to re-install BOINC from that non-admin account, using "Run as..." with the correct admin name and password (Triple verified with my local sysadmin standing next to me!), it would say "Invalid user ID or password".

My solution was to de-install BOINC from the Admin account, then re-install with "Run as a service" option selected (You have to go into 'Advanced' on setup to enable that)

Hope this helps someone.

...
stdoutdae.txt file is EMPTY.
...

---

System:

Windows 7 Professional x64 SP1
DirectX11
ATI/AMD Catalyst 13.1

Asus M4A79XTD EVO
AMD Phenom II X6 1075T 3,00GH
8GB SDRAM
ATI Radeon HD4870

...
stdoutdae.txt file is EMPTY.
No .old file found.
...

---

System:

Windows 7 Professional x64 SP1
DirectX11
ATI/AMD Catalyst 13.1

Asus M4A79XTD EVO
AMD Phenom II X6 1075T 3,00GH
8GB SDRAM
ATI Radeon HD4870

...
stdoutdae.txt file is EMPTY.
No .old file found.
...

Does it populate with information when you install Boinc as a service? Is so post that info.

Claggy

for those experiencing the failure to connect problem...

Could you type the following command from a command line in the c:\programdata\boinc directory:

cacls .

and these commands as well:

net localgroup boinc_admins

net localgroup boinc_users

Thanks in advance.

----- Rom

---

----- Rom
BOINC Development Team, U.C. Berkeley
My Blog

And post the output!

You can either copy the output from the command line box, by right-clicking on it and selecting Mark, then use the cursor keys to go up/down/left/right to the text, and while holding SHIFT, to select the text, then press Enter to copy the text to clipboard, before posting it in an answer here (right-click -> Paste, or CTRL + V).

Or you can make the command line post the output to a text file, which you can then open with Notepad.
To do so, do the following:

cacls . > c:\temp\cacls-output.txt

and

net localgroup boinc_admins > c:\temp\boinc-admins.txt

and

net localgroup boinc_users > c:\temp\boinc-users.txt

These commands can be done from a command line, or from the Run-menu.

---

cacls . > c:\temp\cacls-output.txt

and
net localgroup boinc_admins > c:\temp\boinc-admins.txt

and
net localgroup boinc_users > c:\temp\boinc-users.txt

Rom / Jord,

Unfortunately, urgent family matters have me away from my system until mid-next week. I will post the results from the above command lines upon my return.

Rich

And post the output!

You can either copy the output from the command line box, by right-clicking on it and selecting Mark, then use the cursor keys to go up/down/left/right to the text, and while holding SHIFT, to select the text, then press Enter to copy the text to clipboard, before posting it in an answer here (right-click -> Paste, or CTRL + V).

Or you can make the command line post the output to a text file, which you can then open with Notepad.
To do so, do the following:

cacls . > c:\temp\cacls-output.txt

and

net localgroup boinc_admins > c:\temp\boinc-admins.txt

and

net localgroup boinc_users > c:\temp\boinc-users.txt

These commands can be done from a command line, or from the Run-menu.

cacls . (command line output from within E:\BOINC\ProgramData) :


E:\BOINC\ProgramData Enterprise\boinc_projects:(OI)(CI)(DENY)(special access:)


Enterprise\boinc_users:(OI)(CI)(special access:)

READ_CONTROL
FILE_READ_DATA
FILE_READ_EA
FILE_EXECUTE
FILE_READ_ATTRIBUTES

Enterprise\boinc_admins:(OI)(CI)(special access:)

DELETE
READ_CONTROL
SYNCHRONIZE
FILE_GENERIC_READ
FILE_GENERIC_WRITE
FILE_GENERIC_EXECUTE
FILE_READ_DATA
FILE_WRITE_DATA
FILE_APPEND_DATA
FILE_READ_EA
FILE_WRITE_EA
FILE_EXECUTE
FILE_DELETE_CHILD
FILE_READ_ATTRIBUTES
FILE_WRITE_ATTRIBUTES

NT AUTHORITY\SYSTEM:(OI)(CI)F
BUILTIN\Administrators:(OI)(CI)F
NT AUTHORITY\SYSTEM:(OI)(CI)F


net localgroup boinc_admins (command line output from within E:\BOINC\ProgramData) :

Alias name boinc_admins
Comment Accounts in this group can control the BOINC client.

Members

-------------------------------------------------------------------------------
Administrators
Rich
The command completed successfully.


net localgroup boinc_users (command line output from within E:\BOINC\ProgramData) :

Alias name boinc_users
Comment Accounts in this group can monitor the BOINC client.

Members

-------------------------------------------------------------------------------
The command completed successfully.


Rich