Home

Results 1 to 4 of 4

Thread: Strange behavior of AD driver

Hybrid View

  1. #1
    orisela NNTP User

    Strange behavior of AD driver


    Hey,
    Something really strange happened to my AD driver today. This morning
    our user complained AD accounts were not created, so I looked at the
    driver status using "dxcmd". It showed driver as running, but I did not
    see anything transaction being processed for that AD driver using
    iMonitor. I stopped the driver using "dxcmd" successfully. When I
    started the driver, the status for the AD driver stayed at "starting
    and
    did not change to "running".
    I had to restart ndsd to solve the issue.

    running on IDM 4.01, eDirectory 8.8.6 on redhat linux.


    Thanks,
    Ori


    --
    orisela
    ------------------------------------------------------------------------
    orisela's Profile: https://forums.netiq.com/member.php?userid=6751
    View this thread: https://forums.netiq.com/showthread.php?t=51583


  2. #2

    Re: Strange behavior of AD driver

    orisela wrote:

    > Something really strange happened to my AD driver today. This morning
    > our user complained AD accounts were not created, so I looked at the
    > driver status using "dxcmd". It showed driver as running, but I did not
    > see anything transaction being processed for that AD driver using
    > iMonitor. I stopped the driver using "dxcmd" successfully. When I
    > started the driver, the status for the AD driver stayed at "starting
    > and
    > did not change to "running".
    > I had to restart ndsd to solve the issue.


    This happens sometimes, usually when you force a driver that is not responding
    to stop. Restarting ndsd is what helps, as you already found out by yourself.

  3. #3
    Alex McHugh NNTP User

    Re: Strange behavior of AD driver

    Lothar Haeger wrote:

    > orisela wrote:
    >
    > > Something really strange happened to my AD driver today. This morning
    > > our user complained AD accounts were not created, so I looked at the
    > > driver status using "dxcmd". It showed driver as running, but I did not
    > > see anything transaction being processed for that AD driver using
    > > iMonitor. I stopped the driver using "dxcmd" successfully. When I
    > > started the driver, the status for the AD driver stayed at "starting
    > > and
    > > did not change to "running".
    > > I had to restart ndsd to solve the issue.

    >
    > This happens sometimes, usually when you force a driver that is not responding
    > to stop.


    Sometimes it can help to stop the remote loader instance for that driver first, then try to stop the driver on the engine side. That seems to be more reliable.

    There may also be some fixes in more recent engine/remote loader patches, so make sure you are as up to date as possible.


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

  4. #4
    Join Date
    Dec 2007
    Location
    Brooklyn, NY
    Posts
    6,213

    Re: Strange behavior of AD driver


    > There may also be some fixes in more recent engine/remote loader patches, so make sure you are as up to date as possible.


    There is some class that all HTTP communicating drivers (more than you
    would think!) consume that had an issue when stopping the driver and
    recent patches fixed that. Though the eDir driver was one of them as I
    recall.

    But I do not recall it affecting the AD driver.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •