topic Re: Management server failed to send phase 1 to client cord in Next-Generation Firewall Discussions

Management server failed to send phase 1 to client cord

ErrylTobes — Wed, 28 Dec 2022 02:17:00 GMT

Cannot commit due to error "Management server failed to send phase 1 to client cord". Any idea what to do with it?

Re: Management server failed to send phase 1 to client cord

laurence64 — Wed, 28 Dec 2022 12:30:39 GMT

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 ?

Re: Management server failed to send phase 1 to client cord

ErrylTobes — Mon, 02 Jan 2023 22:32:25 GMT

The error was going for a few days already. Tried to restart the management client cord and it resolved the error.

Re: Management server failed to send phase 1 to client cord

laurence64 — Wed, 04 Jan 2023 00:30:58 GMT

Do you mean you restarted the mgmt server process ?

Re: Management server failed to send phase 1 to client cord

ErrylTobes — Wed, 04 Jan 2023 01:42:22 GMT

i don't think it was the whole mgmt server process. i used this command "debug software restart process cord"

Re: Management server failed to send phase 1 to client cord

laurence64 — Wed, 04 Jan 2023 09:26:42 GMT

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.

Re: Management server failed to send phase 1 to client cord

Arnesh — Wed, 04 Jan 2023 10:42:13 GMT

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,