Dataclay — Automating Digital Production
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Register
    • Login

    Unusual terminal prompt interferes with the bot

    Scheduled Pinned Locked Moved
    Templater Bot Deployment
    2
    2
    250
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Viriatoundefined
      Viriato
      last edited by Viriato

      Hello, this past week, Templater bot seems to stop working after a certain number of hours. While trying to investigate the cause, I’ve found that a terminal is opened and remains open until it is manually closed. Attached is an image of said prompt.

      Any help in determining what it is and if/how it may interfere with proper functionality of Templater would be greatly appreciated. Thank you!

      Templater.png

      Jeffundefined 1 Reply Last reply Reply Quote 0
      • Jeffundefined
        Jeff @Viriato
        last edited by

        @viriato

        The terminal window in that screenshot is an indication that Templater Bot is executing an Event Script at some point during the versioning process. Typically, when a Shell Script is registered to an event, it’ll be wrapped up in a command named templater-event-cmd.bat and run at the appropriate time during the Templater process.

        If this window is causing the process to hang up or fail, it likely has to do with one of the registered Event Scripts in Templater Bot. In order to figure out what’s happening here, we’ll likely need to take a look at any Shell Scripts registered with Templater. We’ll also need to see how those scripts are being invoked to get a clearer idea of what could be causing the issue.

        If you’d like, you can post that information here, but if you’d like to get in touch with us directly so as not to share this data on a public forum, you can always email us at support@dataclay.com.

        Hopefully, with a bit more information on how things are configured, we should be able to track down what’s causing this issue.

        Thanks!

        1 Reply Last reply Reply Quote 0
        • First post
          Last post