Option 2 is no longer supported in v1.1. On Thu, Oct 5, 2017 at 2:08 AM, Sergio Fernández <[email protected]> wrote:
> Hello, > > There are three methods to debug I am using on a daily basis: > > 1 - stdout/stderr of the genieacs-cwmp process > 2 - After setting "DEBUG":true in config/config.json, viewing the debug > logs generated for each CPE under the debug/ folder. The config.json file > can also be modified to only debug a specific CPE and not all of them. > 3 - tcpdump. The hard way when you see nothing in 1) and in 2). > > Best regards. > > Sergio Fernández Rubio - https://www.linkedin.com/in/sergiofdz/ > (+34) 687 016 994 <+34%20687%2001%2069%2094> > CEO @ ACSdesk > https://acsdesk.com > > 2017-09-05 11:34 GMT+02:00 <[email protected]>: > >> Hi, >> >> >> >> I have a preset configured with: >> >> >> >> Weight: 100 >> >> Events: 0 BOOTSTRAP >> >> >> >> setting PeriodicInformInterval + PeriodicInformEnable and adds a Tag >> called factoryReset. >> >> Our provisioning is looking at the Tag and triggers a bunch of set >> commands via API. >> >> >> >> Sometimes the preset is not executed for whatever reason. How can I debug >> this? >> >> Debug is enabled but I only see the communication between ACS and CPE >> which is looking good. >> >> >> >> Thank you in advance >> >> >> Sven >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.genieacs.com/mailman/listinfo/users >> >> > > _______________________________________________ > Users mailing list > [email protected] > http://lists.genieacs.com/mailman/listinfo/users > >
_______________________________________________ Users mailing list [email protected] http://lists.genieacs.com/mailman/listinfo/users
