libssl.so.1.1 error in newest WeKan for Sandstorm

[xet7]

Hi,
today is released Node.js 12.22.9 that I added to wekan-5.91.spk package, when building it on Kubuntu 21.10 amd64:
https://releases.wekan.team/sandstorm/

But when I test wekan-5.91.spk package on my laptop at http://local.sandstorm.io:6080 , WeKan does not start and gives these errors:

** SANDSTORM SUPERVISOR: Starting up grain. Sandbox type: userns
node: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
** HTTP-BRIDGE: App server exited with status code: 127
** SANDSTORM SUPERVISOR: App exited with status code: 1

[ocdtrekkie]

So it sounds to me that libssl isn't being included in your build... which is weird if you didn't change anything relevant?

[xet7]

Hmm, Kubuntu seems to have libssl installed:

$ dpkg -l | grep libssl

ii  libssl1.1:amd64                                             1.1.1l-1ubuntu1.1                                       amd64        Secure Sockets Layer toolkit - shared libraries

[xet7]

I did change to newer npm packages but I don't know can that affect libssl

[xet7]

Does this need some LD_LIBRARY_PATH stuff?
https://www.bswen.com/2018/11/others-Openssl-version-cause-error-when-loading-shared-libraries-libssl.so.1.1.html

[xet7]

I changed distro from Kubuntu back to Mint, and it did not help. Well, that Mint is newer version that is previously was.

That newest WeKan v5.93 is still broken.

[ocdtrekkie]

Sorry I haven't been able to look into this as of yet. I've been a bit occupied in my personal life. Because you use meteor-spk, it's usually pretty weird for something to fail to be included. (And your alwaysInclude is alwaysInclude = [ "." ], which I take to mean "literally everything".

@zenhack Any chance you might have some insight what to try or look for on this one?

[zenhack]

Does that file (libssl.so.1.1) appear in your sandstorm-files.list? If, so what is the full path?

[ocdtrekkie]

@zenhack That's the weird part: meteor-spk doesn't use sandstorm-files.list, or generate one.

[zenhack]

Does a file by that exact name exist anywhere on the system?

What is the output of ldd on the node executable that is being used?

[xet7]

@zenhack

wekan@hx:~$ node -v
v12.22.9

wekan@hx:~$ ldd /home/wekan/.volta/bin/node
        linux-vdso.so.1 (0x00007ffc9a62f000)
        libssl.so.1.1 => /lib/x86_64-linux-gnu/libssl.so.1.1 (0x00007f863f0db000)
        libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007f863ee00000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f863ebd8000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f863f8dc000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f863ebd3000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f863ebb9000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f863ebb4000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f863ebad000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f863eac9000)

[xet7]

@zenhack

This is at Kubuntu:

wekan@hx:~$ uname -a
Linux hx 5.13.0-27-generic #29-Ubuntu SMP Wed Jan 12 17:36:47 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

wekan@hx:~$ cat /etc/issue
Ubuntu 21.10 \n \l

[zenhack]

I think meteor bundles its own copy of node; can you find that and report the output of ldd on that?