justfly1111
commented
3 years ago really noone else having tthis issue? its driving me nuts ...
Open justfly1111 opened 3 years ago
justfly1111
commented
3 years ago really noone else having tthis issue? its driving me nuts ...
bdrewery
commented
3 years ago [00:01:00] pkg-static: Fail to chown /usr/local/lib/perl5/site_perl/Locale/RecodeData/.pkgtemp.IBM437.pm.DjMFvMfQvnaC:Bad file descriptorThis looks like a problem with pkg not Poudriere.
bdrewery
commented
3 years ago What version of pkg is in your repository?
These are not sufficient. Please specify the exact versions/hashes for Poudriere and ports.
Poudriere Version [e.g. 3.3.1 or git hash or port version]:
poudriere-git-3.4-pre
Ports branch and revision [e.g. 2020Q3 r550754]: master/head git.freebsd.org/ports.git
# poudriere version
poudriere-git-3.4-preIn particular poudriere version should not be returning 3.4-pre if it came from the port or git. It has not said that since 2017 53b229ce0190a9e350ba0e6a7ca0cd54dc26fabc https://github.com/freebsd/freebsd-ports/commit/39d6b0f4d78ff43de5bd77605ea2dd1297c3ba2e.
justfly1111
commented
3 years ago its the poudriere from the tarball that you wiki has me fetch i forget if its in the running poudriere in a jail or using portshaker its from https://github.com/freebsd/poudriere/releases/master.tar.gz u think let me try ad find out its from one of the wiki articles that says to fetch poudriere from the void so im to asume that hadsnt been updated in along time.... how would you recommend i update it im looking at its makefile and source and all have 1994-2020 copywrites so it cant be that out dated from 2017 especially when it makes use of the pkg fetch option which is fairly recent if i recall but im just going to kill my current build and update to cloning the current master branch and installling real quickly and pray it no longer happens
heliosyne
commented
3 years ago [00:00:51] pkg-static: Fail to chown /usr/local/include/boost/atomic/detail/.pkgtemp.caps_gcc_ppc.hpp.aDJFroF8B3He:Bad file descriptor
This is probably the volume out of space or a corrupted jail if it's a reproducible error.
justfly1111
commented
3 years ago ive made fresh poudriere jails about 4 diff ones diff options of creating them @heliosyne and have plenty of space zpool iostat capacity operations bandwidth pool alloc free read write read write
zrepo 70.4G 278G 319 64 4.01M 3.70M #
bdrewery
commented
3 years ago its the poudriere from the tarball that you wiki has me fetch i forget if its in the running poudriere in a jail or using portshaker its from https://github.com/freebsd/poudriere/releases/master.tar.gz u think let me try ad find out its from one of the wiki articles that says to fetch poudriere from the void so im to asume that hadsnt been updated in along time....
Yes, I've changed that to say pkg install poudriere.
how would you recommend i update it im looking at its makefile and source and all have 1994-2020 copywrites so it cant be that out dated from 2017 especially when it makes use of the pkg fetch option which is fairly recent if i recall but im just going to kill my current build and update to cloning the current master branch and installling real quickly and pray it no longer happens
The copyrights are not well maintained. Good idea on remaking it. Did you use the FreeBSD 10 jail like that wiki suggested? That might be related to the issues here but I'm not sure.
justfly1111
commented
3 years ago @bdrewery noo am using current built from /usr/src in one jail then current built from base.tar.gz created from /usr/src/release and then another is a current jail built from git+https i been looking and looking into it it seems that it has something to do with chown or chmod files to a nonexistent user or group in the jails that is my best guess at whats causing the issue when i saw that the poudriere fetching from the void with master.tar.gz had a newer poudriere version then building from the master branch i thought i stubled uponn treasure guess not lol but since ive rebuilt poudriere from the master branch and done all the suggestions and still having the issuethats how i came up with the prognosis that its deriving from nonexistant users/groupps in the jails but what do i know its probabyly somethng else as simple as meadding or removing a trailing / or something not quite sure wherre to goo from here its more annoying than anything cause half the time on the next rebuild attempt itll build fine and a diff package willl fail for the same reason it just seems so random
grahamperrin
commented
1 year ago Command:
poudriere bulk -j 1049 -b latest -J 8 emulators/virtualbox-ose
From file:///usr/local/poudriere/data/logs/bulk/1049-default/latest/logs/errors/xkeyboard-config-2.34_2.log:
…
===> Returning to build of xkeyboard-config-2.34_2
===> xkeyboard-config-2.34_2 depends on package: perl5>=5.32.r0<5.33 - not found
===> Installing existing package /packages/All/perl5-5.32.1_3.pkg
[1049-default-job-07] Installing perl5-5.32.1_3...
[1049-default-job-07] Extracting perl5-5.32.1_3: .......
pkg-static: Fail to chown /5.32/unicore/lib/Upper/Y.pl:Bad file descriptor
[1049-default-job-07] Extracting perl5-5.32.1_3... done
Failed to install the following 1 package(s): /packages/All/perl5-5.32.1_3.pkg
*** Error code 1
Stop.
…With the subsequent run of the same command:
root@mowa219-gjp4-8570p-freebsd:~ # poudriere jail -i -j 1049
Jail name: 1049
Jail version: 14.0-CURRENT
Jail arch: amd64
Jail method: url=https://download.freebsd.org/snapshots/amd64/amd64/14.0-CURRENT
Jail mount: /usr/local/poudriere/jails/1049
Jail fs: august/poudriere/jails/1049
Jail updated: 2023-04-30 17:29:21
Jail pkgbase: disabled
root@mowa219-gjp4-8570p-freebsd:~ # emulators/virtualbox-ose is patched as outlined at https://github.com/freebsd/poudriere/discussions/1049, I don't imagine that this patching is relevant.
netfenceventu
commented
1 year ago Just a me too... I'm using 13.2/amd64 and it all started after I upgraded from 13.1.
batrachian
commented
7 months ago Just started seeing these. Happens randomly and not repeatable.
This is on a box just upgraded from 12 to 13.3-RELEASE that is also seeing
Bug 275594 - High CPU usage by arc_prune; analysis and fix
which was first noticed during poudriere runs while building rust.
ETA: 64GB RAM, >500GB available ZFS, seen during even small poudriere runs - e.g. a dozen small ports.
grepping the poudriere logs returns no instances while the box had 11-R or 12-R.
Also found that while it is random, there appear to be a few repeatable contenders for triggering it, and appears to always occur during 'extract' (which I believe is also a trigger for e.g. rust in the 275594 Bug).
So far it has been:
===> Installing existing package /packages/All/cmake-core-3.28.3.pkg
...
[13Ramd64-foo-job-08] Extracting cmake-core-3.28.3: .....
pkg-static: Fail to chown /Help/variable/CMAKE_VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION.rst:Bad file descriptor
===> Installing existing package /packages/All/cmake-core-3.28.3.pkg
...
[13Ramd64-foo-job-08] Extracting cmake-core-3.28.3: .
pkg-static: Fail to chown /Help/module/FindOpenMP.rst:Bad file descriptor
===> Installing existing package /packages/All/cmake-core-3.28.3.pkg
...
[13Ramd64-foo-job-08] Extracting cmake-core-3.28.3: .
pkg-static: Fail to chown /Help/module/FindOpenMP.rst:Bad file descriptor
===> Installing existing package /packages/All/cmake-core-3.28.3.pkg
...
[13Ramd64-foo-job-08] Extracting cmake-core-3.28.3: .....
pkg-static: Fail to chown /Help/variable/CMAKE_VS_WINDOWS_TARGET_PLATFORM_MIN_VERSION.rst:Bad file descriptor
===> Installing existing package /packages/All/py39-setuptools-rust-1.9.0.pkg
...
[13Ramd64-foo-job-03] `-- Extracting rust-1.77.0: ......
pkg-static: Fail to chown /html/core/core_arch/x86/avx512f/fn._mm512_moveldup_ps.html:Bad file descriptor
===> Installing existing package /packages/All/py39-setuptools-rust-1.9.0.pkg
...
[13Ramd64-foo-job-03] `-- Extracting rust-1.77.0: ......
pkg-static: Fail to chown /html/core/core_arch/x86/avx512f/fn._mm512_moveldup_ps.html:Bad file descriptor
===> Installing existing package /packages/All/mariadb105-server-10.5.23.pkg
...
[13Ramd64-foo-job-01] | `-- Extracting boost-libs-1.84.0: ........
pkg-static: Fail to chown /tti/detail/dtemplate_params.hpp:Bad file descriptor
===> Installing existing package /packages/All/mariadb105-server-10.5.23.pkg
...
[13Ramd64-foo-job-01] | `-- Extracting boost-libs-1.84.0: ........
pkg-static: Fail to chown /tti/detail/dtemplate_params.hpp:Bad file descriptor
===> Installing existing package /packages/All/py39-setuptools-63.1.0_1.pkg
...
[13Ramd64-foo-job-03] `-- Extracting python39-3.9.18_2: .......
pkg-static: Fail to chown /test/test_asyncio/__pycache__/utils.cpython-39.opt-1.pyc:Bad file descriptor
===> Installing existing package /packages/All/py39-setuptools-63.1.0_1.pkg
...
[13Ramd64-foo-job-03] `-- Extracting python39-3.9.18_2: .......
pkg-static: Fail to chown /test/test_asyncio/__pycache__/utils.cpython-39.opt-1.pyc:Bad file descriptorhttps://github.com/freebsd/poudriere/issues/923#issuecomment-1529089065 (2023-04-30):
Jail version: 14.0-CURRENT
I don't recall encountering the symptom more than once.
Re: https://freshbsd.org/freebsd/src/commit/aee253d8a7aea40189f8ca74138d6bed10948b1e I would have begun using 15.0-CURRENT in August last year.
grahamperrin
commented
1 month ago https://github.com/freebsd/poudriere/issues/923#issuecomment-928244668 (2021-09-27):
This looks like a problem with
pkg…
FWIW:
At a glance, 2279 is more thought-provoking.
@bdrewery if both are completely unrelated, please hide this comment as off-topic. Thanks.
Prerequisites
Describe the bug
So Im running poudriere in a freebsd-current jail host is running freebsd current likewise
the jails performing builds were built via /usr/src directly and also git+https and also base.txz build from make release in /usr/src this error happens with all
So for roughtly 4-5 days after running bullk builds and during them after noticing a failure and reading the error logs roughly one out of give or take 7-8 ports fails while gathering and setting up dependencies for the build due to poudriere not being able to chown or chmod one of the build dependancies and says simply cannot chown yada yada package bad file descriptor. ill copy and paste that portion of the logs i just had i think 6-7 ports fail due to it randomly during a build 👍🏻 👍🏻
a3ps log:
libwpd log:
aalib log
same thing with the rest of the ports in this error/log dir
It seems that the its choosing random files to have bad descriptors cause as you can see building the same pkg_list file as the build before that i stop that based on the output bellow its completely different packages with bad filedescriptors
Anyone else having anytype of issues like this or anyone see anything remotely like this im building as root/wheel now i switched to it the first time i got a bad file discriptor could not chown of a package because i assumed it had to involve permissions orr lack of permissions to nobody/nobody which it doesnt but incase i kept rolling with building as root to ensure i kept permision and continue to see these errors and its annoying af to say the least hope someonen knowss what is causing this thank you your time is greatly appreciated
btw i am running poudriere version:
How to reproduce
Steps to reproduce the behavior: run any poudriere bulk buid
see failures and skipped packages due to missing packages and see was caused because couldnt run chmod or chown cause of bad file descriptor when it should run compile and package wwith no hiccups or errors
Expected behavior
for poudriere to build all pkgs in my pkglist flawlessly and for there not to be any errors due to bad file descriptors
Screenshots