Exported resource collection timing out

[Huaqing Zheng]

I have a server that's collecting exported resources (icinga/nagios configurations) but it's frequently timing out with:

Error: Could not retrieve catalog from remote server: Timeout::Error

Warning: Not using cache on failed catalog

Error: Could not retrieve catalog; skipping run

Any ideas about how to extend the timeout?

--

Huaqing Zheng
Code Wrangler

[Matthew Schmitt]

In the past, I’ve added a time to my puppet agent run and then adjusted this setting in puppet.conf - configtimeout

I believe the default is 2 minutes, so if your collection is taking longer, you’ll hit the timeout error.

Matt

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAKSYJTN_3-gBk%3DoesSgu%2B%2Bfiz%2BxF3zefZ5GYP3cGgiE6Kz4hXA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Huaqing Zheng]

Documentation says

configtimeout

How long the client should wait for the configuration to be retrieved before considering it a failure. This setting is deprecated and has been replaced by http_connect_timeout and http_read_timeout. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).

Default: 2m

I'll try tweaking http_read_timeout.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/EB465765-21E8-4496-A815-1DD9B74958DB%40gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Ken Barber]

> Documentation says
>
> configtimeout
>
> How long the client should wait for the configuration to be retrieved before
> considering it a failure. This setting is deprecated and has been replaced
> by http_connect_timeout and http_read_timeout. This setting can be a time
> interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or
> years (5y).
>
> Default: 2m
>
> I'll try tweaking http_read_timeout.

The other side of this coin is, improve the time it takes to return
the answer :-). I presume you are using PuppetDB for this? Perhaps
some performance improvements can be made on that end of the stack.
Have you looked into why the queries are taking so long to return yet?

ken.