Nodemanager can't be killed

pkill client nodemanager dfx does not work, does anyone have any other suggestions?

42620 ttys006 0:00.00 grep nodemanager
AdamT-F0122: adam.tothfejel$ sudo pkill client nodemanager dfx
AdamT-F0122: adam.tothfejel$ ps -ax | grep nodemanager
42627 ttys006 0:00.00 grep nodemanager
AdamT-F0122: adam.tothfejel$ sudo pkill client nodemanager dfx
AdamT-F0122: adam.tothfejel$ ps -ax | grep nodemanager
42631 ttys006 0:00.00 grep nodemanager
AdamT-F0122: adam.tothfejel$ sudo pkill client nodemanager dfx
AdamT-F0122: adam.tothfejel$ ps -ax | grep nodemanager
42635 ttys006 0:00.00 grep nodemanager
AdamT-F0122: adam.tothfejel$ sudo pkill client nodemanager dfx
AdamT-F0122: adam.tothfejel$ ps -ax | grep nodemanager
42639 ttys006 0:00.00 grep nodemanager

You could try killall

killall dfx replica nodemanager

Nope, does not work.

AdamT-F0122:adam.tothfejel$ sudo killall dfx client nodemanager
Password:
No matching processes were found
AdamT-F0122: adam.tothfejel$ sudo dfx stop
AdamT-F0122: adam.tothfejel$ ps aux | grep 8000
adam.tothfejel 43910 0.0 0.0 4267972 652 s005 R+ 2:50PM 0:00.00 grep 8000

Can you get the name of the process running on that port? If nodemanager is running, killall should find it.

Thank you this ended up helping. What is the easiest way for me to see all the processes that Dfinity spawns so I can monitor them?

There should only be dfx, replica (formerly client), and nodemanager running.

Running dfx start --background then ps (or ps -a in another terminal if not using the background flag) will show these.

Ok thank you, thanks Ori

If dfx stop isn’t killing these successfully it may be worth you opening an issue at support@dfinity.org

Will do because it isn’t

1 Like

(You shouldn’t really need to run dfx with elevated privileges either so maybe try doing so without using sudo).

Ok thank you, do you know why I might be getting this issue?

WARN Could not perform query on canister: IC0301: Canister ic:BF33404EA7B97A08AA not found, Application: Http Handler

See here:

Note; we are getting rid of the node manager locally as it doesn’t help developers. So dfx start will not use it (in the next release 0.5.1). Cheers

2 Likes