After a config restore we were unable to save IPSO changes
in either voyager or CLI. We were also not able to install any packages.
The symptoms we saw were;
-
In voyager we would be logged out if the “save”
button is pressed.
-
From the CLI if we “save config” the following
error would be displayed.
NMSSYS0026
libdb_do_transaction: connection closed during operation
- Packages will not install from voyager with a db
xpand process error.
-
Or packages will not install with a “Installation
Aborted…” error
Can not find your
/opt/CPshared/5.0/tmp/.CPprofile.sh file
Installation Aborted...
Installation Aborted...
The issue here is documented in a hidden SK (sk59440) and following the
solution has resolved both issues;
After seemingly successful restore from the backup, the following error appears while trying to save configuration in Voyager, clish or through dbset. Configuration can still be applied."libdb_do_transaction: connection closed during operation" attempt to save configuration results in xpand process crash.
SOLUTION
Check point say the solution is;
“Changing the configuration database (copying intial file) in Voyager -> Configuration -> Configuration Sets -> Select a database for next reboot clears the issue e.g. xpand process stops coring and configuration can be saved.”
We found it was better to save the current “locked” config to a new “configuration set” name. For good measure we rebooted after.
After seemingly successful restore from the backup, the following error appears while trying to save configuration in Voyager, clish or through dbset. Configuration can still be applied."libdb_do_transaction: connection closed during operation" attempt to save configuration results in xpand process crash.
SOLUTION
Check point say the solution is;
“Changing the configuration database (copying intial file) in Voyager -> Configuration -> Configuration Sets -> Select a database for next reboot clears the issue e.g. xpand process stops coring and configuration can be saved.”
We found it was better to save the current “locked” config to a new “configuration set” name. For good measure we rebooted after.
No comments:
Post a Comment