1x RTx 4090 fully synced , Windows 10 , Firewall accepted, getkey done and linked with wallet android
When entering “ifconfig” , it says "exception :v : False (network manager is unavailble)
I would have posted log , but cannot because new comer cannot use links , will try later to add it.
during rebooting of core I can see messages as follow:
[Vitals Monitoring]: Network Manager seems dead.
[Vitals Monitoring]: DSM synchronization seems dead.
[Vitals Monitoring]: Network Manager not Operational.
[Bootstrap Stage]: Initializing Kademlia for TestNet
[Vitals Monitoring]: Network Manager seems dead.
[Vitals Monitoring]: DSM synchronization seems dead.
[Vitals Monitoring]: Network Manager not Operational.
[Bootstrap Stage]: Initializing Kademlia for TestNet
BH is fully synced
I see other operators
Web page is working over https on IP address
Solid Storage: File directory was initialized at: 'C:\Users\Administrator\AppData\Roaming\GRIDNET'
Detected valid Certificate and Private-Key!C:\Users\Administrator\AppData\Roaming\GRIDNET\cert.pem
[TestNet:Blockchain Manager]: WWW Server (RAW) successfully bound to: http://0.0.0.0:80
[TestNet:Blockchain Manager]: WWW Server (TLS) successfully bound to: https://0.0.0.0:443
[TestNet:Blockchain Manager]: Note: blockchain formation for Local Sandbox is *NOT* advised except for development and testing.
[TestNet:Blockchain Manager]: I'm now running
[TestNet:Blockchain Manager]: [ Setting-up Network Notifications ]
[TestNet:Blockchain Manager]: [ Setting-up Local System Notifications ]
[TestNet:Blockchain Manager]: [ Setting-up Decentralized VM Notifications ]
[TestNet:Blockchain Manager]: [ Setting-up Debug Info Notifications ]
[TestNet:Blockchain Manager]: [ Setting-up Unknown Notifications ]
[TestNet:Settings]: keyChain for: 1KpndNbW47zhG88raaFtUARdmZ8oDaynnH was FOUND!
[TestNet:Blockchain Manager]: Operator's Key-Chain ID:
[TestNet:Blockchain Manager]: Operator's State Domain ID: 1KpndNbW47zhG88raaFtUARdmZ8oDaynnH
[TestNet:Blockchain Manager]: Note: Your current ID within the network is: 1KpndNbW47zhG88raaFtUARdmZ8oDaynnH use 'getNextID' to generate and set new ID from your key-chain at any moment.
[TestNet:Blockchain Manager]: Retrieving paths from cache..
[TestNet:Blockchain Manager]: getting the Chain-Proof from Cold Storage..
[TestNet:Blockchain Manager]: Verified Chain-Proof retrieved.
[TestNet:Blockchain Manager]: Validating availability of the recent Perspective..
[TestNet:Blockchain Manager]: Current perspective available.
[TestNet:Blockchain Manager]: Heaviest Chain-Proof retrieved.
[TestNet:Blockchain Manager]: The Heaviest Chain-Proof and Heaviest Path seem inconsistent. I'll assume 'verified' as 'heaviest'.
[TestNet:Blockchain Manager]: Verifying the 'verified' chain-proof..
[TestNet:Blockchain Manager]: The 'verified' chain-proof leading block:L2FtGUZ6pMrjjdbcPpduL3b9qUQgejyNxHqJZ3sRwPU1mdKFC. At height: 32202
Just as extra input:
I hope someone has a clue what goes wrong here…
> -- Registered WebSock Conversations --
> none
> -------
>
> [DSM Sync]: processing new block notification from 91.218.244.12.
> [DSM Sync]: the received block-header from 91.218.244.12 is already known.
>
> -- Registered UDT Conversations --
>
> 2x3B9bL5CF4tQL4h8@148.251.75.24:running 🔒
> 3ua1zbJk3TKpEvwVv@146.70.124.203:running 🔒
> 1X2Rj2BL8DYPjuZf@178.132.108.54:running 🔒
> 3VkLpG2oYnUE8sYHx@89.151.33.34:running 🔒
> 3BSKPEMQnkKbgKBQF@146.70.188.26:running 🔒
> 2hGwHqEHLET79xNQK@84.247.59.200:running 🔒
> 2ritZTWaYNZJ2pVVR@91.90.44.28:running 🔒
> 4oQ3Ey6P1rYxyuYLi@216.205.168.31:running 🔒
> tGdDcuwT8Pc8FTqv@185.213.154.180:running 🔒
> 5FyzcCLa3eQd58yH5@92.60.40.196:running 🔒
> 1a4ErxTvroijno5P@198.52.230.233:running 🔒
> aZdoVwW2NrAcqLid@141.98.254.169:running 🔒
> KJMwGEmYMQGkG846@141.98.255.150:running 🔒
> exUXVouPQq7wCxa6@91.218.244.12:running 🔒
> 3ZYpup6kEycdguTzF@185.53.196.226:running 🔒
> 3d7mP7sw8JXgLiiCV@45.155.40.249:running 🔒
> 4DxgdFF6gF6o2K6Zu@185.254.75.45:running 🔒
>
> -------
>
> [DSM Sync]: processing new block notification from 185.254.75.45.
> [DSM Sync]: the received block-header from 185.254.75.45 is already known.
> [DSM Sync]: processing new block notification from 216.205.168.31.
> [DSM Sync]: the received block-header from 216.205.168.31 is already known.
> [DSM Sync]: processing new block notification from 141.98.255.150.
> [DSM Sync]: the received block-header from 141.98.255.150 is already known.
> [DSM Sync]: processing new block notification from 185.213.154.180.
> [DSM Sync]: the received block-header from 185.213.154.180 is already known.
> [DSM Sync]: processing new block notification from 146.70.188.26.
> [DSM Sync]: processing new block notification from 92.60.40.196.
> [DSM Sync]: the received block-header from 146.70.188.26 is already known.
> [DSM Sync]: the received block-header from 92.60.40.196 is already known.
> [DSM Sync]: processing new block notification from 185.53.196.226.
> [DSM Sync]: the received block-header from 185.53.196.226 is already known.
> [DSM Sync]: processing new block notification from 198.52.230.233.
> [DSM Sync]: the received block-header from 198.52.230.233 is already known.
> [DSM Sync]: processing new block notification from 146.70.124.203.
> [DSM Sync]: the received block-header from 146.70.124.203 is already known.
> [DSM Sync]: processing new block notification from 141.98.254.169.
> [DSM Sync]: the received block-header from 141.98.254.169 is already known.
> [DSM Sync]: processing new block notification from 178.132.108.54.
> [DSM Sync]: the received block-header from 178.132.108.54 is already known.
> [DSM Sync]: processing new block notification from 148.251.75.24.
> [DSM Sync]: the received block-header from 148.251.75.24 is already known.
> [DSM Sync]: processing new block notification from 84.247.59.200.
> [DSM Sync]: the received block-header from 84.247.59.200 is already known.
> [Kademlia: Reports] - aware of 29 nodes.
> [DSM Sync]: processing new block notification from 45.155.40.249.
> [DSM Sync]: the received block-header from 45.155.40.249 is already known.
> [TestNet:Transaction Manager]: Initiating Mem-Pool clean-up
> [DSM Sync]: processing new block notification from 91.90.44.28.
> [DSM Sync]: the received block-header from 91.90.44.28 is already known.
> [DSM Sync]: processing new block notification from 89.151.33.34.
> [DSM Sync]: the received block-header from 89.151.33.34 is already known.
> [DSM Sync]: processing new block notification from 91.218.244.12.
> [DSM Sync]: the received block-header from 91.218.244.12 is already known.
> [DSM Sync]: processing new block notification from 185.254.75.45.
> [DSM Sync]: the received block-header from 185.254.75.45 is already known.
> [DSM Sync]: processing new block notification from 141.98.255.150.
> [DSM Sync]: the received block-header from 141.98.255.150 is already known.
> [DSM Sync]: processing new block notification from 185.213.154.180.
> [DSM Sync]: processing new block notification from 216.205.168.31.
> [DSM Sync]: the received block-header from 185.213.154.180 is already known.
> [DSM Sync]: the received block-header from 216.205.168.31 is already known.
> [DSM Sync]: processing new block notification from 146.70.188.26.
> [DSM Sync]: the received block-header from 146.70.188.26 is already known.
> [DSM Sync]: processing new block notification from 185.53.196.226.
> [DSM Sync]: the received block-header from 185.53.196.226 is already known.
> [DSM Sync]: processing new block notification from 92.60.40.196.
> [DSM Sync]: the received block-header from 92.60.40.196 is already known.
> [DSM Sync]: processing new block notification from 198.52.230.233.
> [DSM Sync]: the received block-header from 198.52.230.233 is already known.
> [DSM Sync]: processing new block notification from 146.70.124.203.
> [DSM Sync]: the received block-header from 146.70.124.203 is already known.
> [DSM Sync]: processing new block notification from 141.98.254.169.
> [DSM Sync]: the received block-header from 141.98.254.169 is already known.
> [DSM Sync]: processing new block notification from 148.251.75.24.
> [DSM Sync]: the received block-header from 148.251.75.24 is already known.
> [DSM Sync]: processing new block notification from 178.132.108.54.
> [DSM Sync]: the received block-header from 178.132.108.54 is already known.
> [DSM Sync]: processing new block notification from 84.247.59.200.
> [DSM Sync]: the received block-header from 84.247.59.200 is already known.
> -- Registered Swarms: 1 --
> 1) [Local Peers]: 0 [Remote Peers]: 0
> -----------------------
>
> [TestNet:Transaction Manager]: Min. # of objects for block formation: 1
> [DSM Sync]: processing new block notification from 45.155.40.249.
> [DSM Sync]: the received block-header from 45.155.40.249 is already known.
> [Vitals Monitoring]: All looking Good.
> [DSM Sync]: processing new block notification from 91.90.44.28.
> [DSM Sync]: processing new block notification from 89.151.33.34.
> [DSM Sync]: the received block-header from 91.90.44.28 is already known.
> [DSM Sync]: the received block-header from 89.151.33.34 is already known.
> [DSM Sync]: processing new block notification from 91.218.244.12.
> [DSM Sync]: the received block-header from 91.218.244.12 is already known.
> [DSM Sync]: processing new block notification from 185.254.75.45.
> [DSM Sync]: the received block-header from 185.254.75.45 is already known.
> [DSM Sync]: processing new block notification from 141.98.255.150.
> [DSM Sync]: the received block-header from 141.98.255.150 is already known.
> [DSM Sync]: processing new block notification from 216.205.168.31.
> [DSM Sync]: the received block-header from 216.205.168.31 is already known.
> [DSM Sync]: processing new block notification from 185.213.154.180.
> [DSM Sync]: the received block-header from 185.213.154.180 is already known.
> [DSM Sync]: processing new block notification from 185.53.196.226.
> [DSM Sync]: the received block-header from 185.53.196.226 is already known.
> [DSM Sync]: processing new block notification from 146.70.188.26.
> [DSM Sync]: the received block-header from 146.70.188.26 is already known.
> [DSM Sync]: processing new block notification from 92.60.40.196.
> [DSM Sync]: the received block-header from 92.60.40.196 is already known.
> [DSM Sync]: processing new block notification from 198.52.230.233.
> [DSM Sync]: the received block-header from 198.52.230.233 is already known.
> [DSM Sync]: processing new block notification from 146.70.124.203.
> [DSM Sync]: the received block-header from 146.70.124.203 is already known.
> [DSM Sync]: processing new block notification from 148.251.75.24.
> [DSM Sync]: the received block-header from 148.251.75.24 is already known.
> [DSM Sync]: processing new block notification from 141.98.254.169.
> [DSM Sync]: the received block-header from 141.98.254.169 is already known.
> [DSM Sync]: processing new block notification from 178.132.108.54.
> [DSM Sync]: processing new block notification from 84.247.59.200.
> [DSM Sync]: the received block-header from 178.132.108.54 is already known.
> [DSM Sync]: the received block-header from 84.247.59.200 is already known.
> [Kademlia: Reports] - aware of 29 nodes.
> [DSM Sync]: processing new block notification from 45.155.40.249.
> [DSM Sync]: the received block-header from 45.155.40.249 is already kn
own.
Welcome Operator
[Local:GRIDNET]: Seems like no need to tweak TDR value. It is equal to 30 already.
[Local:GRIDNET]: Firewall Updated: native firewall rules have been updated.
Solid Storage: File directory was initialized at: 'C:\Users\Administrator\AppData\Roaming\GRIDNET'
[TestNet:SolidStorage]: successfully deployed OpenCL cache at: 'C:\Users\Administrator\AppData\Roaming\GRIDNET\kernel\'
[TestNet:SolidStorage]: Testing OpenCL cache at: 'C:\Users\Administrator\AppData\Roaming\GRIDNET\kernel\'
[TestNet:SolidStorage]: OpenCL cache was tested successfully!
Solid Storage: Now initializing RocksDBs...
Solid Storage: Initializing the LIVE Blockchain database...
Solid Storage: LIVE Blockchain-RocksDB: Ready!
Solid Storage: Initializing LIVE TrieDB over RocksDB:
Solid Storage: LIVE TrieDB ockchain-RocksDB: Ready!
Solid Storage: Initializing the STAGED LIVE TrieDB over RocksDB:
Solid Storage: the STAGED LIVE TrieDB ockchain-RocksDB: Ready!
Solid Storage: Initializing the TEST-NET Blockchain over RocksDB...
Solid Storage: TEST-NET Blockchain ockchain-RocksDB: Ready!
Solid Storage: Initializing TEST-NET TrieDB over RocksDB..
Solid Storage: TEST-NET TrieDB ockchain-RocksDB: Ready!
Solid Storage: Initializing the STAGED TEST-NET TrieDB over RocksDB:
Solid Storage: the STAGED TEST-NET TrieDB ockchain-RocksDB: Ready!
Solid Storage: Initializing the LOCAL TEST Blockchain over RocksDB...
Solid Storage: LOCAL TEST Blockchain ockchain-RocksDB: Ready!
Solid Storage: Initializing LOCAL TEST TrieDB over RocksDB..
Solid Storage: LOCAL TEST TrieDB ockchain-RocksDB: Ready!
Solid Storage: Initializing the STAGED LOCAL-TEST TrieDB over RocksDB:
Solid Storage: the STAGED LOCAL-TEST TrieDB ockchain-RocksDB: Ready!
OCL Engine: Attempting to initialize the decentralized computations engine..
OCL Engine: Will attempt to use only the available GPUs
OCL Engine: Found a single OpenCL platform
OCL Engine: Processing computational platforms..
OCL Engine: [Stage 1]: doing preliminary computational platforms' analysis..
OCL Engine: Pre-Processing platform: NVIDIA CUDA
OCL Engine: Platform NVIDIA CUDA is preferred.
OCL Engine: Found 1 preferred platforms.. I'll more picky and neglect integrated GPU platforms..
OCL Engine: [Stage 2]: doing main computational platforms' analysis..
OCL Engine: Processing platform: NVIDIA CUDA
OCL Engine: looking for GPUs only..
OCL Engine: Found 1
OCL Engine: Initialized 1 NVIDIA CUDA devices.
OCL Engine: OpenCL initialization succeeded.
[Local:Work Manager]: Initializing work scheduler..
[Local:Work Manager]: workers already prepared.
Checking integrity of OpenCL components..
[OpenCL]: file '.\kernel\gridnetTest.cl' is present.
[OpenCL]: file '.\kernel\blake.cl' is present.
[OpenCL]: file '.\kernel\hamsi.cl' is present.
[OpenCL]: file '.\kernel\jh.cl' is present.
[OpenCL]: file '.\kernel\keccak.cl' is present.
[OpenCL]: file '.\kernel\shavite.cl' is present.
[OpenCL]: file '.\kernel\skein.cl' is present.
[OpenCL]: file '.\kernel\gridnetTest.cl' is present.
[OpenCL]: file '.\kernel\aes_helper.cl' is present.
[Local:Blockchain Manager]: Lo and behold; initializing the Great GRIDNET Local Blockchain Manager..
[OpenCL]: file '.\kernel\hamsi_helper.cl' is present.
[OpenCL]: Ultimium Components are present.
[Local:Blockchain Manager]: Note: Networking for local sandbox is *NOT* advised, but for development and local testing.
[Local:Blockchain Manager]: Note: blockchain formation for Local Sandbox is *NOT* advised except for development and testing.
[Local:Blockchain Manager]: [ Setting-up Network Notifications ]
[Local:Blockchain Manager]: [ Setting-up Local System Notifications ]
[Local:Blockchain Manager]: [ Setting-up Decentralized VM Notifications ]
[Local:Blockchain Manager]: [ Setting-up Debug Info Notifications ]
[Local:Blockchain Manager]: [ Setting-up Unknown Notifications ]
[Local:Settings]: keyChain for: 12D6gHNLbzL51W9JqgEqVKtqQfdD4NZcmM was FOUND!
[Local:Blockchain Manager]: Retrieving paths from cache..
[Local:Blockchain Manager]: getting the Chain-Proof from Cold Storage..
[Local:Blockchain Manager]: Verified Path is empty
[Local:Blockchain Manager]: No current leader block available.
[Local:Blockchain Manager]: Verifying local data availability..
[Local:Blockchain Manager]: Checking block availability..
[Local:Blockchain Manager]: [Heaviest Chain-Proof]:Local data availability is 0 %
[Local:Blockchain Manager]: No current perspective available.
[Local:Transaction Manager]: Waiting for Blockchain Manager to become ready..
[Local:Transaction Manager]: Waiting for myself to become ready..
[Local:Transaction Manager]: I'm ready, commencing further..
[Local:Transaction Manager]: Waiting for Blockchain Manager to become ready..
[Local:Transaction Manager]: I'm ready, commencing further..
[Local:Transaction Manager]: Waiting for Blockchain Manager to become ready..
[Local:Blockchain Manager]: Updating new cached difficulty co-efficients to match the target (sec):600
[Local:Blockchain Manager]: Falling back to initial difficulty, Leader unknown
[Local:Blockchain Manager]: New Base Difficulty: 1.000000
[Local:Blockchain Manager]: Updating the current ERG price
[Local:Blockchain Manager]: I'm now running
[Local:Blockchain Manager]: Initializing #GridScript (De)Compiler..
[Local:Transaction Manager]: I'm ready, commencing further..
[Local:Transaction Manager]: Running
[Local:Work Manager]: I'm now running
[Local:GRIDNET]: initializing worker: NVIDIA GeForce RTX 4090 (cloned) ( NVIDIA-1 )
[Local:GRIDNET]: NVIDIA-1 is warming up..
[Local:Transaction Manager]: Blockchain Manager ready, commencing further..
[Local:Transaction Manager]: Running
[Local:Transaction Manager]: I'm ready; Firing up block-formation sub-systems! (Key-Blocks:Disabled Data-Blocks:Disabled)
[Local:Transaction Manager]: Blockchain Manager ready, commencing further..
[Local:Transaction Manager]: Running
[Local:Transaction Manager]: Blockchain Manager ready, commencing further..
[Local:Transaction Manager]: Running
[Local:GRIDNET]: worker NVIDIA-1 is now ready.
[Local:Work Manager]: scheduler is still waiting for workers..
[Local:Test Unit]: Work Manager (OpenCL platform) Test Commencing now..
[Local:Test Unit]: Max testing time: 3 minutes or until mined.
[Local:Test Unit]: Setting min. Test difficulty to: 1000.000
[Local:Test Unit]: Setting Test difficulty to: 100.000
[Local:Test Unit]: Waiting for at least one computational device to become available (this might take many hours)..
[Local:Test Unit]: Ready devices found. Proceeding further..
Sub-Task 1: enqued.
[Local:Test Unit]: About to commence with Computational Task 1/3
[Local:Work Manager]: Work 1 was divided into 1 parts. IDs: i1JNn7YHJmmUQC5ZTEwno65FNa5RcJ3fhHGoYczmakjHax7Pw ShortID:2
Sub-Task 2: assigned to a worker.
NVIDIA-1 switched tasks.
Task 2: <----------------[[ assigned to NVIDIA-1 ]]
Sub-Task 2: getting prepared.
Sub-Task 2: prepared.
NVIDIA-1 is now working..
Activating a prepared task.
Sub-Task 1: being worked on. (reported by a sub-task)
Sub-Task 2: being worked on.
Ultimium: NVIDIA-1 found one partial PoW (nonce) : 6815072
Ultimium: NVIDIA-1 found one partial PoW (nonce) : 26140502
/-[ Ultimium: .-=========-.
'-=======-'/
_| .=. |_
((| {{1}} |))
| /| |/
__ '`' __/
_`) (`_
jgs _/________
/___________\n
Ultimium: NVIDIA-1 found one partial PoW (nonce) : 42411390
Sub-Task 2: doneTargetMet (accomplished).
Sub-Task 1: doneTargetMet (accomplished). (reported by a sub-task)
Sub-Task 1: finished.
[Local:Test Unit]: Stopping performance calculation - got confirmed final results..
Sub-Task 1: aborted.
[Local:Test Unit]: >[ SUCCESS: PoW - 0 ]<
Found Nonce: 6815072
Min. Target: 100831065
>[ SUCCESS: PoW - 1 ]<
Found Nonce: 14661702
Min. Target: 100831065
>[ SUCCESS: PoW - 2 ]<
Found Nonce: 26140502
Min. Target: 100831065
>[ SUCCESS: PoW - 3 ]<
.-=========-.
'-=======-'/
_| .=. |_
((| {{1}} |))
| /| |/
__ '`' __/
_`) (`_
jgs _/________
/___________\n
Found Nonce: 32531153
Min. Target: 100831065
>[ SUCCESS: PoW - 4 ]<
Found Nonce: 42411390
Min. Target: 100831065
Sub-Task 3: enqued.
[Local:Test Unit]: About to commence with Computational Task 2/3
worker's ( NVIDIA-1) task was stopped.
Sub-Task 2: aborted.
Ultimium: I'm releasing my resources..
Ultimium: released!
Sub-Task 2: finished.
Sub-Task 1: doneTargetMet (accomplished).
worker's ( NVIDIA-1) task was stopped.
[Local:GRIDNET]: Average Mhps (NVIDIA-1) average Mhps: 9.802043
[Local:GRIDNET]: initializing worker: NVIDIA GeForce RTX 4090 (cloned) ( NVIDIA-1 )
[Local:GRIDNET]: NVIDIA-1 is warming up..
--[ [Nov 12 09:40:25 2023]: waiting for kernel to compile for a Master Task
[Local:GRIDNET]: worker NVIDIA-1 is now ready.
Sub-Task 1: finished.
[Local:Work Manager]: Work 3 was divided into 1 parts. IDs: 2H8qBBXGjx9tJi8uu8oJ73LHBaSiWK4nXh5B142YCarUGTghYS ShortID:4
Sub-Task 4: assigned to a worker.
NVIDIA-1 switched tasks.
Task 4: <----------------[[ assigned to NVIDIA-1 ]]
Sub-Task 4: getting prepared.
Sub-Task 4: prepared.
NVIDIA-1 is now working..
Activating a prepared task.
Sub-Task 3: being worked on. (reported by a sub-task)
Sub-Task 4: being worked on.
Ultimium: NVIDIA-1 found one partial PoW (nonce) : 1679164
Ultimium: NVIDIA-1 found one partial PoW (nonce) : 20231827
Ultimium: NVIDIA-1 found one partial PoW (nonce) : 21158890
Ultimium: NVIDIA-1 found one partial PoW (nonce) : 21695483
Ultimium: .-=========-.
'-=======-'/
_| .=. |_
((| {{1}} |))
| /| |/
__ '`' __/
_`) (`_
jgs _/________
/___________\n
Ultimium: NVIDIA-1 found one partial PoW (nonce) : 37134946
Ultimium: NVIDIA-1 found one partial PoW (nonce) : 38134580
Ultimium: NVIDIA-1 found one partial PoW (nonce) : 42800099
Sub-Task 4: doneTargetMet (accomplished).
Sub-Task 3: doneTargetMet (accomplished). (reported by a sub-task)
Sub-Task 3: finished.
Sub-Task 4: aborted.
worker's ( NVIDIA-1) task was stopped.
Ultimium: I'm releasing my resources..
Ultimium: released!
Sub-Task 4: finished.
Sub-Task 3: doneTargetMet (accomplished).
[Local:GRIDNET]: Average Mhps (NVIDIA-1) average Mhps: 19.365047
[Local:GRIDNET]: initializing worker: NVIDIA GeForce RTX 4090 (cloned) ( NVIDIA-1 )
[Local:GRIDNET]: NVIDIA-1 is warming up..
[Local:GRIDNET]: worker NVIDIA-1 is now ready.
Sub-Task 3: finished.
[Local:Test Unit]: Stopping performance calculation - got confirmed final results..
[Local:Test Unit]: Kernel inactivity detected. Warning issued..
Sub-Task 3: aborted.
[Local:Test Unit]: >[ SUCCESS: PoW - 0 ]<
Found Nonce: 1679164
Min. Target: 100831065
>[ SUCCESS: PoW - 1 ]<
Found Nonce: 20231827
Min. Target: 100831065
>[ SUCCESS: PoW - 2 ]<
Found Nonce: 21158890
Min. Target: 100831065
>[ SUCCESS: PoW - 3 ]<
Found Nonce: 21695483
Min. Target: 100831065
>[ SUCCESS: PoW - 4 ]<
.-=========-.
'-=======-'/
_| .=. |_
((| {{1}} |))
| /| |/
__ '`' __/
_`) (`_
jgs _/________
/___________\n
Found Nonce: 28095127
Min. Target: 100831065
>[ SUCCESS: PoW - 5 ]<
Found Nonce: 37134946
Min. Target: 100831065
>[ SUCCESS: PoW - 6 ]<
Found Nonce: 38134580
Min. Target: 100831065
>[ SUCCESS: PoW - 7 ]<
Found Nonce: 42800099
Min. Target: 100831065
Sub-Task 5: enqued.
[Local:Test Unit]: About to commence with Computational Task 3/3
[Local:Work Manager]: Work 5 was divided into 1 parts. IDs: 2S9LR1iNv8YfAvtrH3NZCiL1CoYg7iyXGoHRWs6Q6v5jP9zdep ShortID:6
Sub-Task 6: assigned to a worker.
NVIDIA-1 switched tasks.
Task 6: <----------------[[ assigned to NVIDIA-1 ]]
Sub-Task 6: getting prepared.
Sub-Task 6: prepared.
NVIDIA-1 is now working..
Activating a prepared task.
Sub-Task 5: being worked on. (reported by a sub-task)
Sub-Task 6: being worked on.
Ultimium: .-=========-.
'-=======-'/
_| .=. |_
((| {{1}} |))
| /| |/
__ '`' __/
_`) (`_
jgs _/________
/___________\n
Ultimium: NVIDIA-1 found one partial PoW (nonce) : 6934293
Ultimium: NVIDIA-1 found one partial PoW (nonce) : 11393225
Sub-Task 6: doneTargetMet (accomplished).
Sub-Task 5: doneTargetMet (accomplished). (reported by a sub-task)
Sub-Task 5: finished.
worker's ( NVIDIA-1) task was stopped.
Sub-Task 6: aborted.
Ultimium: I'm releasing my resources..
Ultimium: released!
Sub-Task 6: finished.
Sub-Task 5: doneTargetMet (accomplished).
[Local:Test Unit]: Stopping performance calculation - got confirmed final results..
[Local:Test Unit]: Kernel inactivity detected. Warning issued..
worker's ( NVIDIA-1) task was stopped.
[Local:GRIDNET]: Average Mhps (NVIDIA-1) average Mhps: 21.017853
[Local:GRIDNET]: initializing worker: NVIDIA GeForce RTX 4090 (cloned) ( NVIDIA-1 )
[Local:GRIDNET]: NVIDIA-1 is warming up..
Sub-Task 5: aborted.
[Local:Test Unit]: >[ SUCCESS: PoW - 0 ]<
.-=========-.
'-=======-'/
_| .=. |_
((| {{1}} |))
| /| |/
__ '`' __/
_`) (`_
jgs _/________
/___________\n
Found Nonce: 334132
Min. Target: 100831065
>[ SUCCESS: PoW - 1 ]<
Found Nonce: 6934293
Min. Target: 100831065
>[ SUCCESS: PoW - 2 ]<
Found Nonce: 11393225
Min. Target: 100831065
[Local:GRIDNET]: worker NVIDIA-1 is now ready.
>
v----------------------- OpenCL platform Test Report -----------------------v
[NVIDIA-1 Statistics Report]-v
[Full Name]: NVIDIA GeForce RTX 4090 (cloned)
[Work Items served]: 3
[Average Mhps]: 21.017853
[Time In Tests(sec)]: 8
[Current State]:Warming Up
^---------------------------^
[Computational Power of Active Devices]:21.017853 (Mhps)
[Computational Power of All Devices]:21.017853 (Mhps)
>
^----------------------- OpenCL platform Test Report -----------------------^
[Local:GRIDNET]: The test succeeded.
[TestNet:Blockchain Manager]: Lo and behold; initializing the Great GRIDNET TestNet Blockchain Manager..
[TestNet:Blockchain Manager]: Storing current networking configuration..
[TestNet:Network Manager]: Initializing the GRIDNET Networking Subsystem..
[TestNet:Network Manager]: Auto-Detecting Local IPv4..
[TestNet:Network Manager]: Auto-Detected Local IPv4:45.87.105.61
[TestNet:Network Manager]: Added 45.87.105.61 to the pool of local IP addresses.
[TestNet:Network Manager]: I'll be listening on all network interfaces.
[TestNet:Network Manager]: Auto-Detecting Public IPv4..
[TestNet:Network Manager]: Auto-Detected Public IPv4:45.87.105.61
[TestNet:Network Manager]: I'll be using Public IPv4:45.87.105.61
[TestNet:Network Manager]: User provided Bootstrap node (148.251.75.43) will be the first one to try.
Whitelisting IP Address: 127.0.0.1
Whitelisting IP Address: 0.0.0.0
Whitelisting IP Address: 45.87.105.61
Solid Storage: File directory was initialized at: 'C:\Users\Administrator\AppData\Roaming\GRIDNET'
Detected valid Certificate and Private-Key!C:\Users\Administrator\AppData\Roaming\GRIDNET\cert.pem
[TestNet:Blockchain Manager]: WWW Server (RAW) successfully bound to: http://0.0.0.0:80
[TestNet:Blockchain Manager]: WWW Server (TLS) successfully bound to: https://0.0.0.0:443
[TestNet:Blockchain Manager]: Note: blockchain formation for Local Sandbox is *NOT* advised except for development and testing.
[TestNet:Blockchain Manager]: I'm now running
[TestNet:Blockchain Manager]: [ Setting-up Network Notifications ]
[TestNet:Blockchain Manager]: [ Setting-up Local System Notifications ]
[TestNet:Blockchain Manager]: [ Setting-up Decentralized VM Notifications ]
[TestNet:Blockchain Manager]: [ Setting-up Debug Info Notifications ]
[TestNet:Blockchain Manager]: [ Setting-up Unknown Notifications ]
[TestNet:Settings]: keyChain for: 18KRJhkcCqn3oXiZYgHaMrnP5N1hqi29PW was FOUND!
[TestNet:Blockchain Manager]: Operator's Key-Chain ID:
[TestNet:Blockchain Manager]: Operator's State Domain ID: 18KRJhkcCqn3oXiZYgHaMrnP5N1hqi29PW
[TestNet:Blockchain Manager]: Note: Your current ID within the network is: 18KRJhkcCqn3oXiZYgHaMrnP5N1hqi29PW use 'getNextID' to generate and set new ID from your key-chain at any moment.
[TestNet:Blockchain Manager]: Retrieving paths from cache..
[TestNet:Blockchain Manager]: getting the Chain-Proof from Cold Storage..
[TestNet:Blockchain Manager]: Verified Chain-Proof retrieved.
[TestNet:Blockchain Manager]: Validating availability of the recent Perspective..
[TestNet:Blockchain Manager]: Current perspective available.
[TestNet:Blockchain Manager]: Heaviest Chain-Proof retrieved.
[TestNet:Blockchain Manager]: Verifying the 'verified' chain-proof..
[TestNet:Blockchain Manager]: The 'verified' chain-proof leading block:2TyZ1GLcYgSzDsa3xxstyByt7T5GZbnwgRhLFGi6kttYmt6t4v. At height: 32228
about to verify a long chain-proof (32229 elements). Status will be reported.
[Checkpoints]: Attempting to activate path-local checkpoints..
[Chain-Proof Validation]: Obligatory checkpoint for height 13668 activated.
[Chain-Proof Validation]: Obligatory checkpoint for height 21237 activated.
[Chain-Proof Validation]: Obligatory checkpoint for height 23911 activated.
[Chain-Proof Validation]: Obligatory checkpoint for height 27600 activated.
[Chain-Proof Validation]: Obligatory checkpoint for height 28489 activated.
[Chain-Proof Validation]: Obligatory checkpoint for height 30864 activated.
[Chain-Proof Validation]: Obligatory checkpoint for height 31227 activated.
[TestNet:Blockchain Manager]: The 'verified' chain-proof is VALID. Total difficulty: 7686410524
[TestNet:Blockchain Manager]: Leading verified block at height 32228: 2TyZ1GLcYgSzDsa3xxstyByt7T5GZbnwgRhLFGi6kttYmt6t4v
[TestNet:Blockchain Manager]: Verifying the 'heaviest' chain-proof..
about to verify a long chain-proof (32229 elements). Status will be reported.
[Checkpoints]: Attempting to activate system-wide checkpoints..
[System Checkpoints]: Obligatory checkpoint for height 13668 activated.
[System Checkpoints]: Obligatory checkpoint for height 21237 activated.
[System Checkpoints]: Obligatory checkpoint for height 23911 activated.
[System Checkpoints]: Obligatory checkpoint for height 27600 activated.
[System Checkpoints]: Obligatory checkpoint for height 28489 activated.
[System Checkpoints]: Obligatory checkpoint for height 30864 activated.
[System Checkpoints]: Obligatory checkpoint for height 31227 activated.
[TestNet:Blockchain Manager]: The 'heaviest' Chain-Proof is VALID Total Difficulty:7686410524
[Checkpoints]: Attempting to activate system-wide checkpoints..
[System Checkpoints]: Obligatory checkpoint for height 13668 activated.
[System Checkpoints]: Obligatory checkpoint for height 21237 activated.
[System Checkpoints]: Obligatory checkpoint for height 23911 activated.
[System Checkpoints]: Obligatory checkpoint for height 27600 activated.
[System Checkpoints]: Obligatory checkpoint for height 28489 activated.
[System Checkpoints]: Obligatory checkpoint for height 30864 activated.
[System Checkpoints]: Obligatory checkpoint for height 31227 activated.
[TestNet:Blockchain Manager]: Retrieved body of current Leader block: 2TyZ1GLcYgSzDsa3xxstyByt7T5GZbnwgRhLFGi6kttYmt6t4v
[TestNet:Blockchain Manager]: Current Blockchain height: 32228
[TestNet:Blockchain Manager]: Verifying local data availability..
[TestNet:Blockchain Manager]: Checking block availability..
[TestNet:Blockchain Manager]: [Heaviest Chain-Proof]:Local data availability is 100 %
[TestNet:Blockchain Manager]: Current Effective Perspective: 2aVxbddUzxyP4Mh2gKy79ZAKrpaLexLjrwwc9zNBwxFWz3f6gA
[TestNet:Blockchain Manager]: Testing the main StateTrie DB. This might take some time..
[TestNet:Blockchain Manager]: Finished. There are 686 State Domains in total.
[TestNet:Blockchain Manager]: 686 State Domains found.
[TestNet:Transaction Manager]: Waiting for Blockchain Manager to become ready..
Bootstrap: Waiting for the Network Manager to initialize..
[TestNet:Transaction Manager]: Waiting for myself to become ready..
[TestNet:Transaction Manager]: I'm ready, commencing further..
[TestNet:Transaction Manager]: Waiting for Blockchain Manager to become ready..
Up to 1 identities (from same key-chain) will be used for mining purposes.
[TestNet:Transaction Manager]: Waiting for myself to become ready..
[TestNet:Transaction Manager]: I'm ready, commencing further..
[TestNet:Transaction Manager]: Waiting for Blockchain Manager to become ready..
[Block Cache]: Preparing..
[TestNet:Blockchain Manager]: I'm now running
[Bootstrap Stage]: Initializing Network Manager for TestNet
[Local Update]: Checking for local UI update package..
[Local Update]: New UI update package available..
[UI Server]: Entering maintenance mode now..
[UI Server]: Exiting maintenance mode..
[TestNet:Transaction Manager]: I'm ready, commencing further..
[TestNet:Transaction Manager]: Waiting for Blockchain Manager to become ready..
[Blockchain Cache Length]: 167
[TestNet:Blockchain Manager]: Updating new cached difficulty co-efficients to match the target (sec):600
[TestNet:Blockchain Manager]: New Base Difficulty: 4321818.356955
[TestNet:Blockchain Manager]: Updating the current ERG price
[TestNet:Network Manager]: Waiting for Blockchain Manager to become ready..
[TestNet:Blockchain Manager]: Initializing #GridScript (De)Compiler..
[TestNet:Network Manager]: Blockchain Manager ready, commencing further..
[TestNet:Network Manager]: I'm nowin an unknown state;/
[TestNet:Transaction Manager]: Blockchain Manager ready, commencing further..
[TestNet:Transaction Manager]: Running
[Networking Assistant]: No process found using port 22
[Networking Assistant]: No process found using port 443
[Local:Blockchain Manager]: I'm now running
[Network Configuration]: UDT sub-system needs to use a concrete IPv4 address, not a wild-card address. OVERRIDING IPv4 address assigned to Eth1 (0.0.0.0) with 45.87.105.61.
[Networking (UDT)]: Looks like you are not behind a NAT. The public Virtual Interface Eth0 (45.87.105.61) is to be assigned to the UDT subsystem.
[Networking (UDT)]: Bootstrapping UDT Service at 45.87.105.61:443
[TestNet:Transaction Manager]: Blockchain Manager ready, commencing further..
[TestNet:Transaction Manager]: Running
[TestNet:Transaction Manager]: Blockchain Manager ready, commencing further..
[TestNet:Transaction Manager]: Running
[TestNet:Transaction Manager]: Running Forming Key-blocks Forming Data-blocks
[TestNet:Transaction Manager]: I'm ready; Firing up block-formation sub-systems! (Key-Blocks:Enabled Data-Blocks:Enabled)
Node is still bootstrapping, holding on with block formation..
[TestNet:Blockchain Manager]: Vitals Monitor is now ACTIVE
[Vitals Monitoring]: Network Manager seems dead.
[Vitals Monitoring]: DSM synchronization seems dead.
[Vitals Monitoring]: Network Manager not Operational.
[Vitals Monitoring]: UDT System not Operational.
[TestNet:Network Manager]: GRIDNET Core DataExchange sub-system open at port: 443
[TestNet:Blockchain Manager]: I'm now running
[Networking Assistant]: No process found using port 443
[Networking Assistant]: No process found using port 80
[TestNet:Network Manager]: Web-Server already initialized
[TestNet:Blockchain Manager]: Attempting to bind CORS Proxy (TLS) to: https://0.0.0.0:444
[TestNet:Blockchain Manager]: Attempting to bind CORS Proxy (non-encrypted) to: http://0.0.0.0:8081
[TestNet:Blockchain Manager]: CORS Proxy (RAW) successfully bound to: http://0.0.0.0:8081
[TestNet:Blockchain Manager]: CORS Proxy (TLS) successfully bound to: https://0.0.0.0:444
[TestNet:Blockchain Manager]: I'm now running
Detected valid Certificate and Private-Key!C:\Users\Administrator\AppData\Roaming\GRIDNET\cert.pem
[TestNet:Blockchain Manager]: Attempting to bind WebSocket Server to: https://0.0.0.0:8001
[TestNet:Blockchain Manager]: Web-Sockets Server successfully bound to: https://0.0.0.0:8001
[TestNet:Blockchain Manager]: Web-Sockets Server bound to https://0.0.0.0:8001
[Kademlia]: Setting current bootstrap node to : IPv4(148.251.75.43) Port:443
[TestNet:Blockchain Manager]: I'm now running
-- Registered WebSock Conversations --
none
-------
[TestNet:Settings]: keyChain for: 18KRJhkcCqn3oXiZYgHaMrnP5N1hqi29PW was FOUND!
[TestNet:Blockchain Manager]: Initializing Kademlia-based node discovery..
[TestNet:Blockchain Manager]: Bootstrapping Peer Discovery Service at 0.0.0.0:443
[TestNet:Blockchain Manager]: Bootstrap peer is set to: 148.251.75.43:443
[TestNet:Network Manager]: created with id 'f72e77fd4de8d4a118f287bd7895675714fe1aa85eb8dd41193d92224db5412 (addr): 18KRJhkcCqn3oXiZYgHaMrnP5N1hqi29PW'.
[TestNet:Network Manager]: Network View bootstrapping using peer '148.251.75.43:443'.
-- Registered Swarms: 1 --
1) [Local Peers]: 0 [Remote Peers]: 0
-----------------------
-- Registered UDT Conversations --
none
-------
[TestNet:Network Manager]: Bootstrap node responded.
[Bootstrap Stage]: Initializing Kademlia for TestNet
Ingress UDT conversation with 216.205.168.31 has begun.
[DSM Sync]: processing new block notification from 216.205.168.31.
[DSM Sync]: won't request chain-proof from 216.205.168.31 - for now considering only Bootstrap nodes.
[TestNet:Blockchain Manager]: Launching the Kademlia thread..
[TestNet:Blockchain Manager]: I'll wait for 60 (sec) for peers' discovery..
[Kademlia: Reports] - aware of 6 nodes.
[TestNet:Blockchain Manager]: Nr. of discovered peers: 5
[Bootstrap Stage]: Initializing Kademlia for TestNet
[Kademlia: Reports] - aware of 6 nodes.
[DSM Sync]: processing new block notification from 216.205.168.31.
[DSM Sync]: won't request chain-proof from 216.205.168.31 - for now considering only Bootstrap nodes.
[Kademlia: Reports] - aware of 6 nodes.
[Vitals Monitoring]: Network Manager seems dead.
[Vitals Monitoring]: DSM synchronization seems dead.
[Vitals Monitoring]: Network Manager not Operational.
[Kademlia: Reports] - aware of 6 nodes.
[Bootstrap Stage]: Initializing Kademlia for TestNet
[Kademlia: Reports] - aware of 6 nodes.
[DSM Sync]: processing new block notification from 216.205.168.31.
[DSM Sync]: won't request chain-proof from 216.205.168.31 - for now considering only Bootstrap nodes.
[Kademlia: Reports] - aware of 6 nodes.
-- Registered WebSock Conversations --
none
-------
[Kademlia: Reports] - aware of 6 nodes.
[Bootstrap Stage]: Initializing Kademlia for TestNet
-- Registered UDT Conversations --
4LkLoMDqo54jXGo8u@216.205.168.31:running 🔒
-------
[Kademlia: Reports] - aware of 6 nodes.
[DSM Sync]: processing new block notification from 216.205.168.31.
[DSM Sync]: won't request chain-proof from 216.205.168.31 - for now considering only Bootstrap nodes.
[Kademlia: Reports] - aware of 6 nodes.
[Vitals Monitoring]: DSM synchronization seems dead.
[Vitals Monitoring]: Network Manager not Operational.
-- Registered Swarms: 1 --
1) [Local Peers]: 0 [Remote Peers]: 0
-----------------------
[Kademlia: Reports] - aware of 6 nodes.
[Bootstrap Stage]: Initializing Kademlia for TestNet
[Kademlia: Reports] - aware of 6 nodes.
[DSM Sync]: processing new block notification from 216.205.168.31.
[DSM Sync]: won't request chain-proof from 216.205.168.31 - for now considering only Bootstrap nodes.
mainly these cause the root issue in my feeling
Trying to provide as many information as possible.
The GPU has 2 network interfaces , the connected has ID Eth2, I disabled (even de-installed) the first one but no change so far.
Is it possible the boot script is searching for ETH1 only?
I noticed maybe something , (also added this in the ticket 398) , could it be that script phase 1 is searching for ETH1 (ethernet 1) connection only, I already tried installing it on 2 different GPU’s , they are in datacenter so they often get another ETH slot. 1 has ETH2 , 1 has ETH3
could this be the reason the network manager is failing to start in boot phase 1?
The problem got autoresolved … no idea what caused it and how it was resolved.
Hi There,
I have one gpu in my system and also want to mine Grid, can you help me how to setup ?
Hi Finalboss, did you follow the instructions first already?
and
@nw82 Dear Operator,
First of all, a sincere thank you for all the time and effort you’ve invested into providing us with such a meticulous Report! Reports such as this help the software improve and get better and better with each passing day. We put lots of effort to maintain satisfactory experience for each and every Operator!
Now, it might be that there never was a problem to begin with.
The ‘errors’ you are getting are notifications from the Vitals Monitoring sub-system. As one may clearly see below:
[Vitals Monitoring]: Network Manager seems dead.
[Vitals Monitoring]: DSM synchronization seems dead.
[Vitals Monitoring]: Network Manager not Operational.
Still, on other lines it also keeps saying that it is still in the Bootstrapping sequence! Thus, the Network Manager might not be available yet to begin with, indeed.
In 1.4.6 (upcoming) we’ve made the Vitals Monitoring sub-system kick-in only after all the bootstrapping sequences have finished, so not to create confusion.
How to tell if you are within a bootstrap sequence? Operator! At the bottom the Events’ View, to the right there’s a [Vitals] dial. If in bootstrap sequence, it would indicate something like Bootstrapping [Phase 1] (example).
Operators! Remember that checking the Vitals dial every now and then is of a paramount importance!
GRIDNET Core comes with an extremely sophisticated self-diagnostic apparatus. If it detects anything wrong with any of its components, the Vitals dial it would produce a warning sign. You may then use the ‘warnings’ GridScript command to look into these in more a detail.
The ‘ifconfig’ utility would become available right after the Network Manager becomes available which is when the Bootstrap sequence has finished.
We wish you Rewarding Operating !