| Summary: | Frequent pseudo aborts with tcp-wrappers, complains about hardlinks in packages-split | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Yocto Project Subprojects] Pseudo | Reporter: | Ernst Persson <ernstp> | ||||
| Component: | pseudo | Assignee: | Steve Sakoman <steve> | ||||
| Status: | RESOLVED INVALID | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Medium+ | CC: | randy.macleod, richard.purdie, yp.pseudo.watcher, yp.watcher | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 3.1.14 | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
|
Description
Ernst Persson
2021-11-18 15:47:20 UTC
I'd like to find some way to reproduce this issue, as I've never seen it in my own testing. I do regular builds with layer sets quite similar to what you are using, though I mostly use the poky distro (or a distro that inherits poky). So your distro is one potential area to investigate. Also none of my testing uses an azure host machine, so that is another area of difference. Have you tried using other host machines to see if it might be azure related? Looks like you need to do two builds in a row without sstate caching you.
So build, tweak something, build again. The error comes from:
def exec_func(func, d, dirs = None):
<...>
cleandirs = flags.get('cleandirs') if flags else None
if cleandirs:
for cdir in d.expand(cleandirs).split():
+ bb.warn("My extra print: running cleandir %s" % cdir)
bb.utils.remove(cdir, True)
bb.utils.mkdirhier(cdir)
So this "rm -rf" is running under Pseudo... seems a bit meaningless? Can it be disabled?
I actually don't think this is Dunfell specific, it's probably the same on all up to date Yocto.. ? I just managed to trigger this somehow.
There's a been a couple of mentions of similar problems:
https://lists.yoctoproject.org/g/yocto/topic/78528061?p=Created,,,20,2,0,0::recentpostdate%2Fsticky,,,20,2,40,78528061
My distro is based on Poky.
Yeah I also suspected Azure a bit. Looks like a normal ext4 filesystem etc, couldn't find anything very special about it... No Docker involved. Decently modern kernel.
Created attachment 4844 [details]
Patch to disable pseudo during bb.utils.remove()
This patch solve my issue. Ignore the patch. This seems to be caused by adding --enable-xattrdb to pseudo. The pseudo database is missing a lot of files. xattrdb is an experimental feature in pseudo and known not to work well, we'd not recommend it. |