I'm struggling using asynchronus tasks to generate a UCS. I've been through the API reference, and tried exactly what they suggest but something isn't right. I've dug through logs, watched lsof and top while executing the commands to see what happens, and I can't figure out why this isn't working. Searching devcentral hasn't been useful for me either.
I've tried this with 4 different devices, and all exhibit the same behaviour.
I send the POST to start the task, and I get confirmation of the task number and it's state.
Just to check on the task, I get the status and it shows as STARTED which we would expect. It makes no difference in the end result if I check the task before putting into VALIDATING or not.
Once that happens, the API seems to hang a bit as I can't make new API calls for 30 seconds to a minute, and during that time both java and gzip are churning away on a file in /var/tmp/imxxxxx/configsync-2.0-1-Linux-3.10.0862.14.4.7..8664.im. In this last case, the directory was im22934, which doesn't correspond to my requested task that I can tell.
im22934: total 438M drwxr-xr-x. 2 root root 4.0K Aug 16 07:06 . drwxrwxrwt. 31 root root 12K Aug 16 07:13 .. -rw-r--r--. 1 root root 438M Aug 16 07:05 configsync-2.0-1-Linux-3.10.0862.14.4.7..8664.im
{"code":404,"message":"Task not found - ID: 1692187396506186 user: apiadmin","errorStack":[],"apiError":1}%
_____________
I've been through logs and not found any errors. I've tried different users, with and without underscores in the name. Nothing seems to want to work for me.
Thank you for that, I had come across it before but didn't think it fit since my version isn't listed as an affected version, I'm running 16.1.3.3.
I do see TimeoutExceptions all over the restjavad.x.log, for everything I try to do. The POST to create the task, which is successful, the PUT, and the GET to check the status. So it seems that either the system is able to recover from that status sometimes, or sometimes it's just a meaningless message.
The bug lists icrd being busy as a requisite, but this is on 2 different pairs of lab devices. The ones I tested this morning are idle, like.. 0 connections for the last few days idle, and I am the only person sending any kind of API requests to them.
The bug also has no resolution, do you happen to know of any fix? We're currently generating ucs archives and downloading via central bash scripts that I'm seeing occasional issues with, and I'd like to move to using the API.
@BrianWeb If this keeps erroring you might use the following article instead which should allow you to automate the UCS creation as well as copying it off using SFTP.
This is not a direction I can go at this time. I need to be able to initiate from and pull to a central location for hundreds of devices. Installing and maintaining an iapp on each device is not sustainable for us right now.
@BrianWeb - If your post was solved it would be helpful to the community to select *Accept As Solution*. This helps future readers find answers more quickly and confirms the efforts of those who helped. Thanks for being part of our community. Lief
I wouldn't call it solved yet. I'm working with Support to see if we can make this work. currently we're monkeying with api timeouts but at the moment, the only part of the answers here that could be even tangentially considered a solution is to contact support. If that meets the bar to your criteria, I'll mark it as such. I don't believe it does.
