bizarre stdoutgui.txt messages (v6.10.58)

Message boards : Questions and problems : bizarre stdoutgui.txt messages (v6.10.58)
Message board moderation

To post messages, you must log in.

AuthorMessage
Professor Ray

Send message
Joined: 31 Mar 08
Posts: 59
United States
Message 36611 - Posted: 27 Jan 2011, 10:15:55 UTC
Last modified: 27 Jan 2011, 10:21:15 UTC

4:20:31 AM: Error: can't open file 'E:\BOINC\\RebootPending.txt' (error 2: the system cannot find the file specified.)

As indicated, the file doesn't exist. However, what does this mean? The aforementioned occurs from either every day to once per week or so. While it occurs indepentantly, it often is seen with the following entrained:

4:53:41 AM: Error: can't open file 'E:\BOINC\\RebootPending.txt' (error 2: the system cannot find the file specified.)
[01/26/11 04:53:42] TRACE [4020]: init_asynch() boinc_socket: 528

[01/26/11 04:53:42] TRACE [4020]: init_asynch() connect: -1

[01/26/11 04:53:42] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:43] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:43] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:43] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:43] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:43] TRACE [4020]: init_poll(): retrying connect: -1

[01/26/11 04:53:44] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:44] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:44] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:44] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:44] TRACE [4020]: init_poll(): retrying connect: -1

[01/26/11 04:53:45] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:45] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:45] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:45] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:45] TRACE [4020]: init_poll(): retrying connect: -1

[01/26/11 04:53:46] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:46] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:46] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:46] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:46] TRACE [4020]: init_poll(): retrying connect: -1

[01/26/11 04:53:47] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:47] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:47] TRACE [4020]: init_poll(): connected to port 31416

[01/26/11 04:53:49] TRACE [4020]: init_poll(): sock = 528

[01/26/11 04:53:49] TRACE [4020]: init_poll(): connected to port 31416

Furthermore, this batch of messages has been recorded:

[11/28/10 11:41:26] TRACE [1252]: init_poll(): connected to port 31416
5:30:20 PM: Error: Memory VFS already contains file 'webexternallink.xpm'!
5:30:20 PM: Error: Memory VFS already contains file 'nvidiaicon.xpm'!
5:30:20 PM: Error: Memory VFS already contains file 'atiicon.xpm'!
5:30:20 PM: Error: Memory VFS already contains file 'multicore.xpm'!
11:02:54 PM: Error: can't open file 'E:\BOINC\\RebootPending.txt' (error 2: the system cannot find the file specified.)
2:06:07 PM: Error: can't open file 'E:\BOINC\\RebootPending.txt' (error 2: the system cannot find the file specified.)
5:45:36 AM: Error: can't open file 'E:\BOINC\\RebootPending.txt' (error 2: the system cannot find the file specified.)
5:49:24 PM: Error: can't open file 'E:\BOINC\\RebootPending.txt' (error 2: the system cannot find the file specified.)
[12/15/10 17:50:12] TRACE [1744]: init_asynch() boinc_socket: 528

...and the whole init.poll() mess repeats itself ad nauseum
ID: 36611 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15480
Netherlands
Message 36614 - Posted: 27 Jan 2011, 13:01:16 UTC - in response to Message 36611.  

4:20:31 AM: Error: can't open file 'E:\BOINC\\RebootPending.txt' (error 2: the system cannot find the file specified.)

As indicated, the file doesn't exist. However, what does this mean? The aforementioned occurs from either every day to once per week or so.

It should occur every time you start BOINC (after an exit). As it will happen at the start of BOINC. It's the reboot-check for clean installations and upgrade from BOINC 5 and prior installations.

If the file exists, the system needs to be rebooted first (to allow for the limited accounts BOINC makes to be activated by Windows). As long as the file doesn't exist, ignore its non-existence and write that line into the stdoutgui.txt file.

Most of the lines written into this file can easily be ignored. As long as your BOINC Manager works, as long as it doesn't crash any time you look at it... there's plenty more obscure things being written into other log files for BOINC. They aren't of interest to you or me, unless you're a (partial) developer of (any part) of the program, who finds pleasure in debugging the messages.
ID: 36614 · Report as offensive
Professor Ray

Send message
Joined: 31 Mar 08
Posts: 59
United States
Message 36625 - Posted: 27 Jan 2011, 22:01:01 UTC - in response to Message 36614.  

Roger (that).
ID: 36625 · Report as offensive

Message boards : Questions and problems : bizarre stdoutgui.txt messages (v6.10.58)

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.