We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.

Why are my API responses timing out / Why am I getting a 500 read timeout from my Email Security Gateway?

  • Type: Knowledgebase
  • Date changed: 7 months ago
Solution #00005460

Scope:
Email Security Gateway with API firmware 4.1 or later.

Answer:
Some requests sent via the API, such as the varlist request or the user.list request, may generate a large amount of data as a response.  This can cause a timeout when using the XML::RPC module because the XML::RPC module uses a default hard-coded timeout value of 10 seconds in the TreePP.pm module which it depends on.

To fix this you must manually edit your TreePP.pm module within the site_perl/perl_ver/XML folder in your server. A value of at least 120 seconds is recommended, but you may need up to 300 seconds (the default HTTP response timeout for most other operations).

For example, if your Barracuda has over 20,000 users on it and you attempt to get a user.list from the API, it likely that the request will timeout with a 500 READ TIMEOUT from apache. However, after increasing the timeout value from 10 seconds to 120 seconds or more you should get the user list as expected.

Link to this page:
https://campus.barracuda.com/solution/50160000000IPhVAAW