Date: Wed, 23 Mar 2022 09:36:39 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 262733] databases/py-carbon: within jail: Message-ID: <bug-262733-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262733 Bug ID: 262733 Summary: databases/py-carbon: within jail: Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: ohartmann@walstatt.org Running databases/py-carbon (with Python 3.8 as default) within a jail (base host is running 13.0-RELENG-p10, jail is running the same OS version: 13.0-RELEASE-p10 FreeBSD 13.0-RELEASE-p10 releng/13.0-n244791-312522780e8 KIPMON amd64. Starting within a jail databases/py-carbon from /etc/rc.conf.local fails, t= he host's log reports: [...] Starting carbon. ld-elf.so.1: Shared object "libpython3.8.so.1.0" not found, required by "python3.8" /etc/rc: WARNING: failed to start carbon ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/local/lib/compat/pkg /usr/local/lib/perl5/5.32/mach/CORE 32-bit compatibility ldconfig path: /usr/lib32 Starting Network: lo0 epair40a. [...] It seems the carbon cache is started too early so the ldconfig utility does= n't has the expanded paths in "LD_LIBRARY_PATH" as expected and the above log snippet indicates this fact - the expansion of ldconfig towards /usr/local/= lib comes too late for carbon; after the jail is up and running, the carbon cac= he can be started manually without any problems. My naive thinking let me expand the carbon's rc script with "# REQUIRE: lfconfig", but this did not resolve the issue, I could watch the ldconfig p= aths being resolved prior the carbon cache script startup, but hen the script si= mply fails to start - no matter why. Even being total pessimistic and enforcing = "' REQUIRE: LOGIN" did not resolve anything, I can see carbon being started in= the jail-hosts log, but switching over to the jail and checking the service abo= ut its state reveals that the carbon cache is not running. Starting the carbon cache manually after login works nicely. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262733-7788>