-
-
Notifications
You must be signed in to change notification settings - Fork 706
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libssl.so.1.1 error in newest WeKan for Sandstorm #3600
Comments
So it sounds to me that libssl isn't being included in your build... which is weird if you didn't change anything relevant? |
Hmm, Kubuntu seems to have libssl installed:
|
I did change to newer npm packages but I don't know can that affect libssl |
Does this need some LD_LIBRARY_PATH stuff? |
Thanks to xet7 ! Related #4280, related sandstorm-io/sandstorm#3600
Thanks to xet7 ! Related #4280, related sandstorm-io/sandstorm#3600
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. |
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 @zenhack Any chance you might have some insight what to try or look for on this one? |
Does that file (libssl.so.1.1) appear in your sandstorm-files.list? If, so what is the full path? |
@zenhack That's the weird part: meteor-spk doesn't use sandstorm-files.list, or generate one. |
Does a file by that exact name exist anywhere on the system? What is the output of |
|
This is at Kubuntu:
|
I think meteor bundles its own copy of node; can you find that and report the output of |
It depends when I find it. I have always used newest available node, installed it with n or npm, and copied to meteor-spk at http://releases.wekan.team/meteor-spk/
That above script calls this install Sandstorm with this: And build spk with this: I run that build spk script from this more general many bundle build script: I tried previous Node 12.22.8 and it also had libssl.so.1.1 error. I'll try to find does Meteor has specific node binary modifications. |
Hmm, actually, I'll look if meteor-spk directory tree is missing some files. Just a moment. |
Hmm, I don't see libssl there, I'll try to copy
|
I copied libssl, libgcc, libcrypto. It seems I need to copy glibc. Just a moment.
|
tammi = January, huhti = April |
Ok, so this makes a bit more sense to me; normal spk dev would likely pick up all the needed library dependencies, but since meteor-spk doesn't use the autodetection and just picks up the meteor dev bundle, if you've copied in an alternate version of node that links to system libraries, those won't be picked up. FWIW, there is a meteor-spk 0.6.0 now, which includes a somewhat more recent version of node (14 I think?). If that's new enough for you, that may be the easiest path forwards. I suspect helping to keep meteor-spk up to date would be easier than than fighting with errors like these; see e.g. sandstorm-io/meteor-spk#40 which was all it took to update meteor the last time. |
Oh, I did not notice version change, and that Node 14 is available, this issue is still open sandstorm-io/meteor-spk#39 WeKan currently uses Node 12, but there is trying to upgrade to Node 14. |
Using meteor-spk 0.6.0, newest Meteor, and WeKan branch that uses Node 14 but does not yet fully work, I get these errors. Fibers error could also be from some previous Node 12 WeKan, I'm not sure. MongoDB compatibility error could maybe be related to meteor/meteor#11666
|
… Node.js 14.x of meteor-spk-0.6.0 . Thanks to xet7 ! Fixes sandstorm-io/sandstorm#3600
I got WeKan working with this fix sandstorm-io/meteor-spk#41 |
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:
The text was updated successfully, but these errors were encountered: