Just updated to latest master, error is still happening. I'll look at the
CPEs next.
Okay, I think I discovered the issue. Some leftover cruft from our old
setup was a button that added a task to run a custom command. That custom
command no longer exists in our v1.1 setup. When genie tries to run that
cmd it dies. Does customCommand now run the external script?
{"_id":"591b38c84671d3617e044721","name":"customCommand","command":
"refresh_params init true","device":"3c9066-96318REF-SR360NA016%2D5008049",
"timestamp":"2017-05-16T17:37:12.836Z"},
RangeError: Maximum call stack size exceeded
at Object.clearProvisions
(/usr/lib64/node_modules/genieacs/lib/session.js:407:27)
at /usr/lib64/node_modules/genieacs/lib/cwmp.js:463:13
at Object.rpcRequest
(/usr/lib64/node_modules/genieacs/lib/session.js:704:12)
at nextRpc (/usr/lib64/node_modules/genieacs/lib/cwmp.js:424:18)
at /usr/lib64/node_modules/genieacs/lib/cwmp.js:540:14
at Object.rpcRequest
(/usr/lib64/node_modules/genieacs/lib/session.js:704:12)
at nextRpc (/usr/lib64/node_modules/genieacs/lib/cwmp.js:424:18)
at /usr/lib64/node_modules/genieacs/lib/cwmp.js:540:14
at Object.rpcRequest
(/usr/lib64/node_modules/genieacs/lib/session.js:704:12)
at nextRpc (/usr/lib64/node_modules/genieacs/lib/cwmp.js:424:18)
session.js:704
703 if (sessionContext.virtualParameters.length === 0 &&
sessionContext.declarations.length === 0 && !(_declarations != null ?
_declarations.length : void 0) && (sessionContext.doneProvisions ||
sessionContext.provisions.length === 0)) {
704 return callback();
705 }
cwmp.js:424
423 nextRpc = function(sessionContext) {
424 return session.rpcRequest(sessionContext, null, function(err,
fault, id, acsRequest) {
425 var alias, channel, flags, j, l, len, len1, len2, len3, m, n,
o, p, ref, ref1, ref2, ref3, ref4, t, task, taskId;
On Tue, May 16, 2017 at 3:50 PM, Zaid Abdulla <[email protected]> wrote:
> Are you on the latest master? I made some fixes recently around that
> part of the code so maybe this one has already been addressed.
>
> I think you may be able to find which device caused this error by
> looking at the last few requests before every one of these exceptions
> happened (or last 5 or so) and find which device doesn't have its last
> inform parameter updated.
>
> --
> 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
