Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Feb 2016 07:24:04 -0800
From:      David Wolfskill <david@catwhisker.org>
To:        freebsd-ports@freebsd.org
Subject:   poudriere: success(?) despite "ELF interpreter /lib/ld-linux.so.2 not found, error 2"?
Message-ID:  <20160213152404.GK1364@albert.catwhisker.org>

next in thread | raw e-mail | index | archive | help

--xpAEiv7IYLnw+pq/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I encountered an unexpected whine-like message during a poudriere
run, but it doesn't seem to actually have indicated a reported (or
logged) error.  So I wrote this up, hoping for a reality check.

I started using poudriere to build my own packages for my stable/10
amd64 machines last July (and actually started installing those
packages on a couple of the machines shortly thereafter).  That
effort appears to have been reasonably successful: one of the
machines thus affected is the one where this email message is being
created; the other is the machine that acts as a packet filter
between the Internet and my internal networks at home.

I update those machines weekly (Sunday mornings) -- first FreeBSD
base, then the installed packages.  In order to accomplish that, I
update FreeBSD base on a "build machine," and perform a "poudriere
bulk" on the same build amchine.  (Actually, I do a couple "poudriere
bulk" runs: one Saturday morning, after the Saturday update to
FreeBSD on the build machine, and another on Sunday, after the
update that day.  The intent is to reduce the amount of package-building
time required on Sunday.)

I perform all FreeBSD builds and poudriere runs within script(1), as I
like to have a record of what happened.

This morning, I just happened to glance at the xterm where poudriere
was running, and noticed a message I wasn't expecting:

ELF interpreter /lib/ld-linux.so.2 not found, error 2

I wondered a few things at that point, including:
* What port it was working on when that was issued?
* Does that (message) indicate a failure to build a package?
* Has it been issued before?

Eventually, the poudriere run ended:

=2E..
[10amd64-ports-home] [2016-02-13_12h44m25s] [committing:] Queued: 266 Built=
: 266 Failed: 0   Skipped: 0   Ignored: 0   Tobuild: 0    Time: 01:24:58
[01:25:00] =3D=3D=3D=3D>> Logs: /usr/local/poudriere/data/logs/bulk/10amd64=
-ports-home/2016-02-13_12h44m25s
[01:25:00] =3D=3D=3D=3D>> Cleaning up
[01:25:00] =3D=3D=3D=3D>> Umounting file systems
freebeast(10.3)[2] echo $?
0

I suppose that answers the 2nd of my questions (above) in the negative.

And looking through the poudriere typescripts, I found that the
message was also issued 31 January -- again with no (other) indication
of error:

=2E..
[10amd64-ports-home] [2016-01-31_12h34m04s] [committing:] Queued: 77 Built:=
 77 Failed: 0  Skipped: 0  Ignored: 0  Tobuild: 0   Time: 00:19:47
[00:19:50] =3D=3D=3D=3D>> Logs: /usr/local/poudriere/data/logs/bulk/10amd64=
-ports-home/2016-01-31_12h34m04s
[00:19:50] =3D=3D=3D=3D>> Cleaning up
[00:19:50] =3D=3D=3D=3D>> Umounting file systems
freebeast(10.3-P)[2] echo $?
0
freebeast(10.3-P)[3] exit

(I only keep the last 4 poudriere typescripts, unless I have some
reason to retain one specially.)

I then checked /usr/local/poudriere/data/logs/bulk/10amd64-ports-home:

freebeast(10.3)[9] dirs
/usr/local/poudriere/data/logs/bulk/10amd64-ports-home=20
freebeast(10.3)[10] grep -r 'ELF interpreter .* not found' .
freebeast(10.3)[11] echo $?
1
freebeast(10.3)[12]=20

Mind, I haven't got around to cleaning out my logs yet, so I have
all of them since I started using poudriere:

freebeast(10.3)[12] ls
2015-07-04_07h07m54s    2015-09-13_04h43m51s    2015-12-05_05h09m40s
2015-07-04_13h20m32s    2015-09-19_04h59m06s    2015-12-06_04h32m19s
2015-07-11_05h38m13s    2015-09-20_04h14m55s    2015-12-12_05h00m18s
2015-07-11_05h38m49s    2015-09-26_05h28m39s    2015-12-13_04h22m52s
2015-07-11_11h57m33s    2015-09-27_04h12m01s    2015-12-19_05h18m01s
2015-07-11_11h59m13s    2015-10-03_04h53m56s    2015-12-20_04h50m11s
2015-07-11_12h06m53s    2015-10-04_04h33m25s    2015-12-24_05h46m16s
2015-07-12_04h47m09s    2015-10-10_05h46m40s    2015-12-24_07h08m50s
2015-07-19_04h25m15s    2015-10-10_08h53m29s    2015-12-24_07h17m26s
2015-07-25_04h52m51s    2015-10-10_12h44m50s    2015-12-26_05h11m20s
2015-07-26_04h08m48s    2015-10-11_04h15m52s    2015-12-26_07h07m21s
2015-07-29_04h16m57s    2015-10-17_05h19m14s    2015-12-27_04h27m54s
2015-08-01_04h47m26s    2015-10-18_04h26m37s    2016-01-02_12h53m11s
2015-08-02_05h04m48s    2015-10-24_05h03m43s    2016-01-03_12h30m26s
2015-08-08_04h44m21s    2015-10-25_04h31m41s    2016-01-09_13h21m18s
2015-08-09_04h30m50s    2015-10-31_05h32m16s    2016-01-16_13h00m21s
2015-08-15_04h31m27s    2015-10-31_07h04m35s    2016-01-17_12h45m33s
2015-08-16_04h30m41s    2015-10-31_07h07m28s    2016-01-23_13h00m20s
2015-08-22_04h52m44s    2015-10-31_07h13m33s    2016-01-24_12h36m54s
2015-08-23_04h29m06s    2015-11-01_04h14m59s    2016-01-30_13h24m11s
2015-08-23_04h57m31s    2015-11-07_08h20m41s    2016-01-31_12h34m04s
2015-08-23_05h00m13s    2015-11-08_04h26m39s    2016-02-06_13h22m35s
2015-08-29_05h14m53s    2015-11-14_10h05m27s    2016-02-07_12h09m49s
2015-08-29_17h42m34s    2015-11-15_04h25m40s    2016-02-13_12h44m25s
2015-08-30_04h31m17s    2015-11-21_04h58m55s    latest
2015-09-05_04h54m19s    2015-11-22_04h26m11s    latest-per-pkg
2015-09-06_04h22m05s    2015-11-28_04h51m26s
2015-09-12_04h48m17s    2015-11-29_04h25m40s
freebeast(10.3)[13]=20

So we can conclude that the message has been issued before, but I
have no evidence to tie its issuance with the build of any particular
package.  Since the packages all report having been built OK, I suppose
nothing is exactly wrong, per se... but this seems a little on the "odd"
side.

Oh: for reference:

freebeast(10.3)[13] uname -a
FreeBSD freebeast.catwhisker.org 10.3-BETA2 FreeBSD 10.3-BETA2 #1938  r2955=
52M/295562:1002509: Fri Feb 12 04:04:31 PST 2016     root@freebeast.catwhis=
ker.org:/common/S1/obj/usr/src/sys/GENERIC  amd64
freebeast(10.3)[14] pkg info poudriere\*
poudriere-devel-3.1.99.20160127_1
freebeast(10.3)[15] svn info /usr/ports/
Path: /usr/ports
Working Copy Root Path: /usr/ports
URL: file:///svn/freebsd/ports/head
Relative URL: ^/head
Repository Root: file:///svn/freebsd/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 408784
Node Kind: directory
Schedule: normal
Last Changed Author: koobs
Last Changed Rev: 408782
Last Changed Date: 2016-02-13 02:51:08 -0800 (Sat, 13 Feb 2016)

freebeast(10.3)[16]=20

I use private SVN mirrors of the FreeBSD src, ports, and doc
repositories, updated nightly (in 2 stages, for historical reasons
dating back to CVS and CVSup & inertia on my part).

Info on my environment and "how I do stuff" may be found at:

* http://www.catwhisker.org/~david/FreeBSD/upgrade.html
* http://www.catwhisker.org/~david/FreeBSD/convert_i386_amd64.html

Peace,
david
--=20
David H. Wolfskill				david@catwhisker.org
Those who would murder in the name of God or prophet are blasphemous coward=
s.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.

--xpAEiv7IYLnw+pq/
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQF8BAEBCgBmBQJWv0qUXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix
NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4X7v0H+gLOrZiU7kITguhCh6P98k+Z
nj7OYG9XM54BechFP49uOXWcusKFSB8yyS5l/hrzeDYYbYOgcwl+LX5f60X2V/n2
sDfkZjNUclOUmWwwOebZ6ZtJWvNjh+hNcmTYaRRyAVC6qkp+35j654EhD+WCdjsE
mY177FW2Jlk4930yktBUuQBK5lcDMK2z8ZhhH8Hzar9PrxGYXNJEzU1WsxELN24W
RPCmbaK0V8jIoDThgeWqgdPCAfIii1c0f/DW5VYBshk8Q6lMmfB+DyzP+1SBxTYL
oh+mNsSdsfZzPFNy0heEmCu7kMOngAZyXd70c4vk1YrC3zr1m5WscDPq7mVBJb0=
=S2D8
-----END PGP SIGNATURE-----

--xpAEiv7IYLnw+pq/--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160213152404.GK1364>