Pseudo abort errors

Pseudo abort errors

[arthur52666]

[-- Attachment #1: Type: text/plain, Size: 6198 bytes --]

H i Experts,

I am building Embedded Linux image based on Yocto framework. The image building involves a lot of recipe execution.

when building the image I always get below pseudo abort error :

> 
> 
> 
> Pseudo log:
> 
> 
> 
> path mismatch [1 link]: ino 147610407 db '/tmp/sh-thd.VPxkGG' req
> '/tmp/sh-thd.4Z7cxB'.
> 
> 
> 
> 
> 
> 

I tried to build the image multiple times, 100% got the error every time, but the error was reported at different recipe every time. I've read the wiki page about them, but I'm not sure exactly what we are doing wrong that is making this happen. The files listed in the error log should be shell tmp files.

The most recently I built the image, the error was reported at autoconf-archive recipe. Below is the build error log:

> 
> 
> 
> ecs-915:/shr/router/yocto/poky > cat
> /shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/pseudo//pseudo.log
> 
> 
> 
> 
> debug_logfile: fd 2
> 
> 
> 
> pid 1068009 [parent 1068008], doing new pid setup and server start
> 
> 
> 
> Setup complete, sending SIGUSR1 to pid 1068008.
> 
> 
> 
> path mismatch [1 link]: ino 147610407 db '/tmp/sh-thd.VPxkGG' req
> '/tmp/sh-thd.4Z7cxB'.
> 
> 
> 
> db cleanup for server shutdown, 11:03:48.420
> 
> 
> 
> memory-to-file backup complete, 11:03:48.420.
> 
> 
> 
> db cleanup finished, 11:03:48.420
> 
> 
> 
> ecs-915:/shr/router/yocto/poky >
> 
> 
> 
> ecs-915:/shr/router/yocto/poky >
> 
> 
> 
> ecs-915:/shr/router/yocto/poky >
> 
> 
> 
> ecs-915:/shr/router/yocto/poky >
> 
> 
> 
> ecs-915:/shr/router/yocto/poky > cat
> /shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/temp/log.do_package_write_ipk.1068364
> 
> 
> 
> 
> DEBUG: Executing python function extend_recipe_sysroot
> 
> 
> 
> NOTE: Direct dependencies are
> ['virtual:native:/shr/router/yocto/poky/../poky/meta/recipes-devtools/opkg-utils/opkg-utils_0.5.0.bb:do_populate_sysroot',
> 'virtual:native:/shr/router/yocto/poky/../poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot',
> 'virtual:native:/shr/router/yocto/poky/../poky/meta/recipes-extended/xz/xz_5.2.6.bb:do_populate_sysroot']
> 
> 
> 
> 
> NOTE: Installed into sysroot: ['opkg-utils-native', 'perl-native',
> 'make-native']
> 
> 
> 
> NOTE: Skipping as already exists in sysroot: ['pseudo-native',
> 'xz-native', 'libtool-native', 'gettext-minimal-native', 'zlib-native',
> 'gdbm-native', 'texinfo-dummy-native']
> 
> 
> 
> DEBUG: sed -e
> 's:^[^/]*/:/shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/recipe-sysroot-native/:g'
> /shr/router/build/tmp/sysroots-components/x86_64/perl-native/fixmepath |
> xargs sed -i -e
> 's:FIXMESTAGINGDIRTARGET:/shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/recipe-sysroot:g;
> s:FIXMESTAGINGDIRHOST:/shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/recipe-sysroot-native:g'
> -e
> 's:FIXME_PSEUDO_SYSROOT:/shr/router/build/tmp/sysroots-components/x86_64/pseudo-native:g'
> -e 's:FIXME_HOSTTOOLS_DIR:/shr/router/build/tmp/hosttools:g' -e
> 's:FIXME_PKGDATA_DIR:/shr/router/build/tmp/pkgdata/axel-qca:g' -e
> 's:FIXME_PSEUDO_LOCALSTATEDIR:/shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/pseudo/:g'
> -e
> 's:FIXME_LOGFIFO:/shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/temp/fifo.1068364:g'
> 
> 
> 
> 
> DEBUG: Python function extend_recipe_sysroot finished
> 
> 
> 
> DEBUG: Executing python function sstate_task_prefunc
> 
> 
> 
> DEBUG: Python function sstate_task_prefunc finished
> 
> 
> 
> DEBUG: Executing python function do_package_write_ipk
> 
> 
> 
> DEBUG: Executing python function read_subpackage_metadata
> 
> 
> 
> DEBUG: Python function read_subpackage_metadata finished
> 
> 
> 
> DEBUG: Executing python function do_package_ipk
> 
> 
> 
> NOTE: Not creating empty archive for autoconf-archive-src-2022.02.11-r0
> 
> 
> 
> ERROR: Fatal errors occurred in subprocesses:
> 
> 
> 
> Command
> 'PATH="/shr/router/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/shr/router/yocto/poky/scripts:/shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/recipe-sysroot-native/usr/bin/allarch-shr-linux:/shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/recipe-sysroot/usr/bin/crossscripts:/shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/recipe-sysroot-native/usr/sbin:/shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/recipe-sysroot-native/usr/bin:/shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/recipe-sysroot-native/sbin:/shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/recipe-sysroot-native/bin:/shr/router/yocto/poky/bitbake/bin:/shr/router/build/tmp/hosttools"
> opkg-build -Z xz -a "--memlimit=50% --threads=16" autoconf-archive-doc
> /shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/deploy-ipks/all'
> died with <Signals.SIGABRT: 6>.
> 
> 
> 
> Subprocess output:abort()ing pseudo client by server request. See https://wiki.yoctoproject.org/wiki/Pseudo_Abort
> for more details on this.
> 
> 
> 
> Check logfile:
> /shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/pseudo//pseudo.log
> 
> 
> 
> 
> 
> 
> 
> 
> DEBUG: Python function do_package_ipk finished
> 
> 
> 
> DEBUG: Python function do_package_write_ipk finished
> 
> 
> 
> sjc-ads-7501:/shr/router/yocto/poky >
> 
> 

Here is the pseudo.log from the most recent failure. I know a lot of proprietary context is missing for anyone in the OSS community to give super confident answers, but I appreciate any suggestions.

Some context here:

1. I are running Yocto build command inside a docker container, rather than a metal Linux server

2. I saw the pseudo abort error reported at multiple recipes such as autoconf-native, ncurses

3. T he same error was still reported when executing Yocto build command to do single recipe build.

Thanks for your time and any suggestions.

Mario

[-- Attachment #2: Type: text/html, Size: 27378 bytes --]

Re: [yocto] Pseudo abort errors

[arthur52666]

[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]

> 
> ecs-915:/shr/router/yocto/poky > cat
> /shr/router/build/tmp/work/all-shr-linux/autoconf-archive/2022.02.11-r0/temp/log.task_order
> 
> do_cleansstate (1066956): log.do_cleansstate.1066956
> do_fetch (1067094): log.do_fetch.1067094
> do_unpack (1067099): log.do_unpack.1067099
> do_prepare_recipe_sysroot (1067100): log.do_prepare_recipe_sysroot.1067100
> 
> do_patch (1067118): log.do_patch.1067118
> do_deploy_source_date_epoch (1067128):
> log.do_deploy_source_date_epoch.1067128
> do_populate_lic (1067129): log.do_populate_lic.1067129
> do_configure (1067219): log.do_configure.1067219
> do_compile (1067974): log.do_compile.1067974
> do_install (1068007): log.do_install.1068007
> do_populate_sysroot (1068089): log.do_populate_sysroot.1068089
> do_package (1068088): log.do_package.1068088
> do_packagedata (1068308): log.do_packagedata.1068308
> do_package_write_ipk (1068364): log.do_package_write_ipk.1068364
> do_package_qa (1068365): log.do_package_qa.1068365
> ecs-915:/shr/router/yocto/poky >
>

[-- Attachment #2: Type: text/html, Size: 1092 bytes --]

Re: [yocto] Pseudo abort errors

[Richard Purdie]

On Tue, 2025-06-03 at 00:40 -0700, arthur52666 via lists.yoctoproject.org wrote:
> 
> I am building Embedded Linux image based on Yocto framework. The image building involves a lot of recipe execution.
> when building the image I always get below pseudo abort error :
>  
> > Pseudo log:
> > path mismatch [1 link]: ino 147610407 db '/tmp/sh-thd.VPxkGG' req '/tmp/sh-thd.4Z7cxB'.
> >  
>  
> I tried to build the image multiple times, 100% got the error every
> time, but the error was reported at different recipe every time. I've
> read the wiki page about them, but I'm not sure exactly what we are
> doing wrong that is making this happen. The files listed in the error
> log should be shell tmp files.
[...]
> Some context here: 
> 1. I are running Yocto build command inside a docker container, rather than a metal Linux server
> 2. I saw the pseudo abort error reported at multiple recipes such as autoconf-native, ncurses 
> 3. The same error was still reported when executing Yocto build command to do single recipe build.
>  
>  
> Thanks for your time and any suggestions.

I suspect the issue is the filesystem setup your docker container is
using. Bitbake/OE's use of pseudo assumes stable inode numbering and
some forms of container filesystems can break this assumption. I'm
afraid I don't remember specifically which setups don't work but others
might. That would certainly be the area I would look.

If the errors are always on the same filesystem location (/tmp?) then
that would hint at which filesystem to look at too.

Cheers,

Richard

Re: [yocto] Pseudo abort errors

[arthur52666]

[-- Attachment #1: Type: text/plain, Size: 421 bytes --]

Hi Richard,

thanks for your reply.
I confirm that the issue is always on the /tmp filesystem, I am wondering why the issue is only reported at my docker container(running at my Linux server), but not reported at other team member's docker container(running at their Linux server). We are following the same document to setup the Yocto build environment.
Which container configuration may cause the issue ?

Mario

[-- Attachment #2: Type: text/html, Size: 548 bytes --]