

Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2018-11-03
18:02
379 views
eDir core when stopping DCS driver
Hello,
Had something odd happen today, I was import a LDIF file containing
about 1 million users, it was at about 780 000 when I decided I wanted
to stop the DCS driver because the Reporting database was having some
issues.
When I clicked Stop, eDirectory stopped responding.
No core file was created even though the hs_err_pid file tells me it
should be here:
/var/opt/novell/eDirectory/data/dib/core or core.2145
This is SLES12SP3 with IDM 4.7.1.
ulimit reports unlimited
I would really like a core file next time, what can I do?
This is from the hs_err_pid file:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fc68c3ff2b8, pid=2145, tid=0x00007fc633683700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_172-b11) (build
1.8.0_172-b11)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.172-b11 mixed mode
linux-amd64 compressed oops)
# Problematic frame:
# C [libzoomdb.so+0x292b8] FlmRecordRetrieve(void*, unsigned long,
unsigned long, unsigned long, FlmRecord**, unsigned long*)+0x78
#
# Core dump written. Default location:
/var/opt/novell/eDirectory/data/dib/core or core.2145
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
--------------- T H R E A D ---------------
Current thread (0x000000001281d000): JavaThread "DCS-CacheReader"
[_thread_in_native, id=3938, stack(0x00007fc633583000,0x00007fc633684000)]
siginfo: si_signo: 11 (SIGSEGV), si_code: 128 (SI_KERNEL), si_addr:
0x0000000000000000
Thanks.
-alekz
--
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
Had something odd happen today, I was import a LDIF file containing
about 1 million users, it was at about 780 000 when I decided I wanted
to stop the DCS driver because the Reporting database was having some
issues.
When I clicked Stop, eDirectory stopped responding.
No core file was created even though the hs_err_pid file tells me it
should be here:
/var/opt/novell/eDirectory/data/dib/core or core.2145
This is SLES12SP3 with IDM 4.7.1.
ulimit reports unlimited
I would really like a core file next time, what can I do?
This is from the hs_err_pid file:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fc68c3ff2b8, pid=2145, tid=0x00007fc633683700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_172-b11) (build
1.8.0_172-b11)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.172-b11 mixed mode
linux-amd64 compressed oops)
# Problematic frame:
# C [libzoomdb.so+0x292b8] FlmRecordRetrieve(void*, unsigned long,
unsigned long, unsigned long, FlmRecord**, unsigned long*)+0x78
#
# Core dump written. Default location:
/var/opt/novell/eDirectory/data/dib/core or core.2145
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
--------------- T H R E A D ---------------
Current thread (0x000000001281d000): JavaThread "DCS-CacheReader"
[_thread_in_native, id=3938, stack(0x00007fc633583000,0x00007fc633684000)]
siginfo: si_signo: 11 (SIGSEGV), si_code: 128 (SI_KERNEL), si_addr:
0x0000000000000000
Thanks.
-alekz
--
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
3 Replies


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2018-11-03
18:05
Just restarted eDir, DCS is set to autostart so I clicked Stop once again.
It crashed.
I can see the following process when running top indicating that some
kind of coredump is being created:
/usr/lib/systemd/systemd-coredump 16943 0 0 6 1541268195
18446744073709551615 ndsd
--
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
It crashed.
I can see the following process when running top indicating that some
kind of coredump is being created:
/usr/lib/systemd/systemd-coredump 16943 0 0 6 1541268195
18446744073709551615 ndsd
--
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2018-11-04
17:20
Hi Alekz,
How many servers you have in your tree?
I just imported a million objects. Maybe you have a huge sync traffic?
What about consumed memory?
How many servers you have in your tree?
I just imported a million objects. Maybe you have a huge sync traffic?
What about consumed memory?


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2018-11-04
23:18
Be sure you have gone over the systemd bits here:
https://support.microfocus.com/kb/doc.php?id=3078409
Anything interesting in /var/lib/systemd/coredump/ ?
--
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.
https://support.microfocus.com/kb/doc.php?id=3078409
Anything interesting in /var/lib/systemd/coredump/ ?
--
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.