during bulk random pkgs fail due to poudriere not being able to chmod or chown a dependency during the build due to bad file descriptors #923
Comments
|
really noone else having tthis issue? its driving me nuts ... |
This looks like a problem with |
|
What version of These are not sufficient. Please specify the exact versions/hashes for Poudriere and ports. In particular |
|
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 |
This is probably the volume out of space or a corrupted jail if it's a reproducible error. |
|
ive made fresh poudriere jails about 4 diff ones diff options of creating them @heliosyne and have plenty of space zrepo 70.4G 278G 319 64 4.01M 3.70M |
Yes, I've changed that to say
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. |
|
@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 |
lang/perl5.32: pkg-static: Fail to chown /5.32/unicore/lib/Upper/Y.pl:Bad file descriptor whilst poudriere built x11/xkeyboard-configCommand:
From With the subsequent run of the same command:
Environment
|
|
Just a me too... |
|
Just started seeing these. Happens randomly and not repeatable. 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: |
|
#923 (comment) (2023-04-30):
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. |
|
#923 (comment) (2021-09-27):
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 likewisethe 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
Environment
poudriere-git-3.4-pre
Additional context
im at my wits end trying to come to a cause and after 4 going on 5 days its driving me insane hopefully someone has some experience fixing this issue or has atleast seen it or has even sometype of intuition or even a preminition or a hunch as to whats the cause of theissue going on here.
just incase to preclude hw issue / zfs issue heres the output of zpool status and iostat to check for erorors
Fingers crossed someone has someidea as to a cause and or a fix
The text was updated successfully, but these errors were encountered: