Novell Home

My Favorites

Close

Please to see your favorites.

NDSD process dies after creating DirXML driver set.

(Last modified: 01Apr2003)

This document (10065041) is provided subject to the disclaimer at the end of this document.

fact

Solaris 8

Solaris 2.6

eDirectory  85.15

DirXML 1.0

symptom

NDSD process dies after creating DirXML driver set.

The NDSD process will crash periodically, occurs typically when a sync cycle happens.

change

Reconfigured DirXML

cause

The following information pertains to a truss file taken showing the NDSD process being killed:

open("216089.TAO", O_RDWR)                        = 54
The line above indicates that the TAO cache file has been opened.

nanosleep(0xEA001CA8, 0x00000000)                = 0
lwp_sema_wait(0xE7C01E78)                        = 0
fstat(54, 0xEB800ED0)                                = 0
lseek(54, 0, SEEK_SET)                                = 0
read(54, "FF D X01\0\0\0\0", 8)                        = 8
nanosleep(0xEA001CA8, 0x00000000)                = 0
lseek(54, 0, SEEK_END)                                = 1411240


write(54, "\0\0011C\0\0\0 <\0\0\0 T".., 284)        = 284
At this point a "write" is taking place to the TAO file.

close(54)                                        = 0
nanosleep(0xEA001CA8, 0x00000000)                = 0
time()                                                = 995045744
lwp_sema_wait(0xEC801E78)                        = 0
lwp_sema_post(0xEC801E78)                        = 0
lwp_mutex_lock(0xEF0EB3B0)                        = 0
lwp_mutex_unlock(0xEF0EB3B0)                        = 0
nanosleep(0xEA001CA8, 0x00000000)                = 0
lwp_sema_wait(0xEC801E78)                        = 0
lwp_sema_post(0xEC801E78)                        = 0
lwp_mutex_lock(0xEF0EB3B0)                        = 0
lwp_mutex_unlock(0xEF0EB3B0)                        = 0


Incurred fault #6, FLTBOUNDS %pc = 0xEF0D0BF0
siginfo: SIGSEGV SEGV_MAPERR addr=0x000061E0
time()                                                = 995045744
Received signal #11, SIGSEGV [caught]
siginfo: SIGSEGV SEGV_MAPERR addr=0x000061E0

At this point above in the truss file a memory error has occurred. Fault number 6 is indicative of either an unknown device or address. The SIGSEGV SEGV_MAPERR information indicates that the process has attempted to map addresses beyond the end of the object. Which will effectively kill the process. subsequent retries fail and the NDSD process halts.

nanosleep(0xEA001CA8, 0x00000000)                = 0
sigaction(SIGSEGV, 0xEF0E84AC, 0x00000000)        = 0
time()                                                = 995045744
setcontext(0xEC7FFED8)
time()                                                = 995045744
Incurred fault #6, FLTBOUNDS %pc = 0xEF0D0BF0
siginfo: SIGSEGV SEGV_MAPERR addr=0x000061E0
lwp_sema_post(0xEE909E78)                        = 0
nanosleep(0xEA001CA8, 0x00000000)                = 0
lwp_sema_wait(0xEE909E78)                        = 0
Received signal #11, SIGSEGV [default]
siginfo: SIGSEGV SEGV_MAPERR addr=0x000061E0
lwp_mutex_unlock(0xEF0EB3B0)                        = 0
lwp_mutex_lock(0xEF0EB3B0)                        = 0
        *** process killed ***.

fix

This is indicates that the record that is being written to in the TAO cache file is corrupt,the only resolution to this issue is either renaming/deleting the TAO cache file. An empty TAO file is available upon request from engineering that will prevent resync of information when DirXML is restarted.

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10065041
  • Solution ID: NOVL59388
  • Creation Date: 28Sep2001
  • Modified Date: 01Apr2003
    • NetIQeDirectory

Did this document solve your problem? Provide Feedback