Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
jwilleke Trusted Contributor.
Trusted Contributor.
575 views

ndsconfig add .... Signature file not found Aborted (core du

On Red Hat Enterprise Linux Server release 7.6 (Maipo)

New root install.
First tried to install 9.1.2. Had issues and then could not confirm if that was supposed to be a full install or needed to be installed only as an upgrade to 9.1.0.

Apparently, there is no method to be sure all of the "novell" products are un-installed as novell-scrub.sh is old.

Running ndsconfig add ...
yields:
Signature file not found
Aborted (core dumped)


strace -ttt -ff -s 499 ndsconfig add ... yeilds:

1550689865.098099 lstat("/opt/novell/eDirectory/lib64/libgssapi.so", {st_mode=S_IFREG|0755, st_size=385040, ...}) = 0
1550689865.098139 open("/opt/nsr/lib/nsr/lib64/openssl_checksum.txt.asc", O_RDONLY) = -1 ENOENT (No such file or directory)
1550689865.098172 write(2, "Signature file not found\n", 25Signature file not found) = 25


Have been trying for more than a week to get eDirectory and IDM installed.
Decided to start over and can not get even eDirectory installed.


-jim
Labels (1)
0 Likes
6 Replies
Anonymous_User Absent Member.
Absent Member.

Re: ndsconfig add .... Signature file not found Aborted (core du

jwilleke <jwilleke@no-mx.forums.microfocus.com> wrote:
>

On Red Hat Enterprise Linux Server release 7.6 (Maipo)
>
> New root install.
> First tried to install 9.1.2. Had issues and then could not confirm if

that was supposed to be a full install or needed to be installed only as
an upgrade to 9.1.0.
>
> Apparently, there is no method to be sure all of the "novell" products

are un-installed as novell-scrub.sh is old.
>
> Running ndsconfig add ...
> yields:
>

Code:
--------------------
Signature file not found
> Aborted (core dumped)
>

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

>
> strace -ttt -ff -s 499 ndsconfig add ... yeilds:
>

Code:
--------------------

> 1550689865.098099 lstat("/opt/novell/eDirectory/lib64/libgssapi.so",
> {st_mode=S_IFREG|0755, st_size=385040, ...}) = 0
> 1550689865.098139
> open("/opt/nsr/lib/nsr/lib64/openssl_checksum.txt.asc", O_RDONLY) = -1 ENOENT (No such file
> or directory)
> 1550689865.098172 write(2, "Signature file not found\n", 25Signature file not found) = 25

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

>
> Have been trying for more than a week to get eDirectory and IDM

installed.
> Decided to start over and can not get even eDirectory installed.
>
>
> -jim



--
jwilleke
------------------------------------------------------------------------
jwilleke's Profile: https://forums.novell.com/member.php?userid=11492
View this thread: https://forums.novell.com/showthread.php?t=511380

>


Hi.

I have reviewed the documentation for eDirectory 9.1.2, and I cant find
that Red Hat Enterprise Linux Server release 7.6 is a supported.

--
Best regards
Marcus
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: ndsconfig add .... Signature file not found Aborted (core du

> I have reviewed the documentation for eDirectory 9.1.2, and I cant find
> that Red Hat Enterprise Linux Server release 7.6 is a supported.


It might be useful to see which pages of documentation were reviewed as it
explicitly states that "Supported on later versions of support packs"
which is basically what RHEL 7.6 is to 7.5, even though they have the SP
in the wrong part of the version.

Back to the original issue, seeing more of the strace output may be nice.
Since you are on RHEL I do not suppose Btrfs was used for the main
filesystem, since in that case you could revert to a snapshot prior to the
install of any other software which would be like scrubbing, but probably
more thorough and not depending on a particular scrub script.

Another way to clean things off is to use the 'rpm' command to see the
order of things installed and roll it back:


rpm -qa --last


#If this box was recently built and patched prior to adding the eDirectory
software, look for the date and time when the last non-eDirectory software
was installed and remove everything after/above that line in the list of
package.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: ndsconfig add .... Signature file not found Aborted (core du

ab <ab@no-mx.forums.microfocus.com> wrote:
>> I have reviewed the documentation for eDirectory 9.1.2, and I cant find
>> that Red Hat Enterprise Linux Server release 7.6 is a supported.

>
> It might be useful to see which pages of documentation were reviewed as it
> explicitly states that "Supported on later versions of support packs"
> which is basically what RHEL 7.6 is to 7.5, even though they have the SP
> in the wrong part of the version.
>
> Back to the original issue, seeing more of the strace output may be nice.
> Since you are on RHEL I do not suppose Btrfs was used for the main
> filesystem, since in that case you could revert to a snapshot prior to the
> install of any other software which would be like scrubbing, but probably
> more thorough and not depending on a particular scrub script.
>
> Another way to clean things off is to use the 'rpm' command to see the
> order of things installed and roll it back:
>
>

> rpm -qa --last
>

>
> #If this box was recently built and patched prior to adding the eDirectory
> software, look for the date and time when the last non-eDirectory software
> was installed and remove everything after/above that line in the list of
> package.
>


Hi.

You are right ab, of course. I was looking at the certified column, and
missed the support column. So I guess 7.5 is certified and 7.6 is
supported.

What confuses me even more is that 9.1 SP3 (released a few days ago) adds
support for Red Hat 7.6 according to the release notes:
https://www.netiq.com/documentation/edirectory-91/edirectory913_releasenotes/data/edirectory913_releasenotes.html

What does that mean in relation to the documentations "certified" and
"supported"? The documentation states supported means it is expected to
work but hasn't been tested. So I guess we cannot assume that installing a
later SP is really going to work. It might work. And MF support will
support you if it isn't. But there is no guarantee that it works since it
hasnt been tested.

Is 7.6 now certified as support has been added by eDir 9.1 sp3 and probably
tested?

So to be on the safe side, always use certified OS?

https://www.netiq.com/documentation/edirectory-91/edir_install/data/a79kg0t.html

--
Best regards
Marcus
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: ndsconfig add .... Signature file not found Aborted (core du

On 03/03/2019 01:20 PM, Marcus wrote:
> You are right ab, of course. I was looking at the certified column, and
> missed the support column. So I guess 7.5 is certified and 7.6 is
> supported.


Correct; certified means tested, so it is known to work, where supported
usually implies something earlier was certified, and since SPs, by
definition, are not supposed to break things that worked before, it should
still work. Still, it has not been officially tested, so that matters
too. Working with supported is usually just fine, especially since
customers are often on them very quickly due to the number of customers
(many) and the need to stay on semi-current code (often great), fairly soon.

> What confuses me even more is that 9.1 SP3 (released a few days ago) adds
> support for Red Hat 7.6 according to the release notes:
> https://www.netiq.com/documentation/edirectory-91/edirectory913_releasenotes/data/edirectory913_releasenotes.html
>
> What does that mean in relation to the documentations "certified" and
> "supported"? The documentation states supported means it is expected to


This is now certified, I believe. Modifying the documentation takes more
time, require more reviews, etc. While I do not think that should be the
case, something is making that harder than just going somewhere and
changing a '5' to a '6'; oh well; "Supported" it is, and that provides us
what we need.

> work but hasn't been tested. So I guess we cannot assume that installing a
> later SP is really going to work. It might work. And MF support will
> support you if it isn't. But there is no guarantee that it works since it
> hasnt been tested.


To be clear, it is likely to work. If a SP from a vendor of a product
breaks depending on that thing (an OS in this case), then they are doing
something wrong or extraordinary. Sometimes it is necessary to break
things in a SP, but it's very rare, and it breaks the implied contract
that companies have with clients that SPs will not break things, which
usually also means that the latest/greatest of something will not be
available in the new version, which sometimes makes clients unhappy, but
you cannot have it both ways. Either you have stability (meaning
compatibility stability) or you have bleeding edge (with metaphorical cuts
that hurt), but not both.

SUSE has worked around this a bit with its SUSE Linux Enterprise Server
(SLES) product line by having channels that are for a particular purpose,
e.g. web and scripting technologies, to which companies can subscribe to
get newer software than came with the original release. Of course, this
is done so that newer software, which needs newer versions of dependencies
(e.g. PHP), will work even though somebody is still on SLES 12 instead of
SLES 15, but it also means that the same box may have PHP versions too
new for other software, meaning older software may not work if you opt in
to that newer version of PHP. Again you cannot have it both ways, but
SUSE has made it possible for customers to get more of the two ways on a
single version of SLES.

> Is 7.6 now certified as support has been added by eDir 9.1 sp3 and probably
> tested?
>
> So to be on the safe side, always use certified OS?
>
> https://www.netiq.com/documentation/edirectory-91/edir_install/data/a79kg0t.html


That's a business decision. I would guess that the majority of my
customers are "only" on supported OS's, or using "supported" dependencies
(databases, directories, other software), and that's fine.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
jwilleke Trusted Contributor.
Trusted Contributor.

Re: ndsconfig add .... Signature file not found Aborted (cor

Apparently the issue I encountered was due to the order of installation of various patches of eDirectory and IDM.

A clean install of eDirectory 9.1.2 appears to work on RHEL 7.6.
IDM 4.7.2 Not so much.

-jim
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: ndsconfig add .... Signature file not found Aborted (core du

> You are right ab, of course. I was looking at the certified column, and

Don't say stuff like that to him, it just goes to his head and he
becomes insufferable.

> missed the support column. So I guess 7.5 is certified and 7.6 is
> supported.
>> What does that mean in relation to the documentations "certified" and

> "supported"? The documentation states supported means it is expected to > work but hasn't been tested. So I guess we cannot assume that

installing a
> later SP is really going to work. It might work. And MF support will
> support you if it isn't. But there is no guarantee that it works since it
> hasnt been tested.
>
> Is 7.6 now certified as support has been added by eDir 9.1 sp3 and probably
> tested?
>
> So to be on the safe side, always use certified OS?
>
> https://www.netiq.com/documentation/edirectory-91/edir_install/data/a79kg0t.html
>


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.