In case there is no server running (daemon), and variable PRSERV_HOST is present, when running a'bitbake <target>' it hangs with the following log: Delaying shutdown due to active processes which appear to be holding bitbake.lock: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python 18299 lsandov1 12u REG 8,4 0 30090935242 /home/lsandov1/poky/build/bitbake.lock . . . Steps to reproduce 1. echo "PRSERV_HOST=\"localhost:8585\"" >> conf/local.conf #make sure you do not run the bitbake-prserv or the daemon is not already running (ps aux | grep bitbake-prserv) 2. bitbake <anytarget> What it is expected is to exit immediately to the command line, instead of showing the log and hanging there.
Also, if one suspends (control + z) when it is hanging, multiple bitbake-prserv process are observed: lsandov1@yctb05:~/poky/build> ps axu | grep bitbake lsandov1 18248 0.3 0.0 124392 27140 pts/34 T 13:09 0:02 python /home/lsandov1/poky/bitbake/bin/bitbake prserv-test lsandov1 18268 0.1 0.0 196428 30032 pts/34 T 13:09 0:00 python /home/lsandov1/poky/bitbake/bin/bitbake prserv-test lsandov1 18299 0.8 0.0 211084 43500 pts/34 Tl 13:09 0:05 python /home/lsandov1/poky/bitbake/bin/bitbake prserv-test . . . .
This is not reproducible on master anymore. It seems this change in cooker solved the issue: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/bitbake/lib/prserv/serv.py?id=85256c8fa986f2a3258e75a22bb8d0656ffa41bf It is not reproducible in master anymore but if return to a commit before the change in cooker, the issue is there.
verified as per above comments.