On Tue, May 11, 2021 at 1:06 PM Diego Sueiro <[email protected]> wrote: > > Hi, > > > > We are having issues (not 100% reproducible) when building podman during the > do_install with the following error message: > > ``` > > (cd docs; ./dckrman.sh ./build/man/*.1) > > install -d -m 755 > /kas_build_dir/tmp/work/armv8a-poky-linux/podman/3.0-rc2+gitAUTOINC+288fb68896-r0/image/usr/bin > > /kas_build_dir/tmp/work/armv8a-poky-linux/podman/3.0-rc2+gitAUTOINC+288fb68896-r0/image/usr/share/man/man1 > > install -m 755 docker > /kas_build_dir/tmp/work/armv8a-poky-linux/podman/3.0-rc2+gitAUTOINC+288fb68896-r0/image/usr/bin/docker > > install -m 644 docs/build/man/docker*.1 -t > /kas_build_dir/tmp/work/armv8a-poky-linux/podman/3.0-rc2+gitAUTOINC+288fb68896-r0/image/usr/share/man/man1 > > abort()ing pseudo client by server request. See > https://wiki.yoctoproject.org/wiki/Pseudo_Abort for more details on this. > > Check logfile: > /kas_build_dir/tmp/work/armv8a-poky-linux/podman/3.0-rc2+gitAUTOINC+288fb68896-r0/pseudo//pseudo.log > > Aborted (core dumped) > > make: *** [Makefile:539: install.docker] Error 134 > > WARNING: exit code 1 from a shell command. > > ERROR: oe_runmake failed > > ``` > > > > This is the content of pseudo.log: > ``` > debug_logfile: fd 2 > > pid 1075 [parent 1073], doing new pid setup and server start > > Setup complete, sending SIGUSR1 to pid 1073. > > creat for '/tmp/sh-thd.95cHV4' replaces existing 672168 > ['/tmp/sh-thd.6D4hI6']. > > creat for '/tmp/sh-thd.986Dd3' replaces existing 672168 > ['/tmp/sh-thd.95cHV4']. > > creat for '/tmp/sh-thd.XlIuyk' replaces existing 672168 > ['/tmp/sh-thd.986Dd3']. > > creat for '/tmp/ccL4aHyi.cdtor.c' replaces existing 672169 > ['/tmp/sh-thd.o1G5U4']. > > creat for '/tmp/sh-thd.r5dLbv' replaces existing 672245 > ['/tmp/sh-thd.vl5PSr']. > > creat for '/tmp/sh-thd.k2j5Py' replaces existing 672245 > ['/tmp/sh-thd.r5dLbv']. > > path mismatch [1 link]: ino 111819501 db > '/kas_build_dir/tmp/work/armv8a-poky-linux/podman/3.0-rc2+gitAUTOINC+288fb68896-r0/go-tmp/go-build672889552/b505/_cgo_.o' > req > '/kas_build_dir/tmp/work/armv8a-poky-linux/podman/3.0-rc2+gitAUTOINC+288fb68896-r0/image/usr/share/man/man1/docker-cp.1'. > > db cleanup for server shutdown, 16:27:04.465 > > memory-to-file backup complete, 16:27:04.465. > > db cleanup finished, 16:27:04.465 > ``` > > Since I’m not familiar with pseudo I have no idea how to root cause and > investigate this issue. >
I'm not seeing this on podman myself, but I have dealt with a few of these over the past months. The best (high level) advice is on that dumped wiki page https://wiki.yoctoproject.org/wiki/Pseudo_Abort (but I'm not offering any news here). Fundamentally this means something is happening outside of the pseudo context, and that is breaking the file tracking. podman is a relatively simple recipe, so I can't think of what would be doing that off the top of my head. Bruce > Any help is really appreciated. > > > > > > -- > Diego Sueiro > Staff Software Developer – Automotive and Industrial Solutions (CE-OSS) > > > > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#6505): https://lists.yoctoproject.org/g/meta-virtualization/message/6505 Mute This Topic: https://lists.yoctoproject.org/mt/82751836/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
