search

HtheChemist / BitBurnerCentralManager

A prototype thread manager for BitBurner
MIT License
26 stars 12 forks source link

TargetManager stuck on "Scanning network" (Was closed but recurred again) #16

Closed flightdragonz closed 2 years ago

flightdragonz commented 2 years ago

Hi, saw a similar/same issue which was closed previously but I think it has happened again.. closed issue: TargetManager stuck on "Scanning network" (Closed)

Targetmanager logs:

Broadcasting to Hack Manager

Found new host: hong-fang-tea

Broadcasting host: hong-fang-tea

Broadcasting to Thread Manager

Broadcasting to Hack Manager

Found new host: harakiri-sushi

Broadcasting host: harakiri-sushi

Broadcasting to Thread Manager

Broadcasting to Hack Manager

Found new host: iron-gym

Broadcasting host: iron-gym

Broadcasting to Thread Manager

Broadcasting to Hack Manager

Found new host: nectar-net

Broadcasting host: nectar-net

Broadcasting to Thread Manager

Broadcasting to Hack Manager

Found new host: phantasy

Broadcasting host: phantasy

Broadcasting to Thread Manager

Broadcasting to Hack Manager

Found new host: crush-fitness

Broadcasting host: crush-fitness

Broadcasting to Thread Manager

Broadcasting to Hack Manager

Found new host: omega-net

Broadcasting host: omega-net

Broadcasting to Thread Manager

Broadcasting to Hack Manager

Found new host: the-hub

Broadcasting host: the-hub

Broadcasting to Thread Manager

Broadcasting to Hack Manager

Found new host: johnson-ortho

Broadcasting host: johnson-ortho

Broadcasting to Thread Manager

Broadcasting to Hack Manager

Found new host: avmnite-02h

Broadcasting host: avmnite-02h

Broadcasting to Thread Manager

Broadcasting to Hack Manager

Scanning network

Scanning network

Scanning network

Scanning network

Scanning network

Scanning network

Scanning network

Scanning network

Scanning network

Scanning network

Terminal: (Console.js printRunningHacks

[home ~/]> run /Orchestrator/Console.js printRunningHacks

Running script with 1 thread(s), pid 521 and args: ["printRunningHacks"].

/Orchestrator/Console.js: Printing Running Hacks.

[home ~/]>

Threadmanager logs:

Deallocated 3 threads of pserv-23

Received thread freeing request from hackConductor(Origin ID: 86)

Deallocated 49 threads of pserv-23

Deallocated 73 threads of pserv-24

Deallocated 9 threads of joesguns

Deallocated 44 threads of pserv-0

Deallocated 38 threads of pserv-5

Received thread freeing request from hackConductor(Origin ID: 81)

Deallocated 13 threads of pserv-1

Deallocated 18 threads of max-hardware

Deallocated 73 threads of pserv-2

Deallocated 73 threads of pserv-3

Deallocated 73 threads of pserv-4

Deallocated 9 threads of hong-fang-tea

Deallocated 9 threads of harakiri-sushi

Deallocated 18 threads of iron-gym

Deallocated 9 threads of nectar-net

Deallocated 18 threads of phantasy

Deallocated 18 threads of omega-net

Deallocated 18 threads of the-hub

Deallocated 36 threads of avmnite-02h

Received thread freeing request from hackConductor(Origin ID: 78)

Deallocated 27 threads of pserv-7

Deallocated 5 threads of pserv-8

Deallocated 4 threads of pserv-9

Deallocated 1 threads of foodnstuff

Deallocated 8 threads of pserv-10

Deallocated 18 threads of pserv-12

Deallocated 29 threads of pserv-13

Deallocated 18 threads of neo-net

Deallocated 36 threads of pserv-14

Deallocated 36 threads of pserv-15

Deallocated 27 threads of pserv-16

Deallocated 23 threads of pserv-17

Deallocated 11 threads of pserv-22

Updating threads amount on pserv-7

Got new host: pserv-7 with 73 threads

Received thread freeing request from hackConductor(Origin ID: 74)

Deallocated 31 threads of pserv-8

Deallocated 24 threads of pserv-9

Updating threads amount on pserv-8

Got new host: pserv-8 with 73 threads

Received thread freeing request from hackConductor(Origin ID: 75)

Deallocated 8 threads of pserv-9

Deallocated 9 threads of pserv-16

Deallocated 11 threads of pserv-22

Deallocated 35 threads of pserv-5

Received thread freeing request from hackConductor(Origin ID: 83)

Deallocated 3 threads of pserv-11

Deallocated 18 threads of zer0

Deallocated 18 threads of pserv-12

message manager: disableLog: Disabled logging for sleep

my list of servers:

getServers.js: pserv-9 | 64

getServers.js: pserv-10 | 64

getServers.js: pserv-11 | 64

getServers.js: pserv-12 | 64

getServers.js: pserv-13 | 64

getServers.js: pserv-14 | 64

getServers.js: pserv-15 | 64

getServers.js: pserv-16 | 64

getServers.js: pserv-17 | 64

getServers.js: pserv-18 | 64

getServers.js: pserv-19 | 64

getServers.js: pserv-20 | 64

getServers.js: pserv-21 | 64

getServers.js: pserv-22 | 128

getServers.js: pserv-23 | 128

getServers.js: pserv-24 | 128

getServers.js: pserv-0 | 128

getServers.js: pserv-1 | 128

getServers.js: pserv-2 | 128

getServers.js: pserv-3 | 128

getServers.js: pserv-4 | 128

getServers.js: pserv-5 | 128

getServers.js: pserv-6 | 128

getServers.js: pserv-7 | 128

getServers.js: pserv-8 | 128

Console.js threadsUse

[home ~/]> run /Orchestrator/Console.js threadsUse

Running script with 1 thread(s), pid 525 and args: ["threadsUse"].

/Orchestrator/Console.js: Printing Threads status.

/Orchestrator/ThreadManager/manager.js: n00dles             : [||||||||||||||||||||] (2/2)  0 GiB/4 GiB

/Orchestrator/ThreadManager/manager.js: pserv-9             : [--------------------] (0/36)  0 GiB/64 GiB

/Orchestrator/ThreadManager/manager.js: foodnstuff          : [--------------------] (0/9)  0 GiB/16 GiB

/Orchestrator/ThreadManager/manager.js: pserv-10            : [--------------------] (0/36)  0 GiB/64 GiB

/Orchestrator/ThreadManager/manager.js: pserv-11            : [|||||||||-----------] (16/36)  0 GiB/64 GiB

/Orchestrator/ThreadManager/manager.js: zer0                : [--------------------] (0/18)  0 GiB/32 GiB

/Orchestrator/ThreadManager/manager.js: pserv-12            : [--------------------] (0/36)  0 GiB/64 GiB

/Orchestrator/ThreadManager/manager.js: pserv-13            : [||||----------------] (7/36)  0 GiB/64 GiB

/Orchestrator/ThreadManager/manager.js: neo-net             : [--------------------] (0/18)  0 GiB/32 GiB

/Orchestrator/ThreadManager/manager.js: pserv-14            : [--------------------] (0/36)  0 GiB/64 GiB

/Orchestrator/ThreadManager/manager.js: pserv-15            : [--------------------] (0/36)  0 GiB/64 GiB

/Orchestrator/ThreadManager/manager.js: pserv-16            : [--------------------] (0/36)  0 GiB/64 GiB

/Orchestrator/ThreadManager/manager.js: pserv-17            : [--------------------] (0/36)  0 GiB/64 GiB

/Orchestrator/ThreadManager/manager.js: CSEC                : [--------------------] (0/4)  0 GiB/8 GiB

/Orchestrator/ThreadManager/manager.js: pserv-18            : [--------------------] (0/36)  0 GiB/64 GiB

/Orchestrator/ThreadManager/manager.js: pserv-19            : [--------------------] (0/36)  0 GiB/64 GiB

/Orchestrator/ThreadManager/manager.js: silver-helix        : [--------------------] (0/36)  0 GiB/64 GiB

/Orchestrator/ThreadManager/manager.js: pserv-20            : [--------------------] (0/36)  0 GiB/64 GiB

/Orchestrator/ThreadManager/manager.js: pserv-21            : [--------------------] (0/36)  0 GiB/64 GiB

/Orchestrator/ThreadManager/manager.js: pserv-22            : [--------------------] (0/73)  0 GiB/128 GiB

/Orchestrator/ThreadManager/manager.js: sigma-cosmetics     : [--------------------] (0/9)  0 GiB/16 GiB

/Orchestrator/ThreadManager/manager.js: pserv-23            : [--------------------] (0/73)  0 GiB/128 GiB

/Orchestrator/ThreadManager/manager.js: pserv-24            : [--------------------] (0/73)  0 GiB/128 GiB

/Orchestrator/ThreadManager/manager.js: joesguns            : [--------------------] (0/9)  0 GiB/16 GiB

/Orchestrator/ThreadManager/manager.js: pserv-0             : [--------------------] (0/73)  0 GiB/128 GiB

/Orchestrator/ThreadManager/manager.js: pserv-1             : [--------------------] (0/73)  0 GiB/128 GiB

/Orchestrator/ThreadManager/manager.js: max-hardware        : [--------------------] (0/18)  0 GiB/32 GiB

/Orchestrator/ThreadManager/manager.js: pserv-2             : [--------------------] (0/73)  0 GiB/128 GiB

/Orchestrator/ThreadManager/manager.js: pserv-3             : [--------------------] (0/73)  0 GiB/128 GiB

/Orchestrator/ThreadManager/manager.js: pserv-4             : [--------------------] (0/73)  0 GiB/128 GiB

/Orchestrator/ThreadManager/manager.js: hong-fang-tea       : [--------------------] (0/9)  0 GiB/16 GiB

/Orchestrator/ThreadManager/manager.js: harakiri-sushi      : [--------------------] (0/9)  0 GiB/16 GiB

/Orchestrator/ThreadManager/manager.js: iron-gym            : [--------------------] (0/18)  0 GiB/32 GiB

/Orchestrator/ThreadManager/manager.js: nectar-net          : [--------------------] (0/9)  0 GiB/16 GiB

/Orchestrator/ThreadManager/manager.js: phantasy            : [--------------------] (0/18)  0 GiB/32 GiB

/Orchestrator/ThreadManager/manager.js: omega-net           : [--------------------] (0/18)  0 GiB/32 GiB

/Orchestrator/ThreadManager/manager.js: the-hub             : [--------------------] (0/18)  0 GiB/32 GiB

/Orchestrator/ThreadManager/manager.js: avmnite-02h         : [--------------------] (0/36)  0 GiB/64 GiB

/Orchestrator/ThreadManager/manager.js: pserv-5             : [--------------------] (0/73)  0 GiB/128 GiB

/Orchestrator/ThreadManager/manager.js: pserv-6             : [|-------------------] (3/73)  0 GiB/128 GiB

/Orchestrator/ThreadManager/manager.js: pserv-7             : [--------------------] (0/73)  0 GiB/128 GiB

/Orchestrator/ThreadManager/manager.js: pserv-8             : [--------------------] (0/73)  0 GiB/128 GiB
HtheChemist commented 2 years ago

I think you are simply at a point where the Target Manager does not find new target, either because your probably because your hacking is still not high enough. I will add a message stating that it did not find anything.

flightdragonz commented 2 years ago

So the hacking jus stops completely? Cause it was working fine for a while with full usage on almost all server and all of a sudden, the hacking jus stops all of a sudden..

HtheChemist commented 2 years ago

It seems that it is the Hack Manager that get stuck waiting for a ready message from a conductor. This in turn is due to a delay from the Thread Manager, I am still investigating why.

HtheChemist commented 2 years ago

I reworked the way the MessageManager work and added timeout check to conductor and manager to ensure that they don't get stuck anymore.