Palo Alto Networks Knowledgebase: Slow or Failed Commits

Slow or Failed Commits

8853
Created On 02/07/19 23:47 PM - Last Updated 02/07/19 23:47 PM
Content Release Deployment
Resolution

Issue

Sometimes commits become slow or fail entirely. The following devsrv.log example shows the pan_util.c call fails to connect to the devsrv and phase1 is not passed along.

2181 root 20 0 975m 11m 1468 S 2 1.2 196:53.46 cryptod 9620 root 20 0 798m 127m 39m S 2 12.9 97:40.63 devsrvr 1 root 20 0 1832 560 532 S 0 0.1 0:12.83 init
mp\devsrv.log 10-17 17:20:15 Error: pan_util_connect_server(pan_util.c:1776): Failed to connect to server: Connection refused
mp\devsrv.log 10-17 17:20:15 Error: pan_util_connect_server(pan_util.c:1776): Failed to connect to server: Connection refused
mp\devsrv.log 10-17 17:20:15 Error: pan_util_connect_server(pan_util.c:1776): Failed to connect to server: Connection refused
mp\devsrv.log 10-17 17:20:21 Error: pan_util_connect_server(pan_util.c:1776): Failed to connect to server: Connection refused
mp\devsrv.log 10-17 17:20:21 Error: pan_util_connect_server(pan_util.c:1776): Failed to connect to server: Connection refused
mp\devsrv.log 10-17 17:20:21 Error: pan_util_connect_server(pan_util.c:1776): Failed to connect to server: Connection refused
mp\devsrv.log 10-17 17:20:23 SIGTERM triggered
mp\devsrv.log 10-17 17:20:23 DEVSRV: connection to MS terminated
mp\devsrv.log 10-17 17:21:00 BrightCloud URL engine startup... mp\devsrv.log 10-17 17:21:01 pan_shmgr_merge_with_peer(runtime.user-idmgr) begin
mp\devsrv.log 10-17 17:21:35 BrightCloud URL filtering engine started
mp\devsrv.log 10-17 17:22:05 Config commit phase1 started

 

Resolution

Use the following command to check for high memory use by the devsrvr process:

> show system resources | match devsr

2672       20   0  172m  67m  13m S    0  1.7   7:00.84 devsrvr

 

Restart the device server with the following command, if necessary:

> debug software restart device-server

After the process restarts, phase1 is sent and the commit can be completed.

 

Note: The devsrvr process is running on the management plane, which takes care of pushing configurations to the dataplane. It is also in charge of some communication between the management plane and the dataplane, such as URL filtering request response.

 

owner: rkalugdan



Attachments
Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Clu8CAC&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail

Attachments
Choose Language