Hi all,

I tried to update to 7.12 from 7.8, but boinc.exe would not open the manager port 31416. Here's what I did:

Set all projects to No New Tasks, and waited for the all WU's to be reported.
Shutdown 7.8 and installed 7.12 with VBOX over older the version. Manager failed to connect.
Rebooted windows, but the manager was still not connecting.
Checked and recreated firewall rules for BOINC.EXE, BOINCMGR.EXE and that port 31416 was open for inbound TCP & UDP.
Added the BOINC program folder to the Avira Antivirus exception list.
Removed 7.12 with VBOX, rebooted and then reinstalled.
Removed 7.12 with VBOX, rebooted and then installed 7.12 without VBOX then rebooted again.
Checked NETSTAT -B and Resource Monitor and saw BOINC.EXE had not opened any listening ports.
Rechecked firewall rules as above, but manager would still not connect.
Removed Installed 7.10 without VBOX, and manager connected within seconds. No reboot was needed.
Set one project to Allow New Tasks, and have 24 WU's in the queue.

I'm waiting for the new tasks to complete, before I try 7.12 again. Are there any logs/flags that will help diagnose the issue if it returns?

Thanks,
Dave

The one thing I'm not seeing in your list is if you checked with Task Manager that boinc.exe is actually running.

The logs are in stdoutdae.txt and stderrdae.txt files in BOINC's data directory (usually C:\ProgramData\BOINC, you can check the location with the previous, working version from Manager's Event Log).

Check for messages like this in stdoutdae.txt

13-Jul-2018 23:02:10 [---] Setting up project and slot directories
13-Jul-2018 23:02:10 [---] Checking active tasks
13-Jul-2018 23:02:10 [---] Setting up GUI RPC socket
13-Jul-2018 23:02:10 [---] Checking presence of 582 project files
13-Jul-2018 23:02:10 Initialization completed

If the client gets past Setting up GUI RPC socket then, as far as the client knows, the socket is open. If there is an error message instead copy-paste it here.

If boinc.exe is not running then check stderrdae.txt for crash log.

Hello,

Just reinstalled 7.12, and getting the same issue. BOINC.exe listes in task manager, as it was in the previous testing stages above.

Here is the contents of the STDOUTDAE .TXT log file:

28-Jul-2018 15:03:04 [---] cc_config.xml not found - using defaults
28-Jul-2018 15:03:04 [---] Starting BOINC client version 7.12.1 for windows_x86_64
28-Jul-2018 15:03:04 [---] log flags: file_xfer, sched_ops, task
28-Jul-2018 15:03:04 [---] Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
28-Jul-2018 15:03:04 [---] Data directory: C:\ProgramData\BOINC
28-Jul-2018 15:03:04 [---] Running under account ukdav
28-Jul-2018 15:03:05 [---] CUDA: NVIDIA GPU 0: GeForce GTX 860M (driver version 382.05, CUDA version 8.0, compute capability 5.0, 2048MB, 1692MB available, 1305 GFLOPS peak)
28-Jul-2018 15:03:05 [---] OpenCL: NVIDIA GPU 0: GeForce GTX 860M (driver version 382.05, device version OpenCL 1.2 CUDA, 2048MB, 1692MB available, 1305 GFLOPS peak)
28-Jul-2018 15:03:05 [---] OpenCL: Intel GPU 0: Intel(R) HD Graphics 4600 (driver version 20.19.15.4835, device version OpenCL 1.2, 1630MB, 1630MB available, 192 GFLOPS peak)
28-Jul-2018 15:03:05 [---] OpenCL CPU: Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 5.2.0.10094, device version OpenCL 1.2 (Build 10094))
28-Jul-2018 15:03:05 [---] Creating new client state file

The STDERRDAE.TXT file is empty.

Thanks,
Dave

I've just installed 7.12.1 on a completely bare Windows 10 1803. It only has Firefox installed, no anti virus or other anti malware. Just Windows firewall.
It started without trouble.

One thing I see in your log:

28-Jul-2018 15:03:05 [---] Creating new client state file

That only shows when you didn't have a client state file before, thus an empty data directory. Did you delete the data directory prior to reinstalling BOINC? Or did you use a different data directory before?

---

Do you have or have you had Windows Subsystem for Linux installed? If you don't have no need to install it.

If you do have WSL installed could you check if boinc.exe has started any WSL processes? Probably easiest to check with Process Explorer so that you can see the process tree.

Hello,

For this re-install, I did delete the contents of the C:\ProgramData\BOINC folder. It was recommended in another thread when troubleshooting.

Regards,
Dave

Hello,

I do use WSL with Ubuntu, and it's never been a problem with earlier versions of BOINC.

Regards,
Dave

WSL detection is new in 7.12. The way WSL distros are installed changed in Fall Creators Update. Was that Ubuntu you have installed before or after FCU?

Would you be willing to run a debug build or two? I think that's the fastest way to figure out what's going on.

Hello,

Thanks for the help, V7.12 now works since removing WSL. I no longer need it installed.

Regards,
Dave

Would you be willing to run a debug build or two? I think that's the fastest way to figure out what's going on.

Yes, I can compile and run - though the machine which is Windows-10-capable usually runs Windows 7. What are you suspecting may be the problem? (I have FCU loaded already, so reverting would be a faff)

Well, this is my startup (bare test machine) for v7.12.1 with WSL - ran Windows update to get the July cumulative update before running.

30/07/2018 18:32:48 | | cc_config.xml not found - using defaults
30/07/2018 18:32:48 | | Starting BOINC client version 7.12.1 for windows_x86_64
30/07/2018 18:32:48 | | log flags: file_xfer, sched_ops, task
30/07/2018 18:32:48 | | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
30/07/2018 18:32:48 | | Data directory: C:\ProgramData\BOINC
30/07/2018 18:32:48 | | Running under account Richard Haselgrove
30/07/2018 18:32:48 | | CUDA: NVIDIA GPU 0: GeForce GTX 1050 Ti (driver version 388.13, CUDA version 9.1, compute capability 6.1, 4096MB, 3386MB available, 2138 GFLOPS peak)
30/07/2018 18:32:48 | | Version change (7.11.0 -> 7.12.1)
30/07/2018 18:32:50 | | Host name: Beverly
30/07/2018 18:32:50 | | Processor: 4 GenuineIntel Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz [Family 6 Model 94 Stepping 3]
30/07/2018 18:32:50 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 vmx smx tm2 pbe fsgsbase bmi1 hle smep bmi2
30/07/2018 18:32:50 | | OS: Microsoft Windows 10: Professional x64 Edition, (10.00.17134.00)
30/07/2018 18:32:50 | | Memory: 7.93 GB physical, 9.18 GB virtual
30/07/2018 18:32:50 | | Disk: 255.62 GB total, 210.31 GB free
30/07/2018 18:32:50 | | Local time is UTC +1 hours
30/07/2018 18:32:50 | | WSL detected:
30/07/2018 18:32:50 | | [Ubuntu] (default): Linux Ubuntu (Ubuntu 16.04.4 LTS [4.4.0-17134-Microsoft])
30/07/2018 18:32:50 | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 8508571; resource share 100
30/07/2018 18:32:50 | | General prefs: from http://einstein.phys.uwm.edu/ (last modified 31-Mar-2017 13:02:59)
30/07/2018 18:32:50 | | Host location: none
30/07/2018 18:32:50 | | General prefs: using your defaults
30/07/2018 18:32:50 | | Reading preferences override file
30/07/2018 18:32:50 | | Preferences:
30/07/2018 18:32:50 | | max memory usage when active: 4058.20 MB
30/07/2018 18:32:50 | | max memory usage when idle: 7304.76 MB
30/07/2018 18:32:50 | | max disk usage: 210.22 GB
30/07/2018 18:32:50 | | don't use GPU while active
30/07/2018 18:32:50 | | suspend work if non-BOINC CPU load exceeds 25%
30/07/2018 18:32:50 | | (to change preferences, visit a project web site or select Preferences in the Manager)
30/07/2018 18:32:50 | | Setting up project and slot directories
30/07/2018 18:32:50 | | Checking active tasks
30/07/2018 18:32:50 | | Setting up GUI RPC socket
30/07/2018 18:32:50 | | Checking presence of 14 project files
30/07/2018 18:32:50 | | Running CPU benchmarks
30/07/2018 18:32:50 | | Suspending computation - CPU benchmarks in progress
30/07/2018 18:33:21 | | Benchmark results:
30/07/2018 18:33:21 | | Number of CPUs: 4
30/07/2018 18:33:21 | | 4081 floating point MIPS (Whetstone) per CPU
30/07/2018 18:33:21 | | 14202 integer MIPS (Dhrystone) per CPU
30/07/2018 18:33:58 | SETI@home | work fetch resumed by user
30/07/2018 18:34:01 | SETI@home | Sending scheduler request: To fetch work.
30/07/2018 18:34:01 | SETI@home | Requesting new tasks for NVIDIA GPU
30/07/2018 18:34:03 | SETI@home | Scheduler request completed: got 1 new tasks
30/07/2018 18:34:05 | SETI@home | Started download of blc03_2bit_guppi_58227_15036_HIP66840_0040.32359.0.22.45.170.vlar
30/07/2018 18:34:06 | SETI@home | work fetch suspended by user
30/07/2018 18:34:08 | SETI@home | Finished download of blc03_2bit_guppi_58227_15036_HIP66840_0040.32359.0.22.45.170.vlar
30/07/2018 18:34:08 | SETI@home | Starting task blc03_2bit_guppi_58227_15036_HIP66840_0040.32359.0.22.45.170.vlar_0

Just missing an OpenCL driver because I haven't run the machine with the intel_gpu active yet.

ukdave74 wrote:

V7.12 now works since removing WSL. I no longer need it installed.

Well, bummer. I mean, it's great that 7.12 works now but in order to find out why the client hung we need a client that, well, hangs.

If you are still around please tell if you had Ubuntu installed before or after FCU?


Richard wrote:

Yes, I can compile and run - though the machine which is Windows-10-capable usually runs Windows 7. What are you suspecting may be the problem? (I have FCU loaded already, so reverting would be a faff)

I was thinking making a debug build, Dave running it and once the client hangs Dave making a dump file (via Task Manager). The dump file could then be opened in Visual Studio to see what the client was doing and see the state of variables. Or alternatively, adding a bunch of printf's before and after functions calls to log where the client is and to log parameters and return values. A possible trouble point is read_from_pipe in hostinfo_wsl.cpp which might be an infinite loop if WSL decides to misbehave.

I have Windows 10 machine updated to 1803 and WSL detection seems to be working fine. This is my daily driver so I'm not exactly enthusiastic about doing a factory reset to test WSL installed before FCU :(

I have Windows 10 machine updated to 1803 and WSL detection seems to be working fine. This is my daily driver so I'm not exactly enthusiastic about doing a factory reset to test WSL installed before FCU :(

If it's critical, I can wipe that test install and start again - I prefer to run the W7 boot for normal work. But give me a few days to finish recovering from the workshop first...

Well, the client shouldn't hang but I don't know how critical it is. Only one report and another maybe so far.

Should really open an issue but uhh... that feels like too much work right now...