Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

process can't be killed for a long time #479

Open
issaxyz opened this issue Jun 10, 2021 · 2 comments
Open

process can't be killed for a long time #479

issaxyz opened this issue Jun 10, 2021 · 2 comments

Comments

@issaxyz
Copy link

issaxyz commented Jun 10, 2021

I used pkill bchd command, but the server seems turn in to a zombie process.
OS: ubuntu 18.04

bchd --version

bchd version 0.18.0

startup script

bchd
--rpclisten=0.0.0.0
--grpclisten=0.0.0.0
--addrindex --txindex --slpindex
-b=./ -C=./config.ini

config.ini

listen=127.0.0.1
rpclisten=0.0.0.0
maxpeers=12
maxpeersperip=1
rpclimituser=xxxxx
rpclimitpass=xxxxx
rpcuser=xxxxx
rpcpass=xxxxx
rpcquirks=1
notls=1

tail -f $WORK_HOME/nohup.out

2021-06-09 16:12:28.196 [INF] SRVR: Stopped: cpuMiner
2021-06-09 16:12:28.196 [INF] SRVR: Stopping: rpcServer
2021-06-09 16:12:28.196 [WRN] RPCS: RPC server shutting down
2021-06-09 16:12:28.197 [INF] RPCS: RPC server shutdown complete
2021-06-09 16:12:28.197 [INF] SRVR: Stopped: rpcServer
2021-06-09 16:12:28.197 [INF] SRVR: Saving fee estimate to database
2021-06-09 16:12:32.417 [INF] SRVR: Fee estimate save complete
2021-06-09 16:12:32.417 [INF] SRVR: Waiting for server waitgroup to complete
2021-06-10 10:15:09.020 [INF] BCHD: Received signal (terminated). Already shutting down...
2021-06-10 10:21:03.765 [INF] BCHD: Received signal (terminated). Already shutting down...

top

%Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 4039088 total, 326820 free, 2243412 used, 1468856 buff/cache
KiB Swap: 0 total, 0 free, 0 used. 2438384 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
739 root 20 0 2360880 1.978g 7856 S 0.0 51.4 7284:52 bchd

@zquestz
Copy link
Contributor

zquestz commented Jun 11, 2021

We have had some issues with shutdown. I am also seeing it on my node. When I run trace logs, I get a few peers that don't disconnect and continue to send ping/pong messages. The only way to terminate the process is to kill -9.

@issaxyz
Copy link
Author

issaxyz commented Jun 17, 2021

We have had some issues with shutdown. I am also seeing it on my node. When I run trace logs, I get a few peers that don't disconnect and continue to send ping/pong messages. The only way to terminate the process is to kill -9.

thx, I did what you suggest, only need to resync a few blocks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants