I've seen this same behavior when there was no fault. Yes, I created the task via the API.
I just looked into this a little bit more and it looks to be an issue with how v1.0 and v1.1 handle tasks. In the specific instance of file upgrades, (for some odd reason) I was setting the _id to be the ACS ID for the device (I honestly have no clue why I did that). Obviously this is incorrect behavior on my part. This caused no issues with v1.0 but obviously causes issues with v1.1. So I removed the explicit setting of the ID. I retested everything and it works fine now. I apologize for the troubles. -dan On Mon, Jun 5, 2017 at 11:13 AM, Zaid Abdulla <[email protected]> wrote: > On Thu, 2017-06-01 at 13:52 -0800, Dan Morphis wrote: > > I'm trying to do firmware/config upgrades with genie from master (as > > of 2 weeks ago). The modem successfully downloads the config file and > > reboots. Modem comes back online in the BOOTSTRAP state, and then > > genie sends the file to the CPE again, repeat over and over. > > The logs show an exception. That explains why the task is never cleared > as tasks are cleared at the end of the session. > > Could you update the function clearTasks in db.coffee to print the > value of taskIds console.dir()? For some reason the task ID is not a > valid Mongo ID and that's causing the exception. I assume you inserted > the task through the API, right? > > -- > Zaid Abdulla <[email protected]> > _______________________________________________ > Users mailing list > [email protected] > http://lists.genieacs.com/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.genieacs.com/mailman/listinfo/users
