PREMIUM getting "Configuration Saved Notification. Rules could not be loaded"

Follow

Juned Shaikh

• July 21, 2020 01:54

"Configuration Saved Notification. Rules could not be loaded. Please try again" and wizard is stuck at attempt to save the config

 

any pointers?

 

Thanks in advance

0

• Official comment

  

  Matt

  • July 21, 2020 17:19

  Hi Juned,

  This we see when there's high cpu utilization on the firewall which results in slow response times from the backend APIs. 

  If that's not the case for you, shoot a PR and team will have a look.

  Comment actions Permalink
• 

  Juned Shaikh

  • July 22, 2020 13:59

  the cpu utilization doesn't even mount to 1% 

  0

  Comment actions Permalink
• 

  Matt

  • July 22, 2020 17:51

  Hi Juned, looking at your issue report; it looks like the engine was in "stopped status" for some time. Chances are high that you tried to do a configuration change at this time. UI tried to communicate the new configuration with the engine which was not up and running and this caused a connection error. 

  We think that we need a UX improvement here in the sense that UI should be providing a more meaningful error stating that the engine is down and changes will take effect as soon as you start the packet engine. 

   

  0

  Comment actions Permalink

Please sign in to leave a comment.