Good morning, greeting to this interesting and groundbreaking community!
Yesterday I decided to become an operator. After several reboots I managed todynchonize to 100% (at least that’s what the console shows) my last block is 16340 which is strange because I’ve seen on screenshots from other users much higher numbers.
Currently I am getting messages all the time like on the attached screen saying that:
[TestNet:Transaction Manager]: Max nr. of my identities has been reached. Cycling back..
[TestNet:Transaction Manager]: Can't generate block at height secured by an Obligatory Checkpoint (16341)
[TestNet:Transaction Manager]: Max nr. of my identities has been reached. Cycling back..
[TestNet:Transaction Manager]: Can't generate block at height secured by an Obligatory Checkpoint (16341)
[TestNet:Transaction Manager]: Max nr. of my identities has been reached. Cycling back..
[TestNet:Transaction Manager]: Can't generate block at height secured by an Obligatory Checkpoint (16341)
[TestNet:Transaction Manager]: Max nr. of my identities has been reached. Cycling back..
[TestNet:Transaction Manager]: Can't generate block at height secured by an Obligatory Checkpoint (16341)
[TestNet:Transaction Manager]: Max nr. of my identities has been reached. Cycling back..
[TestNet:Transaction Manager]: Can't generate block at height secured by an Obligatory Checkpoint (16341)
[TestNet:Transaction Manager]: Max nr. of my identities has been reached. Cycling back..
[TestNet:Transaction Manager]: Can't generate block at height secured by an Obligatory Checkpoint (16341)
[TestNet:Transaction Manager]: Max nr. of my identities has been reached. Cycling back..
|-[ Events-View [BH]:16340 [Sync]: 100% [BQ]:0 [BPM]:0 [APM]:0 [Vitals]: Warnings ]-|
What should I have done? I have the addition of automatically unblocked ports for GridNet in FireWall (I also added 443 manually, but that didn’t change anything). I will point out that I am operating on an Nvidia GeForece RTX 4090 and an AMD Ryzen 9 7900x3d
thank you very much for any help on this issue
Once I check warning I’ve got sometinh like this
[ GridScript-View (#) Activated. Status: Ready
$ warnings
[1] [Nov 15 11:54:09 2023]: DSM idle for too long. [Source: Local System]
[2] [Nov 15 11:56:32 2023]: DSM idle for too long. [Source: Local System]
[3] [Nov 15 11:53:47 2023]: DSM idle for too long. [Source: Local System]
[4] [Nov 15 11:54:31 2023]: DSM idle for too long. [Source: Local System]
[5] [Nov 15 11:55:48 2023]: DSM idle for too long. [Source: Local System]
[6] [Nov 15 11:53:58 2023]: DSM idle for too long. [Source: Local System]
[7] [Nov 15 11:57:05 2023]: DSM idle for too long. [Source: Local System]
[8] [Nov 15 11:55:37 2023]: DSM idle for too long. [Source: Local System]
[9] [Nov 15 11:58:22 2023]: DSM idle for too long. [Source: Local System]
[10] [Nov 15 11:55:15 2023]: DSM idle for too long. [Source: Local System]
[11] [Nov 15 11:56:43 2023]: DSM idle for too long. [Source: Local System]
[12] [Nov 15 11:54:53 2023]: DSM idle for too long. [Source: Local System]
[13] [Nov 15 11:53:36 2023]: DSM idle for too long. [Source: Local System]
[14] [Nov 15 11:56:10 2023]: DSM idle for too long. [Source: Local System]
[15] [Nov 15 11:55:04 2023]: DSM idle for too long. [Source: Local System]
[16] [Nov 15 11:54:42 2023]: DSM idle for too long. [Source: Local System]
[17] [Nov 15 11:56:21 2023]: DSM idle for too long. [Source: Local System]
[18] [Nov 15 11:57:38 2023]: DSM idle for too long. [Source: Local System]
[19] [Nov 15 11:57:16 2023]: DSM idle for too long. [Source: Local System]
[20] [Nov 15 11:55:26 2023]: DSM idle for too long. [Source: Local System]
[21] [Nov 15 11:56:54 2023]: DSM idle for too long. [Source: Local System]
[22] [Nov 15 11:55:59 2023]: DSM idle for too long. [Source: Local System]
[23] [Nov 15 11:54:20 2023]: DSM idle for too long. [Source: Local System]
[24] [Nov 15 11:53:25 2023]: DSM idle for too long. [Source: Local System]
[25] [Nov 15 11:58:11 2023]: DSM idle for too long. [Source: Local System]
[26] [Nov 15 11:58:00 2023]: DSM idle for too long. [Source: Local System]
[27] [Nov 15 11:57:49 2023]: DSM idle for too long. [Source: Local System]
[28] [Nov 15 11:57:27 2023]: DSM idle for too long. [Source: Local System]
