Session took too long to respond error when we commiting 100 paramter

1

Hi,
Iam getting the "Session took too long to respond error when we commiting 100 paramter " error frequently. @zaidka

Does CPE device need reboot after a successfull commit ?

2

The ACS doesn’t trigger a reboot. But it’s possible that the CPE decides to reboots itself if it deems necessary after changing certain parameters. It’s entirely at the discretion of the CPE.

3

My experience has been its always best to reboot the CPE after provisioning. Some of them straight up act really weird when setting up things like PPPoE. Example, SmartRG CPEs will continue to try and auth PPPoE even after successfully authenticating PPPoE and traffic is being routed. Other times, the CPEs will be in this half-assed working state and rebooting them without making any other changes causes things to work successfully.

1 Like
4

Iam getting the "Session took too long to respond error when we commiting 100 paramter " error frequently. @zaidka any explaination?

5

Hi ,
Can you please respond my query @zaidka

6

you had same error using GitHub - genieacs/genieacs-sim: TR-069 client simulator for GenieACS instead a real CPE? maybe the CPE is just not good enough to process this amount of data and end the session before finish the processing.

7

@Regin to add to what @cdavid14 said, try adding the following config to admin/config

key: cwmp.gpnNextLevel value: 3
key: cwmp.gpvBatchSize value: 24

This will cause genieacs to send smaller batches of data to the CPE.

-dan

2 Likes
8

we tried but getting same error. does this issue related to mongoDB? Because, when we trying 100 commit , the system get stock some times
.