Error: application timeout message from ConfD

[arun88]

I have a ConfD action command that looks something like

move log-file-name to flash:

I call this command via maapi after opening a CLI session with ConfD. The command handler is external to ConfD and is in a C file that performs the action (moving a log file at the provided path to another location). When I run this command, I occasionally see a response that says “Error: application timeout”. Could you help me understand what this problem is about and how to get around this? Is there a timeout value I can add if you think the error message could be due to the move operation taking too long in the external application (because the log file is huge)?

[cohult]

Here is one of the answers to this common question/issue:

How to increase time out for one specific command

Hello, /confdConfig/capi/queryTimeout is by default set to 120 seconds and can be modified in the confd.conf. This applies for all data callbacks. In case one data callback (I assume your operational command is implemented as data callback) needs to increase the timeout, the confd_data_set_timeout function can be used. See documentation for confd_lib_dp. Copied description: A data callback should normally complete "quickly", since e.g. the execution of a 'show' command in the CLI may requi…

[arun88]

@cohult, Thanks. But what confuses me is that mine is an action command (meaning the command does not fetch operational information but rather asks an external application to perform an action). In other words, it is not a “show…” command. Is it still called an “Oper” command in ConfD parlance?

Also, I tried putting a sleep in the external application that causes a delay of more than 10 mins in responding to the command and that did not trigger this response message for the command. This tells me that it is not a timeout issue. Is this message generated by ConfD internally? Under what circumstances does ConfD return this message? (Error: application timeout)?

[arun88]

@cohult, did you get a chance to look into this?

[cohult]

@cohult, Thanks. But what confuses me is that mine is an action command (meaning the command does not fetch operational information but rather asks an external application to perform an action). In other words, it is not a “show…” command. Is it still called an “Oper” command in ConfD parlance?

Yes, DP API. See confd.conf(5) man page for details on the timeout. See also the confd_lib_dp(3) man page on how to override and set the timeout from the action daemon/code.

Also, I tried putting a sleep in the external application that causes a delay of more than 10 mins in responding to the command and that did not trigger this response message for the command. This tells me that it is not a timeout issue. Is this message generated by ConfD internally? Under what circumstances does ConfD return this message? (Error: application timeout)?

The timeout log entry would be seen in for example the developer log.
The timeout trigger if the application doesn’t extend it.