Skip to main content
laurenceb72990977
laurenceb72990977
Participant
April 12, 2017
Answered

AME - debug logging and "Timeout while creating encoder group"

  • April 12, 2017
  • 2 replies
  • 1204 views

Hi All,

Apologies if this has already been answered somewhere else. We're running a set of 4 AME conforming engines running the latest edition of AME 2017. They're being fed jobs from our asset management system via the webservice & network-based storage and 98% of the time they transcode correctly with no problems. Occasionally we get a failure where it states in the console window "Creating Encoder - Timeout while creating encoder group" and it fails the job.

Is there any way of turning on any sort of debug logging in AME? There's nothing about this error in the encoding log and nothing at all in the error log.

The AME instances are running on a combination of VMs running server 2012 and Dell servers running 2008 R2. I believe it's more of an issue with our media management system but if there's anyway to get some more information out of AME it'd be greatly appreciated.

Thanks

    This topic has been closed for replies.
    Correct answer Sven S

    Please try to use the --help option on the command (currently not working in 23.x). There is a value "func_call_timeout_ms" you can add to the .ini file. Default is 5000 = 5 sec. Check if longer values, e.g. 20000 = 20 sec, could help for the network cases.

     

    2 replies

    robbertf52910312
    robbertf52910312
    Participant
    March 27, 2023

    Same problem here, really frustrating. It works sometimes with local sources, but it doens't work on the server / network.

    It also does not work with AWS Thinkbox Deadline. Please Adobe, have a look...

      J
      jimd91757313
      Participating Frequently
      March 24, 2023

      Getting the same error here "Timeout while creating encoder group" any idea how to fix this issue? Is it possible to set a longer timeout?

        S
        Community Manager
        Sven SCommunity ManagerCorrect answer
        Community Manager
        March 27, 2023

        Please try to use the --help option on the command (currently not working in 23.x). There is a value "func_call_timeout_ms" you can add to the .ini file. Default is 5000 = 5 sec. Check if longer values, e.g. 20000 = 20 sec, could help for the network cases.

         

          J
          jimd91757313
          Participating Frequently
          March 27, 2023

          This "func_call_timeout_ms" worked thanks! But I still cant get any --help info out of the "ame_webservice_console.exe" file. Am I missing something here?

          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices