× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



So Kevin - any clue as to why they are getting

0509-022<tel:0509-022> Cannot load module libcrypto.a(libcrypto.so.1).

When they execute the node command?

Sent from my iPad

On 3 Oct 2016, at 23:59, Kevin Adler <kadler@xxxxxxxxxx<mailto:kadler@xxxxxxxxxx>> wrote:

"OpenSource" <opensource-bounces@xxxxxxxxxxxx<mailto:opensource-bounces@xxxxxxxxxxxx>> wrote on 10/03/2016
07:11:25 AM:

From: Aaron Bartell <aaronbartell@xxxxxxxxx<mailto:aaronbartell@xxxxxxxxx>>
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx<mailto:opensource@xxxxxxxxxxxx>>
Date: 10/03/2016 07:11 AM
Subject: Re: [IBMiOSS] Latest node installation woes
Sent by: "OpenSource" <opensource-bounces@xxxxxxxxxxxx<mailto:opensource-bounces@xxxxxxxxxxxx>>

What is interesting is that on our server we don't appear to have the
path
specifically set to anything and yet it works.

I am not certain about this, but IBM's installation might conditionally
create the symlinks --or-- they may have tried to create the symlinks
and
it failed because perzl is part of the default PATH (which if failing on
libcrypto.a).

Node v0.12 (5733-OPS Option 1) used its own install mechanism and with
manual code for creating all the symlinks (yuck). For Python, I wrote a
new install mechanism that just generates a save file that gets restored
with the symlinks. One aspect of this is that if the symlink already
exists, it will not get overwritten during our install. Whether this is
right or wrong is a matter of opinion, but the good news is that Perzl
installs in to /opt/freeware/bin and /usr/bin while PASE/OPS installs to
/QOpenSys/usr/bin, so we should never run in to a conflict unless someone
has created their own link in /QOpenSys/usr/bin.

Also, PATH is not used for symlink creating. The only thing PATH is used
for is when calling execp() (or one of it's variants) to find the path to
the program being executed if you don't specify an absolute or relative
path: https://linux.die.net/man/3/exec


Aaron Bartell
litmis.com<http://litmis.com> - Services for open source on IBM i


On Mon, Oct 3, 2016 at 7:05 AM, Kevin Turner
<kevin.turner@xxxxxxxxxxxxxxx<mailto:kevin.turner@xxxxxxxxxxxxxxx>>
wrote:

Thanks Aaron

We aren't using v.0.12.x but they were - but I have fixed that.

What is interesting is that on our server we don't appear to have the
path
specifically set to anything and yet it works.

I will check if they have perzl installed...

Cheers
Kevin

[https://www.netcracker.com/assets/img/netcracker-social-final.png] ƕ
-----Original Message-----
From: OpenSource [mailto:opensource-bounces@xxxxxxxxxxxx] On Behalf Of
Aaron Bartell
Sent: 03 October 2016 13:02
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx<mailto:opensource@xxxxxxxxxxxx>>
Subject: Re: [IBMiOSS] Latest node installation woes

Further to Robert's comments, you should also run the
/QOpenSys/QIBM/ProdData/OPS/Node4/bin/nodeenv.sh(n1) shell script
which
will set the symlinks in /QOpenSys/usr/bin.

n1 - More info here: http://bit.ly/developerWorks-node-v4

Concerning why it bombs on libcrypto.a, that many times is because of
a
conflict with perzl stuff. Remove /opt/freeware/bin from PATH and see
if
that allows it to continue. If you need perzl stuff in your path then
that's a longer conversation to fix it.

Also, it appears you're using Node
v.0.12.x(/QOpenSys/QIBM/ProdData/Node/bin/node). IBM has alluded
giving
that an EndOfLife, time to move on to Node
v4.x(/QOpenSys/QIBM/ProdData/
OPS/Node4/bin/node).

Aaron Bartell
litmis.com<http://litmis.com> - Services for open source on IBM i


On Mon, Oct 3, 2016 at 5:11 AM, R Brown <rbpaservices@xxxxxxxxx<mailto:rbpaservices@xxxxxxxxx>>
wrote:

I had the same issue. Look inside the OPS for NODE4 and add that
to
the path. It should find node then.

On Oct 3, 2016 4:40 AM, "Kevin Turner"
<kevin.turner@xxxxxxxxxxxxxxx<mailto:kevin.turner@xxxxxxxxxxxxxxx>>
wrote:

Hi

The guys managing our US IBMi servers are now trying to install
5770OPS.
They have installed the product and all PTFs, but it is still
foobar.

First and foremost no symbolic links have been created in /usr/bin
for
the
“node” and “npm” commands.
Despite that, even if you navigate to
QOpenSys/QIBM/ProdData/Node/bin
and
execute the node command it fails:

node -v
exec(): 0509-036 Cannot load program node because of the following
errors:
0509-150 Dependent module libcrypto.a(libcrypto.so.1)
could
not
be loaded.
0509-022 Cannot load module libcrypto.a(libcrypto.so.1).
0509-026 System error: A file or directory in the path
name
does not exist.

Sounds like something else needs to be there that 5770OPS does not
install
(ssh perhaps)?

I am not sure how or why IBM are making such a pigs ear of this.
Anyone
seen this before?

Thanks
Kevin


________________________________

NOTICE: The information in this electronic mail transmission is
intended by CoralTree Systems Ltd for the use of the named
individuals or entity
to
which it is directed and may contain information that is
privileged
or otherwise confidential. If you have received this electronic
mail
transmission in error, please delete it from your system without
copying
or
forwarding it, and notify the sender of the error by reply email
or
by telephone, so that the sender's address records can be
corrected.



------------------------------------------------------------
--------------------


CoralTree Systems Limited
25 Barnes Wallis Road
Segensworth East, Fareham
PO15 5TT

Company Registration Number 5021022.
Registered Office:
12-14 Carlton Place
Southampton, UK
SO15 2EA
VAT Registration Number 834 1020 74.
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To
post a message email: OpenSource@xxxxxxxxxxxx<mailto:OpenSource@xxxxxxxxxxxx> To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx<mailto:OpenSource-request@xxxxxxxxxxxx> Before posting, please
take a moment to review the archives at
http://archive.midrange.com/opensource.

--
This is the IBMi Open Source Roundtable (OpenSource) mailing list To
post a message email: OpenSource@xxxxxxxxxxxx<mailto:OpenSource@xxxxxxxxxxxx> To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx<mailto:OpenSource-request@xxxxxxxxxxxx> Before posting, please
take
a moment to review the archives at
http://archive.midrange.com/opensource.

--
This is the IBMi Open Source Roundtable (OpenSource) mailing list To
post
a message email: OpenSource@xxxxxxxxxxxx<mailto:OpenSource@xxxxxxxxxxxx> To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx<mailto:OpenSource-request@xxxxxxxxxxxx> Before posting, please take
a
moment to review the archives at
http://archive.midrange.com/opensource.



________________________________
The information transmitted herein is intended only for the person or
entity to which it is addressed and may contain confidential,
proprietary
and/or privileged material. Any review, retransmission, dissemination
or
other use of, or taking of any action in reliance upon, this
information by
persons or entities other than the intended recipient is prohibited.
If you
received this in error, please contact the sender and delete the
material
from any computer.
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx<mailto:OpenSource@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx<mailto:OpenSource-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.

--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx<mailto:OpenSource@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx<mailto:OpenSource-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.


--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx<mailto:OpenSource@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx<mailto:OpenSource-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.

________________________________

NOTICE: The information in this electronic mail transmission is intended by CoralTree Systems Ltd for the use of the named individuals or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by telephone, so that the sender's address records can be corrected.



--------------------------------------------------------------------------------


CoralTree Systems Limited
25 Barnes Wallis Road
Segensworth East, Fareham
PO15 5TT

Company Registration Number 5021022.
Registered Office:
12-14 Carlton Place
Southampton, UK
SO15 2EA
VAT Registration Number 834 1020 74.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.