mmiltenberger Valued Contributor.
Valued Contributor.
3193 views

imanager 277X cores on latest SLES 11 SP4 kernel update

We had iManager 2.7.7.6 running on SLES 11 (x86_64) SP4, for quite some time with no issues.

Kernel related patches applied last Friday, after which we started experiencing relatively frequent core dumps.

Versions prior to update:
kernel-default-3.0.101-108.48.1
kernel-default-devel-3.0.101-108.48.1
kernel-source-3.0.101-108.48.1

Versions after update:
kernel-default-3.0.101-108.57.1
kernel-default-devel-3.0.101-108.57.1
kernel-source-3.0.101-108.57.1

Upgrade to iManager 2.7.7.11 hoping that would be the solution, but problem continued so we had to revert the kernel patches back to the prior version.

Core is here: http://susepaste.org/15554366

Anyone else run into anything similar ?

Labels (1)
0 Likes
6 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: imanager 277X cores on latest SLES 11 SP4 kernel update

When, exactly, does it dump the core? As iManager begins starting? Later
during startup of iManager? When somebody first connects?

Have you tried changing ulimits to have higher values, at least for the
core (so you get a full core should you want to submit it to Micro Focus)
or maybe to test other things, like a lack of RAM available to the process?

--
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
zavalae Absent Member.
Absent Member.

Re: imanager 277X cores on latest SLES 11 SP4 kernel update

mmiltenberger;2483785 wrote:


Anyone else run into anything similar ?


We believe we are facing a similar issue, but not certain as we are still investigating.
I looked at the SUSE paste and can see:
fpu_exception   : yes

I wonder if this is related to:
https://www.suse.com/support/kb/doc/?id=7023167
There is no solution yet, but a workaround is available (which did not work for us).
By the way, what you posted in SUSE Paste is not a core...it's a Java Fatal Error log file:
https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/felog002.html
0 Likes
Knowledge Partner
Knowledge Partner

Re: imanager 277X cores on latest SLES 11 SP4 kernel update

mmiltenberger;2483785 wrote:
We had iManager 2.7.7.6 running on SLES 11 (x86_64) SP4, for quite some time with no issues.

Kernel related patches applied last Friday, after which we started experiencing relatively frequent core dumps.

Versions prior to update:
kernel-default-3.0.101-108.48.1
kernel-default-devel-3.0.101-108.48.1
kernel-source-3.0.101-108.48.1

Versions after update:
kernel-default-3.0.101-108.57.1
kernel-default-devel-3.0.101-108.57.1
kernel-source-3.0.101-108.57.1

Upgrade to iManager 2.7.7.11 hoping that would be the solution, but problem continued so we had to revert the kernel patches back to the prior version.

Core is here: http://susepaste.org/15554366

Anyone else run into anything similar ?


Saw similar here after the latest SLES11Sp4 patches were applied. iManager 2.7 will run for a little while, but then randomly dies. Happens when idle. Happens when in use. Doesn't seem to matter.

I upgraded to iManager 3.1.1. That worked. You'll probably need to do that as well.
0 Likes
tomgreene Contributor.
Contributor.

Re: imanager 277X cores on latest SLES 11 SP4 kernel update

According to the documentation iManager 3.X should only be used to manage eDirectory 9.X directories. Not sure what the consequences of using iManager 3.X to manage 8.8.8.X trees is..would be nice. We've seen this issue pop up all over the place.

https://www.netiq.com/documentation/imanager-31/imanager_install/data/b18oit3b.html
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: imanager 277X cores on latest SLES 11 SP4 kernel update

On 10/01/2018 12:44 PM, tomgreene wrote:
>
> According to the documentation iManager 3.X should only be used to
> manage eDirectory 9.X directories. Not sure what the consequences of
> using iManager 3.X to manage 8.8.8.X trees is..would be nice. We've seen
> this issue pop up all over the place.
>
> https://www.netiq.com/documentation/imanager-31/imanager_install/data/b18oit3b.html


To be clear, that link points to the system requirements page. While
iMangaer 3.1 in particular is probably only extensively tested with
eDirectory 9.x, it works just fine with eDirectory 8.8 in general, but you
MUST NOT install the two on the system system (thus "system requirements")
and the reason is that iManager 3.x uses NICI 3.x and eDirectory 8.8 is
too old for NICI 3.x. Mixing the two WILL likely break eDirectory until
you revert to NICI 2.7, which will break iManager.

For what it is worth, the same applies to iManager Workstation. If you
have eDirectory 8.8 on a Linux box and you want to use iManager
Workstation 3.x you cannot since you must upgrade NICI for iManager to
work, which will likely break eDirectory.

--
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
tomgreene Contributor.
Contributor.

Re: imanager 277X cores on latest SLES 11 SP4 kernel update

Yes great point. It's the NICI situation!
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.