<div dir="ltr"><div>I've tried again with the change from Alex (without additional SRCREV bump) on ubuntu-14.04</div><div><br></div><div>To make it simple I've triggered the build of just to recipes (which caused "tried to close client 0 (highest is 1)" before:</div><div><br></div>$ bitbake tzdata update-rc.d<br><div>and again I quickly got:</div><div><div>23G tzdata/2018c-r0/pseudo/</div><div>24G update-rc.d/0.7-r5/pseudo/</div></div><div><br></div><div>There is nothing special in the pseudo.log before this <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">"tried to close client 0 (highest is 1)"</span></div><div><div>==> tzdata/2018c-r0/pseudo/pseudo.log <==</div><div>debug_logfile: fd 2</div><div>pid 8489 [parent 8484], doing new pid setup and server start</div><div>Setup complete, sending SIGUSR1 to pid 8484.</div><div>tried to close client 0 (highest is 1)</div><div>tried to close client 0 (highest is 1)</div><div><br></div><div>==> update-rc.d/0.7-r5/pseudo/pseudo.log <==</div><div>debug_logfile: fd 2</div><div>pid 8488 [parent 8481], doing new pid setup and server start</div><div>Setup complete, sending SIGUSR1 to pid 8481.</div><div>tried to close client 0 (highest is 1)</div><div>tried to close client 0 (highest is 1)</div></div><div><br></div><div>And there is actually nothing else after those 3 lines at the beginning until I've killed the bitbake build (which didn't kill pseudo itself) and then killed both pseudo processes - which resulted with left-over bitbake-worker starting 2 new pseudo processes which kept spamming "<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">tried to close client 0 (highest is 1)" after initial setup:</span></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><div>$grep -v "^tried to close client 0 (highest is 1)$" */*/pseudo/pseudo.log<br></div><div><div>tzdata/2018c-r0/pseudo/pseudo.log:debug_logfile: fd 2</div><div>tzdata/2018c-r0/pseudo/pseudo.log:pid 8489 [parent 8484], doing new pid setup and server start</div><div>tzdata/2018c-r0/pseudo/pseudo.log:Setup complete, sending SIGUSR1 to pid 8484.</div><div>tzdata/2018c-r0/pseudo/pseudo.log:Received signal 15, quitting.</div><div>tzdata/2018c-r0/pseudo/pseudo.log:db cleanup for server shutdown, 19:10:01.424</div><div>tzdata/2018c-r0/pseudo/pseudo.log:memory-to-file backup complete, 19:10:01.436.</div><div>tzdata/2018c-r0/pseudo/pseudo.log:db cleanup finished, 19:10:01.436</div><div>tzdata/2018c-r0/pseudo/pseudo.log:debug_logfile: fd 2</div><div>tzdata/2018c-r0/pseudo/pseudo.log:pid 11205 [parent 11199], doing new pid setup and server start</div><div>tzdata/2018c-r0/pseudo/pseudo.log:Setup complete, sending SIGUSR1 to pid 11199.</div><div>update-rc.d/0.7-r5/pseudo/pseudo.log:debug_logfile: fd 2</div><div>update-rc.d/0.7-r5/pseudo/pseudo.log:pid 8488 [parent 8481], doing new pid setup and server start</div><div>update-rc.d/0.7-r5/pseudo/pseudo.log:Setup complete, sending SIGUSR1 to pid 8481.</div><div>update-rc.d/0.7-r5/pseudo/pseudo.log:Received signal 15, quitting.</div><div>update-rc.d/0.7-r5/pseudo/pseudo.log:db cleanup for server shutdown, 19:10:01.423</div><div>update-rc.d/0.7-r5/pseudo/pseudo.log:memory-to-file backup complete, 19:10:01.436.</div><div>update-rc.d/0.7-r5/pseudo/pseudo.log:db cleanup finished, 19:10:01.436</div><div>update-rc.d/0.7-r5/pseudo/pseudo.log:debug_logfile: fd 2</div><div>update-rc.d/0.7-r5/pseudo/pseudo.log:pid 11212 [parent 11200], doing new pid setup and server start</div><div>update-rc.d/0.7-r5/pseudo/pseudo.log:Setup complete, sending SIGUSR1 to pid 11200.</div></div><div><br></div><div><div>$ du -hs */*/pseudo/</div><div>28G tzdata/2018c-r0/pseudo/</div><div>28G update-rc.d/0.7-r5/pseudo/</div></div><div><br></div><div>Without --enable-epoll in pseudo.inc tzdata built fine and pseudo.log is very short:</div><div><div>debug_logfile: fd 2</div><div>pid 14630 [parent 14629], doing new pid setup and server start</div><div>14630: new pid: 14630 [pseudo]</div><div>14630: Setup complete, sending SIGUSR1 to pid 14629.</div><div>14630: path mismatch [2 links]: ino 282238092 db '/run/shm/sem.mp-yluz7s8j' req '/run/shm/sem.5mP74h'.</div><div>14630: db cleanup for server shutdown, 20:19:27.475</div><div>14630: memory-to-file backup complete, 20:19:27.475.</div><div>14630: db cleanup finished, 20:19:27.475</div></div><div><br></div><div>Shouldn't PSEUDO_DEBUG=4 in the environment generate a bit more verbose log?</div><div><br></div><div>I've also tried to add it in <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">FAKEROOTENV (because pseudo seems to lock up before run.do_install is executed, so the export there probably didn't happen soon enough, but then even when it worked without --enable-epoll the log wasn't any bigger).</span></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><div><div>meta/conf/bitbake.conf:export PSEUDO_DEBUG = "4"</div><div>meta/conf/bitbake.conf:FAKEROOTBASEENV = "PSEUDO_BINDIR=${PSEUDO_SYSROOT}${bindir_native} PSEUDO_LIBDIR=${PSEUDO_SYSROOT}${prefix_native}/lib/pseudo/lib PSEUDO_PREFIX=${PSEUDO_SYSROOT}${prefix_native} PSEUDO_DISABLED=1 PSEUDO_DEBUG=4"</div><div>meta/conf/bitbake.conf:FAKEROOTENV = "PSEUDO_PREFIX=${PSEUDO_SYSROOT}${prefix_native} PSEUDO_LOCALSTATEDIR=${PSEUDO_LOCALSTATEDIR} PSEUDO_PASSWD=${PSEUDO_PASSWD} PSEUDO_NOSYMLINKEXP=1 PSEUDO_DEBUG=4 PSEUDO_DISABLED=0"</div></div><div><br></div><div>Regards,</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Feb 18, 2018 at 12:43 PM, Martin Jansa <span dir="ltr"><<a href="mailto:martin.jansa@gmail.com" target="_blank">martin.jansa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">The do_install tasks failing with exit code '134'/SIGABRT were caused by left over pseudo processes from previous builds still holding the pseudo.lock.</span><br><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><div>Manually killing those (still spinning at around 90% CPU for last 2 days) resolved the do_install failures.</div><div><br></div><div>It also explains the lack of log.do_install files, because do_install failed before it even properly started.</div><div><br></div><div>Regards,</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Feb 17, 2018 at 9:17 PM, Seebs <span dir="ltr"><<a href="mailto:seebs@seebs.net" target="_blank">seebs@seebs.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Sat, 17 Feb 2018 15:28:55 +0200<br>
Alexander Kanavin <<a href="mailto:alexander.kanavin@linux.intel.com" target="_blank">alexander.kanavin@linux.intel<wbr>.com</a>> wrote:<br>
<br>
> For me, with epoll enabled:<br>
><br>
> b6a015a works<br>
> 23f089f and 26e30fa both lock up<br>
<br>
</span>Huh. It's possible that the initial "don't try to close fd 0" was<br>
correct, and the real problem is that the attempt is getting made<br>
mistakenly. I'll study that more; the epoll code was a contribution and<br>
I may not have fully understood it.<br>
<span class="m_-3203429403165069772HOEnZb"><font color="#888888"><br>
-s<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>