Manager: Odd messages during successful autologin

[TheAspens]

During a successful auto-login there were some messages that were confusing during the startup and attach sequence:

Tue 14 Nov 2017 09:17:16 PM CST |  | Read installer filename file
Tue 14 Nov 2017 09:17:16 PM CST |  | Doing token lookup RPC to Localhost@Home
Tue 14 Nov 2017 09:17:16 PM CST |  | Setting up GUI RPC socket
Tue 14 Nov 2017 09:17:16 PM CST |  | Checking presence of 0 project files
Tue 14 Nov 2017 09:17:16 PM CST |  | This computer is not attached to any projects
Tue 14 Nov 2017 09:17:16 PM CST |  | Visit http://boinc.berkeley.edu for instructions
Tue 14 Nov 2017 09:17:18 PM CST |  | Running CPU benchmarks
Tue 14 Nov 2017 09:17:18 PM CST |  | Suspending computation - CPU benchmarks in progress
Tue 14 Nov 2017 09:17:49 PM CST |  | Benchmark results:
Tue 14 Nov 2017 09:17:49 PM CST |  | Number of CPUs: 8
Tue 14 Nov 2017 09:17:49 PM CST |  | 3812 floating point MIPS (Whetstone) per CPU
Tue 14 Nov 2017 09:17:49 PM CST |  | 13972 integer MIPS (Dhrystone) per CPU
Tue 14 Nov 2017 09:17:50 PM CST |  | Resuming computation
Tue 14 Nov 2017 09:17:52 PM CST | Localhost@Home | Master file download succeeded
Tue 14 Nov 2017 09:17:57 PM CST | Localhost@Home | Sending scheduler request: Project initialization.
Tue 14 Nov 2017 09:17:57 PM CST | Localhost@Home | Requesting new tasks for CPU
Tue 14 Nov 2017 09:17:58 PM CST | boincserver | Scheduler request completed: got 0 new tasks
Tue 14 Nov 2017 09:17:58 PM CST | boincserver | Project has no tasks available

Specifically the log messages about "This computer is not attached to any projects". However, the popup to attach to a project did not render (as it shouldn't because it was an successful auto attach). The messages are misleading and should be examined.

[CharlieFenton]

I tested this with a Mac installer built from the latest code in the branch. Since the account_data.txt file downloaded by the test project now has a project ID of 100, but there is no project with this ID in the all_projects_list.xml file, the auto-attach failed and the Manager displayed the Attach Wizard, as it should. However, the messages in the Event Lof had several problems:

Wed Nov 15 01:29:31 2017 |  | Read installer filename file
Wed Nov 15 01:29:31 2017 |  | Unknown project ID: 100
Wed Nov 15 01:29:31 2017 |  | Setting up GUI RPC socket
Wed Nov 15 01:29:31 2017 |  | Checking presence of 0 project files
Wed Nov 15 01:29:31 2017 |  | This computer is not attached to any projects
Wed Nov 15 01:29:31 2017 |  | Visit http://boinc.berkeley.edu for instructions

This should say Read account_data file or Read account data file, not Read filename file
Since the Attach Wizard was displayed, it should not tell the user to Visit http://boinc.berkeley.edu for instructions

[CharlieFenton]

I am now seeing an additional misleading / incorrect message:

16-Nov-2017 02:12:00 [---] Data directory: /Library/Application Support/BOINC Data
16-Nov-2017 02:12:00 [---] Invalid account filename: account_data.txt
16-Nov-2017 02:12:00 [---] CUDA: NVIDIA GPU 0: GeForce 8800 GT (driver version 6.0.51, 

Apparently the is_account_file() in the client [called from parse_account_files()] thinks that the account_data.txt file is a file representing a specific project account, because it checks all files whose name starts with "account_". But since its extension is not ".xml" it calls bad_account_filename().

[davidpanderson]

I changed the filename

[RichardHaselgrove]

@SETIguy - this is open for review and testing prior to v7.10 branch, dependent on successful deployment of server code to SETI production server - possibly due today?

[TheAspens]

@RichardHaselgrove and @davidpanderson - can we close this?

[RichardHaselgrove]

Strictly speaking, we need to do a final test when we have a production installer live on SETI with the right file name and deploying a production client. But that's just for confirmation - my private build test passed. We can always re-open it if things go pear-shaped.

[SETIguy]

We need some work to test it with, which is scarce today, unless we're sure everything else in the BOINC clients is unaffected by these changes. I'll talk to David about the procedure for testing auto attach, and what could possibly go wrong.

…

On Mon, Feb 5, 2018 at 8:17 AM, RichardHaselgrove ***@***.***> wrote: Strictly speaking, we need to do a final test when we have a production installer live on SETI with the right file name and deploying a production client. But that's just for confirmation - my private build test passed. We can always re-open it if things go pear-shaped. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2238 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKXcsq_9Ee6XgCD2nedwLwaay1BVMhzgks5tRymOgaJpZM4QeVrL> .

-- Eric Korpela korpela@ssl.berkeley.edu AST:7731^29u18e3

[RichardHaselgrove]

I faked the auto-attach with a home-build and file rename on 25 January, and that home-build client has been running in production mode continuously since 26 January - no faults observed. But I haven't tested it as if it were a release build.

[AenBleidd]

Is it still an issue?