- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
12-27-2022 06:17 PM
Cannot commit due to error "Management server failed to send phase 1 to client cord". Any idea what to do with it?
01-03-2023 05:42 PM
i don't think it was the whole mgmt server process. i used this command "debug software restart process cord"
01-04-2023 02:42 AM
Hi @ErrylTobes
Whenever a commit is performed on the firewall, management server is responsible to push the changes to all the respective process. Sometimes this can fail as we see in your case.
This could be because of the cord process not responding or stopped. The best way is to check the status of the processes on the firewall by CLI command "show system software status" which provides the current status.
If the process is stopped, you can restart the process (as you did which resolved the issue) and you can also check the logs (In the mp-log > cord.log), if required.
A similar incident is discussed here.
Regards,
12-28-2022 04:30 AM
HI
Sometimes these errors are due to a process or daemon being busy at the time of pushing, did you try again ? if you did is it still not working ?
01-02-2023 02:32 PM
The error was going for a few days already. Tried to restart the management client cord and it resolved the error.
01-03-2023 04:30 PM
Do you mean you restarted the mgmt server process ?
01-03-2023 05:42 PM
i don't think it was the whole mgmt server process. i used this command "debug software restart process cord"
01-04-2023 01:26 AM
Awesome, not seen that command before, I will remember it for future use!
You should mark your post as answered! thank you for posting the resolution.
01-04-2023 02:42 AM
Hi @ErrylTobes
Whenever a commit is performed on the firewall, management server is responsible to push the changes to all the respective process. Sometimes this can fail as we see in your case.
This could be because of the cord process not responding or stopped. The best way is to check the status of the processes on the firewall by CLI command "show system software status" which provides the current status.
If the process is stopped, you can restart the process (as you did which resolved the issue) and you can also check the logs (In the mp-log > cord.log), if required.
A similar incident is discussed here.
Regards,
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!