Scripting driver doesn't start

Hello,

My scripting driver stopped to work in my production environment without reason one week ago.

I stopped it through iManager and I tried to restart it.

The green icon is now flashing in iManager and the driver doesn't write in the log file.

It's not a permission issue because other drivers are able to write some logs.

I checked the status driver with dxcmd and I saw my driver is in starting status.

As I am in production i can't restart the driver or the service.

Do you have any ideas ?

For information, I work with IDM 4.6.2 (Driver is in version 4.0.3.1) on RHEL 7.3.

Thanks in advance.
  • As always, post a level three (3) trace so we can try to figure it out.
    Otherwise, without any real data from the system, it's impossible to give
    you anything conclusive, especially if it used to work.

    Once in a great while a driver object's thread can become stuck, and
    usually it fixes itself within a few minutes, but if not then in the past
    I've had to restart eDirectory to resolve the issue, but it's been a long
    time. Since something in production is down (your scripting driver), and
    since restating eDirectory only takes a minute or two, this may be a good
    reason for a quick change order.

    --
    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.
  • bprulhiere <bprulhiere@no-mx.forums.microfocus.com> wrote:
    >
    > I checked the status driver with dxcmd and I saw my driver is in

    starting status.
    >
    > As I am in production i can't restart the driver or the service.
    >
    > Do you have any ideas ?
    >


    Yes. We have seen issues like this. Basically it is waiting for the other
    side to connect or timeout. (Which never happens in this scenario)

    On Windows we have had success with the following:

    Restarting the scripting driver on RL side.

    If that doesnâ€Tmt work.

    forcing closed the network connection from IDM to scripting driver RL
    (usually something like tcp port 809x with destination IP that matches your
    RL). Used a sysinternals tool for that.
    Dunno how to do that cleanly on Linux.

    We got a Windows hotfix from Micro Focus to correct the underlying problem.
    Donâ€Tmt know if that made it into a shipping release yet.