bcclient issue TS-212
-
- New here
- Posts: 9
- Joined: Tue Nov 22, 2011 11:21 pm
bcclient issue TS-212
I have TS-212 that runs great except when the bcclient process runs away. (Then its a brick)
I read another thread listing firmware downgrades to solve the issue, but that thread was 8 years old.
This unit has the latest firmware they released for the TS-212 Firmware: 4.3.3.1432
I am not sure what this process really does other than eat 70-93% of my CPU.
What calls bcclient?
and do I really need it?
I read another thread listing firmware downgrades to solve the issue, but that thread was 8 years old.
This unit has the latest firmware they released for the TS-212 Firmware: 4.3.3.1432
I am not sure what this process really does other than eat 70-93% of my CPU.
What calls bcclient?
and do I really need it?
The More I learn The Less I Know...
-
- Experience counts
- Posts: 1081
- Joined: Thu Aug 24, 2017 10:28 pm
Re: bcclient issue TS-212
According to some people, this process is the QNAP program responsible for communicating with Qfinder.
You could try to kill it, if you don't need to use Qfinder it wouldn't hurt anything, but it will be respawned automatically.
crazy process: /sbin/bcclient
You could try to kill it, if you don't need to use Qfinder it wouldn't hurt anything, but it will be respawned automatically.
crazy process: /sbin/bcclient
-
- New here
- Posts: 9
- Joined: Tue Nov 22, 2011 11:21 pm
Re: bcclient issue TS-212
Thanks for the reply.
Seems like that would be a settable option.
Seems like that would be a settable option.
The More I learn The Less I Know...
-
- New here
- Posts: 9
- Joined: Tue Nov 22, 2011 11:21 pm
Re: bcclient issue TS-212
F.Y.I.
I just added an hourly cron job to the admin crontab.
kill $(ps -ef | grep "bcclient" | grep -v grep | awk '{print $1}')
Now it should check every hour for the bcclient process and kill it if it finds it...
I just added an hourly cron job to the admin crontab.
kill $(ps -ef | grep "bcclient" | grep -v grep | awk '{print $1}')
Now it should check every hour for the bcclient process and kill it if it finds it...
The More I learn The Less I Know...
-
- Experience counts
- Posts: 1081
- Joined: Thu Aug 24, 2017 10:28 pm
Re: bcclient issue TS-212
Yeah, alternatively you could use daemon_mgr to shut bcclient down permanently and prevent automatic respawns (which otherwise happen when you kill it with kill).
You only need to do this once after the NAS has booted up.
(replace 'stop' with 'start' if you need to bring it up again)
I confirmed that Qfinder is unable to locate the NAS when bcclient is not running.
Code: Select all
# /sbin/daemon_mgr bcclient stop /sbin/bcclient
(replace 'stop' with 'start' if you need to bring it up again)
I confirmed that Qfinder is unable to locate the NAS when bcclient is not running.
Last edited by Mousetick on Thu Dec 24, 2020 3:52 am, edited 1 time in total.
- OneCD
- Guru
- Posts: 12037
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: bcclient issue TS-212
Or use the much shorter:
Code: Select all
killall bcclient
Code: Select all
chmod -x /sbin/bcclient
-
- Starting out
- Posts: 26
- Joined: Mon Oct 21, 2013 9:44 pm
Re: bcclient issue TS-212
I have an TS-419pII with the same bcclient issue. I tried this daemon_mgr code. But I got a replay thatMousetick wrote: ↑Thu Dec 24, 2020 3:51 am Yeah, alternatively you could use daemon_mgr to shut bcclient down permanently and prevent automatic respawns (which otherwise happen when you kill it with kill).
You only need to do this once after the NAS has booted up.Code: Select all
# /sbin/daemon_mgr bcclient stop /sbin/bcclient
(replace 'stop' with 'start' if you need to bring it up again)
I confirmed that Qfinder is unable to locate the NAS when bcclient is not running.
Code: Select all
/sbin/daemon_mgr
-
- Experience counts
- Posts: 1081
- Joined: Thu Aug 24, 2017 10:28 pm
Re: bcclient issue TS-212
I guess the firmware on your NAS is too old and it doesn't have a daemon_mgr command?moserroger wrote: ↑Mon May 03, 2021 4:38 pm I have an TS-419pII with the same bcclient issue. I tried this daemon_mgr code. But I got a replay thatwasn't found. How to make it work?Code: Select all
/sbin/daemon_mgr
Try the command suggested by @OneCD two posts above:
Code: Select all
killall bcclient
-
- Starting out
- Posts: 26
- Joined: Mon Oct 21, 2013 9:44 pm
Re: bcclient issue TS-212
Firmware is: 4.3.3.1624
What about respawn?Mousetick wrote: ↑Mon May 03, 2021 10:40 pm Try the command suggested by @OneCD two posts above:Code: Select all
killall bcclient
-
- Experience counts
- Posts: 1081
- Joined: Thu Aug 24, 2017 10:28 pm
Re: bcclient issue TS-212
Does it actually respawn?
To block execution:
Code: Select all
# chmod -x /sbin/bcclient
# killall bcclient
Code: Select all
# chmod +x /sbin/bcclient
Last edited by Mousetick on Tue May 04, 2021 2:19 am, edited 1 time in total.
-
- Starting out
- Posts: 26
- Joined: Mon Oct 21, 2013 9:44 pm
Re: bcclient issue TS-212
I will try and see.
Update: it returned:
killall: /sbin/bcclient: no process killed
Will I have to kill it again after every restart?Mousetick wrote: ↑Tue May 04, 2021 1:10 am To block execution:To undo:Code: Select all
# chmod -x /sbin/bcclient # killall /sbin/bcclient
or simply restart NAS.Code: Select all
# chmod +x /sbin/bcclient
Can I add the code to autostart.sh?
-
- Experience counts
- Posts: 1081
- Joined: Thu Aug 24, 2017 10:28 pm
Re: bcclient issue TS-212
Yes, unless you add it to autorun.sh.
Yes. Beware you will no longer be able to use QFinder to locate or connect to the NAS, in case it matters.Can I add the block execution to autostart.sh?
-
- Starting out
- Posts: 26
- Joined: Mon Oct 21, 2013 9:44 pm
Re: bcclient issue TS-212
Code: Select all
# killall /sbin/bcclient
killall: /sbin/bcclient: no process killed
-
- Experience counts
- Posts: 1081
- Joined: Thu Aug 24, 2017 10:28 pm
-
- Starting out
- Posts: 26
- Joined: Mon Oct 21, 2013 9:44 pm
Re: bcclient issue TS-212
Worked! Thank you!Mousetick wrote: ↑Tue May 04, 2021 2:19 am Yes, my bad sorry. Typo error.
Try again:Code: Select all
# killall bcclient