drive mapping not working after restart

Viewing 4 posts - 1 through 4 (of 4 total)
  • 22nd August 2019 at 8:22 pm #20736

    Since we are on Muster 9 (before we were still on 5) we loose the drive mapping on a machine after restart of the machine.
    After restarting a machine it starts the render service and the machine comes available for rendering in the dispatcher.
    When it gets a job, it starts rendering and then aborts because it can not find the mapped drive.

    When i then restart the render service on the machine it works fine.
    It happens with all of our render nodes and workstations.

    Is this a known problem?

    23rd August 2019 at 10:38 am #20766

    No this is not a known problem. Check your renderclient.log file just after the first restart (when the Drive mappings is supposed to not being mapped), it should report a reason for not mapping the drive. Maybe when you restart the machine the network services are still not up on the drive mapping side ?

    28th August 2019 at 9:38 am #20999

    Thank you Leonardo,
    I will have a look at it.
    Could be that de networkdrive are not available at that moment.
    Is there a way to let the service wait for some time?

    28th August 2019 at 1:27 pm #21007

    Well that’s part of the regular windows startup process, you can bypass the problem by configuring the drive mappings mounting at job startup instead of service startup, this will mount/unmount the drives before a job starts and I think they will be available at that moment

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.