jtl1 Absent Member.
Absent Member.
399 views

Problem adding a 887 server to existing tree

Hello,

I have problems adding a new 887 server to an existing tree. ndsd crashes after a short period and ndsd.log doesn't give any
clues why. I've increased the log level and ndsd.log just shows SYNC events.

The new server is a SLES11SP2 server and the existing servers are all OES2SP2 with 885 patch 6 installed.

Anyone having a clue or have seen the same?

Best regards,
Tobias
Labels (1)
0 Likes
9 Replies
Knowledge Partner
Knowledge Partner

Re: Problem adding a 887 server to existing tree

On Wed, 27 Jun 2012 12:17:33 +0000, Tobias Ljunggren wrote:

> Anyone having a clue or have seen the same?


I'm currently avoiding 887, but you might need to collect a coredump and
open an SR on this one.

--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.novell.com

Please post questions in the forums. No support provided via email.

0 Likes
jtl1 Absent Member.
Absent Member.

Re: Problem adding a 887 server to existing tree

On 2012-06-27 15:30, David Gersic wrote:
> On Wed, 27 Jun 2012 12:17:33 +0000, Tobias Ljunggren wrote:
>
>> Anyone having a clue or have seen the same?

>
> I'm currently avoiding 887, but you might need to collect a coredump and
> open an SR on this one.
>

We have a couple of installations with eDir 887 and until now it has been stable.

I've opened a SR.

The gdb command output shows:
"Core was generated by `/opt/novell/eDirectory/sbin/ndsd'.
Program terminated with signal 11, Segmentation fault.
#0 0x00007f8b7a9e704e in WNPutInt32 () from /opt/novell/eDirectory/lib64/nds-modules/libnds.so"

Doesn't look good...
0 Likes
Knowledge Partner
Knowledge Partner

Re: Problem adding a 887 server to existing tree

On Wed, 27 Jun 2012 13:34:29 +0000, Tobias Ljunggren wrote:

> On 2012-06-27 15:30, David Gersic wrote:
>> On Wed, 27 Jun 2012 12:17:33 +0000, Tobias Ljunggren wrote:
>>
>>> Anyone having a clue or have seen the same?

>>
>> I'm currently avoiding 887, but you might need to collect a coredump
>> and open an SR on this one.
>>

> We have a couple of installations with eDir 887 and until now it has
> been stable.


That's good to hear. I don't have time to test it here at the moment, too
many other projects going on. I do want to go to it for the enhanced
"microsoft complexity" password support. On the other hand, the changes
in how it handles delegation of "password management" rights would be a
problem for me. So for the moment, I'm holding off.


> I've opened a SR.


Good, thanks. Let us know what turns up from that.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.novell.com

Please post questions in the forums. No support provided via email.

0 Likes
Knowledge Partner
Knowledge Partner

Re: Problem adding a 887 server to existing tree

This is from the readme for eDir, it talks about signal 11, might help you:

eDirectory Dumps the Core on Loading xdasauditds When the Syslog
Appender Is Disabled

Install and configure eDirectory, then configure the xdasproperties
file. Ensure that the syslog appender is enabled as follows:

log4j.appender.S=org.apache.log4j.net.SyslogAppender
Disable Layout definition for appender Syslog S as follows:

# Layout definition for appender Syslog S.
log4j.appender.S.layout=org.apache.log4j.PatternLayout
#log4j.appender.S.layout.ConversionPattern=%c : %p%m%n
When you attempt to load xdasauditds, eDirectory starts dumping the core
and the program is terminated with signal 11.

This issue arises because log4cxx does not check for the existence of
layout in the xdasproperties file before setting it up. It assumes that
Layout definition for appender Syslog S is automatically enabled if the
syslog appender is enabled in the xdasproperties file.

On 27/06/2012 15:34, Tobias Ljunggren wrote:
> On 2012-06-27 15:30, David Gersic wrote:
>> On Wed, 27 Jun 2012 12:17:33 +0000, Tobias Ljunggren wrote:
>>
>>> Anyone having a clue or have seen the same?

>>
>> I'm currently avoiding 887, but you might need to collect a coredump and
>> open an SR on this one.
>>

> We have a couple of installations with eDir 887 and until now it has
> been stable.
>
> I've opened a SR.
>
> The gdb command output shows:
> "Core was generated by `/opt/novell/eDirectory/sbin/ndsd'.
> Program terminated with signal 11, Segmentation fault.
> #0 0x00007f8b7a9e704e in WNPutInt32 () from
> /opt/novell/eDirectory/lib64/nds-modules/libnds.so"
>
> Doesn't look good...


0 Likes
jtl1 Absent Member.
Absent Member.

Re: Problem adding a 887 server to existing tree

Hi,

Did that but it doesn't help. I removed the server from all replica rings yesterday and removed server objects from the
directory and re-installed it completely.

One thing I noticed is that it runs perfectly until I add a partition.
There are 10 servers in the tree so the new one doesn't get any partitions by default but as soon as I tried to add a replica
for the Security partition if cored almost immediately.

Best regards,
Tobias

On 2012-06-27 21:26, alekz wrote:
> This is from the readme for eDir, it talks about signal 11, might help you:
>
> eDirectory Dumps the Core on Loading xdasauditds When the Syslog
> Appender Is Disabled
> [...]

0 Likes
jtl1 Absent Member.
Absent Member.

Re: Problem adding a 887 server to existing tree

Just got a reply from support. This seems to be caused by a known issue when adding a replica for a partition that already has
quite some servers on it.

I've applied a FTF we got and so far it seems to be working fine.

Best regards,
Tobias

On 2012-06-27 14:17, Tobias Ljunggren wrote:
> Hello,
>
> I have problems adding a new 887 server to an existing tree. ndsd crashes after a short period and ndsd.log doesn't give any
> clues why. I've increased the log level and ndsd.log just shows SYNC events.
>
> The new server is a SLES11SP2 server and the existing servers are all OES2SP2 with 885 patch 6 installed.
>
> Anyone having a clue or have seen the same?
>
> Best regards,
> Tobias



0 Likes
Knowledge Partner
Knowledge Partner

Re: Problem adding a 887 server to existing tree

On Thu, 28 Jun 2012 09:59:27 +0000, Tobias Ljunggren wrote:

> Just got a reply from support. This seems to be caused by a known issue
> when adding a replica for a partition that already has quite some
> servers on it.


Oh, great. Did they give you a bug number?


> I've applied a FTF we got and so far it seems to be working fine.


Thanks for the followup. That's good to know.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.novell.com

Please post questions in the forums. No support provided via email.

0 Likes
jtl1 Absent Member.
Absent Member.

Re: Problem adding a 887 server to existing tree

Yes, 763802

Best regards,
Tobias

On 2012-06-28 16:00, David Gersic wrote:
> On Thu, 28 Jun 2012 09:59:27 +0000, Tobias Ljunggren wrote:
>
>> Just got a reply from support. This seems to be caused by a known issue
>> when adding a replica for a partition that already has quite some
>> servers on it.

>
> Oh, great. Did they give you a bug number?
>
>
>> I've applied a FTF we got and so far it seems to be working fine.

>
> Thanks for the followup. That's good to know.
>
>



0 Likes
jtl1 Absent Member.
Absent Member.

Re: Problem adding a 887 server to existing tree

Patch 1 just released but this bug isn't fixed, not according to http://www.novell.com/support/kb/doc.php?id=3426981


On 2012-06-28 17:25, Tobias Ljunggren wrote:
> Yes, 763802
>
> Best regards,
> Tobias
>
> On 2012-06-28 16:00, David Gersic wrote:
>> On Thu, 28 Jun 2012 09:59:27 +0000, Tobias Ljunggren wrote:
>>
>>> Just got a reply from support. This seems to be caused by a known issue
>>> when adding a replica for a partition that already has quite some
>>> servers on it.

>>
>> Oh, great. Did they give you a bug number?
>>
>>
>>> I've applied a FTF we got and so far it seems to be working fine.

>>
>> Thanks for the followup. That's good to know.
>>
>>

>
>


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.