Page 1 of 2

Log rotated, but the log does not continue or a new one opens

Posted: Tue Apr 18, 2023 8:29 pm
by Lukinator
Hello, I noticed in the latest beta that the log doesn't go any further when a new day begins, the log is cut off and you don't get any more information about the work units at least above the interface, I've attached an example here . Is that normal or is it a bug?

Code: Select all

*********************** Log Started 2023-04-17T12:42:54Z ***********************
12:42:54:I1:*********************** Folding@home Client ***********************
12:42:54:I1:    Version: 8.1.17
12:42:54:I1:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
12:42:54:I1:        Org: foldingathome.org
12:42:54:I1:  Copyright: 2023 foldingathome.org
12:42:54:I1:   Homepage: https://foldingathome.org/
12:42:54:I1:    License: https://www.gnu.org/licenses/gpl-3.0.txt
12:42:54:I1:       Date: Apr 14 2023
12:42:54:I1:       Time: 16:26:21
12:42:54:I1:   Compiler: Visual C++
12:42:54:I1:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
12:42:54:I1:   Platform: win32 10
12:42:54:I1:       Bits: 64
12:42:54:I1:       Mode: Release
12:42:54:I1:       Args: --open-web-control
12:42:54:I1:     Config: R:\FAHClient\config.xml
12:42:54:I1:****************************** CBang ******************************
12:42:54:I1:    Version: 1.7.2
12:42:54:I1:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
12:42:54:I1:        Org: Cauldron Development LLC
12:42:54:I1:  Copyright: Cauldron Development LLC, 2003-2023
12:42:54:I1:   Homepage: https://cauldrondevelopment.com/
12:42:54:I1:    License: GPL 2+
12:42:54:I1:       Date: Feb 7 2023
12:42:54:I1:       Time: 20:33:41
12:42:54:I1:   Compiler: Visual C++
12:42:54:I1:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
12:42:54:I1:   Platform: win32 10
12:42:54:I1:       Bits: 64
12:42:54:I1:       Mode: Release
12:42:54:I1:***************************** System ******************************
12:42:54:I1:        CPU: AMD EPYC 7502P 32-Core Processor
12:42:54:I1:     CPU ID: AuthenticAMD Family 23 Model 49 Stepping 0
12:42:54:I1:       CPUs: 64
12:42:54:I1:     Memory: 127.87GiB
12:42:54:I1:Free Memory: 99.06GiB
12:42:54:I1:    Threads: WINDOWS_THREADS
12:42:54:I1: OS Version: 6.2
12:42:54:I1:Has Battery: false
12:42:54:I1: On Battery: false
12:42:54:I1: UTC Offset: 2
12:42:54:I1:        PID: 4064
12:42:54:I1:        CWD: R:\FAHClient
12:42:54:I1:       Exec: C:\Program Files\FAHClient\FAHClient.exe
12:42:54:I1:*******************************************************************
12:42:54:I2:<config/>
12:42:54:I1:Opening Database
12:42:54:I1:Listening for HTTP on 127.0.0.1:7396
12:42:54:I3:id = sWx9hwUXdgx9yfamemK2gxdB6qhvEdFPiB9cX73Edug=
12:42:54:I3:Loading work unit 23 to group '' with ID uQVGa2gPKyb7Il_ZxIavT7lWzYXHPzDC5ym6p3sZxtM
12:42:54:I3:Loaded 1 wus.
12:42:54:I1:Started Windows systray control
12:42:54:E :Exception: clGetPlatformIDs() returned -1001
12:42:54:E :Exception: Failed to open dynamic library 'nvcuda.dll': Das angegebene Modul wurde nicht gefunden.
12:42:59:I1:Loaded cores/fahcore-a8-win-64bit-avx2_256-0.0.12/FahCore_a8.exe
12:42:59:I3::WU23:Running FahCore: R:\FAHClient\cores/fahcore-a8-win-64bit-avx2_256-0.0.12/FahCore_a8.exe -dir uQVGa2gPKyb7Il_ZxIavT7lWzYXHPzDC5ym6p3sZxtM -suffix 01 -version 8.1.17 -lifeline 4064 -np 64
12:42:59:I3::WU23:Started FahCore on PID 11296
12:42:59:I1::WU23:*********************** Log Started 2023-04-17T12:42:59Z ***********************
12:42:59:I1::WU23:************************** Gromacs Folding@home Core ***************************
12:42:59:I1::WU23:       Core: Gromacs
12:42:59:I1::WU23:       Type: 0xa8
12:42:59:I1::WU23:    Version: 0.0.12
12:42:59:I1::WU23:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
12:42:59:I1::WU23:  Copyright: 2020 foldingathome.org
12:42:59:I1::WU23:   Homepage: https://foldingathome.org/
12:42:59:I1::WU23:       Date: Jan 16 2021
12:42:59:I1::WU23:       Time: 12:29:40
12:42:59:I1::WU23:   Revision: c5816759c404e4b65f9f364c3d1ef554a67c4225
12:42:59:I1::WU23:     Branch: master
12:42:59:I1::WU23:   Compiler: Visual C++ 2019 16.7
12:42:59:I1::WU23:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
12:42:59:I1::WU23:   Platform: win32 10
12:42:59:I1::WU23:       Bits: 64
12:42:59:I1::WU23:       Mode: Release
12:42:59:I1::WU23:       SIMD: avx2_256
12:42:59:I1::WU23:     OpenMP: ON
12:42:59:I1::WU23:       CUDA: OFF
12:42:59:I1::WU23:       Args: -dir uQVGa2gPKyb7Il_ZxIavT7lWzYXHPzDC5ym6p3sZxtM -suffix 01
12:42:59:I1::WU23:             -version 8.1.17 -lifeline 4064 -np 64
12:42:59:I1::WU23:************************************ libFAH ************************************
12:42:59:I1::WU23:       Date: Jan 16 2021
12:42:59:I1::WU23:       Time: 11:24:13
12:42:59:I1::WU23:   Revision: c5816759c404e4b65f9f364c3d1ef554a67c4225
12:42:59:I1::WU23:     Branch: master
12:42:59:I1::WU23:   Compiler: Visual C++ 2019 16.7
12:42:59:I1::WU23:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
12:42:59:I1::WU23:   Platform: win32 10
12:42:59:I1::WU23:       Bits: 64
12:42:59:I1::WU23:       Mode: Release
12:42:59:I1::WU23:************************************ CBang *************************************
12:42:59:I1::WU23:       Date: Jan 16 2021
12:42:59:I1::WU23:       Time: 11:23:53
12:42:59:I1::WU23:   Revision: c5816759c404e4b65f9f364c3d1ef554a67c4225
12:42:59:I1::WU23:     Branch: master
12:42:59:I1::WU23:   Compiler: Visual C++ 2019 16.7
12:42:59:I1::WU23:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
12:42:59:I1::WU23:   Platform: win32 10
12:42:59:I1::WU23:       Bits: 64
12:42:59:I1::WU23:       Mode: Release
12:42:59:I1::WU23:************************************ System ************************************
12:42:59:I1::WU23:        CPU: AMD EPYC 7502P 32-Core Processor
12:42:59:I1::WU23:     CPU ID: AuthenticAMD Family 23 Model 49 Stepping 0
12:42:59:I1::WU23:       CPUs: 64
12:42:59:I1::WU23:     Memory: 127.87GiB
12:42:59:I1::WU23:Free Memory: 98.96GiB
12:42:59:I1::WU23:    Threads: WINDOWS_THREADS
12:42:59:I1::WU23: OS Version: 6.2
12:42:59:I1::WU23:Has Battery: false
12:42:59:I1::WU23: On Battery: false
12:42:59:I1::WU23: UTC Offset: 2
12:42:59:I1::WU23:        PID: 11296
12:42:59:I1::WU23:        CWD: R:\FAHClient\work
12:42:59:I1::WU23:********************************************************************************
12:42:59:I1::WU23:Project: 18475 (Run 142, Clone 0, Gen 5)
12:42:59:I1::WU23:Unit: 0x00000000000000000000000000000000
12:42:59:I1::WU23:Digital signatures verified
12:42:59:I1::WU23:Calling: mdrun -c frame5.gro -s frame5.tpr -x frame5.xtc -cpi state.cpt -cpt 5 -nt 64 -ntmpi 1
12:42:59:I1::WU23:Steps: first=50000000 total=60000000
12:43:06:I1::WU23:Completed 206813 out of 10000000 steps (2%)
13:00:54:I1::WU23:Completed 300000 out of 10000000 steps (3%)
13:20:07:I1::WU23:Completed 400000 out of 10000000 steps (4%)
13:39:23:I1::WU23:Completed 500000 out of 10000000 steps (5%)
13:58:37:I1::WU23:Completed 600000 out of 10000000 steps (6%)
14:17:35:I1::WU23:Completed 700000 out of 10000000 steps (7%)
14:36:47:I1::WU23:Completed 800000 out of 10000000 steps (8%)
14:56:02:I1::WU23:Completed 900000 out of 10000000 steps (9%)
15:15:11:I1::WU23:Completed 1000000 out of 10000000 steps (10%)
15:34:26:I1::WU23:Completed 1100000 out of 10000000 steps (11%)
15:53:19:I1::WU23:Completed 1200000 out of 10000000 steps (12%)
16:12:27:I1::WU23:Completed 1300000 out of 10000000 steps (13%)
16:31:39:I1::WU23:Completed 1400000 out of 10000000 steps (14%)
16:50:46:I1::WU23:Completed 1500000 out of 10000000 steps (15%)
17:10:05:I1::WU23:Completed 1600000 out of 10000000 steps (16%)
17:29:15:I1::WU23:Completed 1700000 out of 10000000 steps (17%)
17:48:32:I1::WU23:Completed 1800000 out of 10000000 steps (18%)
18:07:49:I1::WU23:Completed 1900000 out of 10000000 steps (19%)
18:27:02:I1::WU23:Completed 2000000 out of 10000000 steps (20%)
18:46:14:I1::WU23:Completed 2100000 out of 10000000 steps (21%)
19:05:23:I1::WU23:Completed 2200000 out of 10000000 steps (22%)
19:24:37:I1::WU23:Completed 2300000 out of 10000000 steps (23%)
19:43:25:I1::WU23:Completed 2400000 out of 10000000 steps (24%)
20:02:36:I1::WU23:Completed 2500000 out of 10000000 steps (25%)
20:21:45:I1::WU23:Completed 2600000 out of 10000000 steps (26%)
20:40:55:I1::WU23:Completed 2700000 out of 10000000 steps (27%)
21:00:12:I1::WU23:Completed 2800000 out of 10000000 steps (28%)
21:19:19:I1::WU23:Completed 2900000 out of 10000000 steps (29%)
21:38:29:I1::WU23:Completed 3000000 out of 10000000 steps (30%)
21:57:43:I1::WU23:Completed 3100000 out of 10000000 steps (31%)
22:16:53:I1::WU23:Completed 3200000 out of 10000000 steps (32%)
22:35:59:I1::WU23:Completed 3300000 out of 10000000 steps (33%)
22:55:15:I1::WU23:Completed 3400000 out of 10000000 steps (34%)
23:14:21:I1::WU23:Completed 3500000 out of 10000000 steps (35%)
23:33:34:I1::WU23:Completed 3600000 out of 10000000 steps (36%)
23:52:34:I1::WU23:Completed 3700000 out of 10000000 steps (37%)
*********************** Log Rotated 2023-04-18T00:11:49Z ***********************

Re: Log rotated, but the log does not continue or a new one opens

Posted: Wed Apr 19, 2023 9:08 am
by calxalot
It looks normal to me.
Was a new log.txt not created?

Re: Log rotated, but the log does not continue or a new one opens

Posted: Wed Apr 19, 2023 9:21 am
by Lukinator
No, did not create a new one.
Always had to restart the client for it to work again.

Re: Log rotated, but the log does not continue or a new one opens

Posted: Wed Apr 19, 2023 9:34 am
by calxalot
Have you tried v8.1.18 ?

Re: Log rotated, but the log does not continue or a new one opens

Posted: Thu Apr 20, 2023 1:29 am
by Lukinator
Yes, I tried it, the problem persists.

Re: Log rotated, but the log does not continue or a new one opens

Posted: Thu Apr 20, 2023 4:29 am
by calxalot
I see you're using R:\FAHClient.
Is it possible there is a permissions problem?

Just guessing. I am not a Windows expert.

Re: Log rotated, but the log does not continue or a new one opens

Posted: Thu Apr 20, 2023 10:05 am
by Lazvon
Unless they have a TON of local disks, certainly sounds like NAS (Network Attached Storage) likely using SMB/CIFS. Do you have “create file” rights? Maybe “rename file” which on a Synology NAS would be “Delete” permissions on the containing folder I believe from a quick Google.

Re: Log rotated, but the log does not continue or a new one opens

Posted: Thu Apr 20, 2023 10:36 am
by Lukinator
No, actually I don't have any permissions problems, since otherwise the folding would not work, I have now reset the data directory to the standard. Let's see what that brings.

And no, I'm not using it on a NAS.

Re: Log rotated, but the log does not continue or a new one opens

Posted: Fri Apr 21, 2023 12:48 am
by Lukinator
So have now tried it in the default data directory and still have the problem, if it closes the client log from the day, it doesn't open a new log for the next day unless you restart the client.

Re: Log rotated, but the log does not continue or a new one opens

Posted: Fri Apr 21, 2023 1:08 am
by calxalot
Please install the debug build and look for errors in the log.

Re: Log rotated, but the log does not continue or a new one opens

Posted: Sat Apr 22, 2023 9:45 am
by Lukinator
So I installed the debug build and checked the log for errors, but didn't find any errors why no new log is created. I am attaching the log here. Due to the length, I uploaded the log via Google Drive, here is the link: https://drive.google.com/file/d/1wZt9XI ... sp=sharing

Re: Log rotated, but the log does not continue or a new one opens

Posted: Sat Apr 22, 2023 10:22 am
by calxalot
For now, you can disable the periodic rotation with this line in config.xml:

Code: Select all

<log-rotate-period v='0'/>
If you don't have config.xml in the fah data directory, create it with the following:

Code: Select all

<config>
  <log-rotate-period v='0'/>
</config>
You will need to restart the client for it to take effect.

Re: Log rotated, but the log does not continue or a new one opens

Posted: Sat Apr 22, 2023 8:15 pm
by Peter_Hucker
I am getting a similar problem. On my fastest host, one GPU and a 24 core CPU, I have the current log at "C:\ProgramData\FAHClient\log.txt" with the last line "*********************** Log Rotated 2023-04-20T00:01:40Z ***********************"

In the logs folder under there, the latest file is named "log-20230419-210035"

Does this mean at 20230419-210035, a log rotation took place, moving a file into the logs folder, and it started the current one. But at 2023-04-20T00:01:40Z it tried to rotate but failed?

Re: Log rotated, but the log does not continue or a new one opens

Posted: Sat Apr 22, 2023 10:05 pm
by calxalot
I believe that line indicates a log rotation was started. It is not a failure message. Could be clearer.

Sequence is something like
- print log rotate line
- close log
- move and rename log file with timestamp
- open new log.txt

The file used to be moved first, but Windows didn’t like an open file being moved.

Re: Log rotated, but the log does not continue or a new one opens

Posted: Tue Apr 25, 2023 11:35 pm
by Lukinator
Okay thanks. It worked. But it's still stupid that the log rotate doesn't create a new log.