Error updating stats files, ... = Error reading current client.cfg username

[07:45:26] GPU 0 completed a WU successfully
[07:45:26] Error updating stats files, source client = GPU0
[07:45:26] Deleted WU on GPU0
[07:45:26] Starting GPU 0
[07:45:26] Error reading current client.cfg username. Client: GPU0
[07:45:26] Started new WU on GPU0
[07:49:10] --------------------------------------------------
[07:49:10] FAH GPU Tracker v3.46 Startup

Then it did this on every unit ever since, (been a week)

[11:41:24] GPU 0 completed a WU successfully
[11:41:24] Deleted WU on GPU0
[11:41:24] Starting GPU 0
[11:41:24] Error reading current client.cfg username. Client: GPU0
[11:41:24] Started new WU on GPU0

The cfg file content :

Code:

[http]active=no[settings]machineid=1local=8

(it's fixed / just reporting)

It happened again, 3.52

client.cfg

Code:

[http]
active=no

[settings]
machineid=1
local=74


I had expected this could fix it :
Stop all
change setting (team)
start
(fail)

then maybe :
stop all
delete client.cfg
start
(fail, I'm now anonymous)

All permutation of these,:
delete client
change setting
restart gputracker
(fail)
Now my clients start with
"User name [Anonymous]?"

At what point does FAHtracker apply the user/team settings to the clients ?

Transisto wrote:It happened again, 3.52

client.cfg

Code:

[http]
active=no

[settings]
machineid=1
local=74


I had expected this could fix it :
Stop all
change setting (team)
start
(fail)

then maybe :
stop all
delete client.cfg
start
(fail, I'm now anonymous)

All permutation of these,:
delete client
change setting
restart gputracker
(fail)
Now my clients start with
"User name [Anonymous]?"

At what point does FAHtracker apply the user/team settings to the clients ?

Ok, to clarify how the Tracker deals with client.cfg:

1. During initial setup the full config process (change advanced setting = yes) is used to create the full client.cfg.

2. When a WU starts, the Tracker checks the current name/team/passkey. If they don't match the currently set values, it runs the client in -configonly and changes the settings. However, if the client.cfg file can't be read or the format is invalid, the Tracker will log an error and start the client without modifying the config.

The Tracker can't correct client.cfg errors automatically. I have yet to reproduce a situation where the client.cfg files become unusable without manually editing them.