Couple of things you could check on firewall engine side is first if there's some earlier policy push process running/stuck:
# ps auxf |grep sgcfg
If there's process running, try killing it manually.
Second thing that could help is restarting management daemon on firewall:
# msvc -d mgmtd
# msvc -u mgmtd
First command stops the daemon and second one restarts it. After restarting the daemon you can verify that status is up:
# msvc mgmtd
Then try pushing policy again.
Thank for your reply. I'll try your solution when face this error again to figure out what's the issues.
In my case, i waited for about 30' and able to normally installed policy.
If policy push succeeds after that first 30 second period, it probably just means that something on engine side was busy and it's always better to allow engine to "recover" on it's own. So if you see this happen again, wait at least that one 30 second period before using the commands from my previous message. Those were more intended for situation where you keep on seeing the "engine node is busy" message several times, i.e. then it's likely that something in engine side is stuck and restarting management daemon could be used to recover.
Today, i face this problem again and i use your solution and it works. So i come back to mark yours answer is correct!
Thanks and Regards!