From agoyeneche at gmail.com  Tue Nov  1 18:23:17 2022
From: agoyeneche at gmail.com (Ariel Goyeneche)
Date: Tue, 1 Nov 2022 19:23:17 +0100
Subject: =?utf-8?Q?dlopen=28=22python3912=2Eunit=2Eso=E2=80=9D=29=2C_faile?=
 =?utf-8?Q?d=3A_=E2=80=9Clibpython3=2E9=2Eso=2E1=2E0_cannot_open_shared_ob?=
 =?utf-8?Q?ject_file=3A_No_such_file_or_directory?=
In-Reply-To: <4988E1FB-49F3-4453-89D2-A1A239C756C6@nginx.com>
References: <CAD=KtToztjxWzFrUuDsk_DT+6qWW-PPrJi5+9Xerq6E6BWfdTA@mail.gmail.com>
 <4988E1FB-49F3-4453-89D2-A1A239C756C6@nginx.com>
Message-ID: <45C8FB3D-820A-4B5C-90FA-933B2D40DB91@gmail.com>

Hi Team,

I have to recompile Unit 1.28 with Python 3.9.12 as embedded language. 

In summary my compilation steps are: 

	tar xzf unit-1.28.0.tar.gz
	configure — openssl
	configure. python —config=/bin/miniconda39/python3.9-config —module=python3912 —lib-path=/bin/miniconda39/lib/libpython3.9.so
	make

Note that /bin/miniconda39/lib/libpython3.9.so exists and it is a symlink to /bin/miniconda39/lib/libpython3.9.so.1.0

As a result, the /bin/unit-1.28.0/build directory contains among other files

	python3912.unit.so
	unitd
	unitd.8

When I am trying to start unitd I have the following error in the log file
	dlopen("/bin/unit-1.28.0/build/python3912.unit.so”), failed: “libpython3.9.so.1.0 cannot open shared object file: No such file or directory”

Can you please help me to understand what the problem may be here?

Thanks
AG




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/unit/attachments/20221101/2df236c5/attachment.htm>

From andrew at digital-domain.net  Tue Nov  1 19:07:47 2022
From: andrew at digital-domain.net (Andrew Clayton)
Date: Tue, 1 Nov 2022 19:07:47 +0000
Subject: =?UTF-8?B?ZGxvcGVuKCJweXRob24zOTEyLnVuaXQuc2/igJ0pLA==?=
 failed: =?UTF-8?B?4oCcbGlicHl0aG9uMy45LnNvLjEuMA==?= cannot open shared
 object file: No such file or directory
In-Reply-To: <45C8FB3D-820A-4B5C-90FA-933B2D40DB91@gmail.com>
References: <CAD=KtToztjxWzFrUuDsk_DT+6qWW-PPrJi5+9Xerq6E6BWfdTA@mail.gmail.com>
	<4988E1FB-49F3-4453-89D2-A1A239C756C6@nginx.com>
	<45C8FB3D-820A-4B5C-90FA-933B2D40DB91@gmail.com>
Message-ID: <20221101190747.340e37de@kappa.digital-domain.net>

On Tue, 1 Nov 2022 19:23:17 +0100
Ariel Goyeneche <agoyeneche at gmail.com> wrote:

> 	configure. python —config=/bin/miniconda39/python3.9-config —module=python3912 —lib-path=/bin/miniconda39/lib/libpython3.9.so

I think --lib-path is supposed to point to a directory, not a file. Try
—lib-path=/bin/miniconda39/lib
   
> 	make
> 
> Note that /bin/miniconda39/lib/libpython3.9.so exists and it is a symlink to /bin/miniconda39/lib/libpython3.9.so.1.0

[...]

> When I am trying to start unitd I have the following error in the log file
> 	dlopen("/bin/unit-1.28.0/build/python3912.unit.so”), failed: “libpython3.9.so.1.0 cannot open shared object file: No such file or directory”
> 
> Can you please help me to understand what the problem may be here?

If fixing --lib-path doesn't help, you could also try something like
when starting unit

  LD_LIBRARY_PATH=/bin/miniconda39/lib /path/to/unitd ...

Cheers,
Andrew


From agoyeneche at gmail.com  Tue Nov  1 20:10:48 2022
From: agoyeneche at gmail.com (Ariel Goyeneche)
Date: Tue, 1 Nov 2022 21:10:48 +0100
Subject: =?utf-8?Q?Re=3A_dlopen=28=22python3912=2Eunit=2Eso=E2=80=9D=29=2C?=
 =?utf-8?Q?_failed=3A_=E2=80=9Clibpython3=2E9=2Eso=2E1=2E0_cannot_open_sha?=
 =?utf-8?Q?red_object_file=3A_No_such_file_or_directory?=
In-Reply-To: <20221101190747.340e37de@kappa.digital-domain.net>
References: <CAD=KtToztjxWzFrUuDsk_DT+6qWW-PPrJi5+9Xerq6E6BWfdTA@mail.gmail.com>
 <4988E1FB-49F3-4453-89D2-A1A239C756C6@nginx.com>
 <45C8FB3D-820A-4B5C-90FA-933B2D40DB91@gmail.com>
 <20221101190747.340e37de@kappa.digital-domain.net>
Message-ID: <F951B7B5-CA1A-488C-A1A1-AB8C78D91347@gmail.com>

Thanks Andrew. This did the trick:
> I think --lib-path is supposed to point to a directory, not a file. Try
> —lib-path=/bin/miniconda39/lib


Thanks
AG

> On 1 Nov 2022, at 20:07, Andrew Clayton <andrew at digital-domain.net> wrote:
> 
> On Tue, 1 Nov 2022 19:23:17 +0100
> Ariel Goyeneche <agoyeneche at gmail.com> wrote:
> 
>> 	configure. python —config=/bin/miniconda39/python3.9-config —module=python3912 —lib-path=/bin/miniconda39/lib/libpython3.9.so
> 
> I think --lib-path is supposed to point to a directory, not a file. Try
> —lib-path=/bin/miniconda39/lib
> 
>> 	make
>> 
>> Note that /bin/miniconda39/lib/libpython3.9.so exists and it is a symlink to /bin/miniconda39/lib/libpython3.9.so.1.0
> 
> [...]
> 
>> When I am trying to start unitd I have the following error in the log file
>> 	dlopen("/bin/unit-1.28.0/build/python3912.unit.so”), failed: “libpython3.9.so.1.0 cannot open shared object file: No such file or directory”
>> 
>> Can you please help me to understand what the problem may be here?
> 
> If fixing --lib-path doesn't help, you could also try something like
> when starting unit
> 
>  LD_LIBRARY_PATH=/bin/miniconda39/lib /path/to/unitd ...
> 
> Cheers,
> Andrew


From agoyeneche at gmail.com  Fri Nov 11 09:25:34 2022
From: agoyeneche at gmail.com (Ariel Goyeneche)
Date: Fri, 11 Nov 2022 10:25:34 +0100
Subject: [info] SSL_read(...) failed (104: Connection reset by peer)
In-Reply-To: <F951B7B5-CA1A-488C-A1A1-AB8C78D91347@gmail.com>
References: <CAD=KtToztjxWzFrUuDsk_DT+6qWW-PPrJi5+9Xerq6E6BWfdTA@mail.gmail.com>
 <4988E1FB-49F3-4453-89D2-A1A239C756C6@nginx.com>
 <45C8FB3D-820A-4B5C-90FA-933B2D40DB91@gmail.com>
 <20221101190747.340e37de@kappa.digital-domain.net>
 <F951B7B5-CA1A-488C-A1A1-AB8C78D91347@gmail.com>
Message-ID: <6BCC34C8-7D5F-45AC-BB52-DDFB3AB4F00F@gmail.com>

Hi Team,

I am running Nginx Unit 1.28 with Python 3.9.12 as embedded language. All seems fine, except a random entry in the logs saying

   [info] SSL_read(...) failed (104: Connection reset by peer)

I don’t see neither receive any feedback that the web servers are dropping any calls, but I wonder what may produce this info line?
Does anyone experienced this before?

Thanks in advance,
AG