cpinfo ... will stop the machine

[S_E_]

Hi,

can't remember that we saw that earlier:

What does the statement with shut down machine exactly mean? Did not see that any service goes down.

MDS R80.40 ; HF T91

Regards,

[Expert@MDS:0]# cpinfo -z -d -D -o /var/tmp/MDS_cpinfo.tgz

This is Check Point CPinfo Build 914000202 for GAIA

CPinfo Creation...

Collecting information...: 100%
Starting MDS export.
This process can take a few minutes or hours (depending on size of export) and will stop the machine.

[_Val_]

On management servers, CPINFO creates a migrate export file. To make sure DB is consistent, cpstop/mdsstop is required. This ensures no DB transactions are in progress when export file is being created.

[S_E_]

Hi,

If I understand correctly:

mdsstop -> admins will be dropped > unsaved sessions might exist

mdsstop -> downtime for admins = => maintenance window

That is not good. This is usually the first thing TAC asked for. 

Thanks

Regards

[_Val_]

you are correct, it is reasonable to run cpinfo during a service window.

[the_rock]

Hm...I never seen that before on mds, mind you, I had not played around on Provider-1 since R77.30, so it could be different in R80 version. But, on gateway or regular mgmt server, cpinfo would never require you to do cpstop, Im 100% positive of that.

[Tal_Paz-Fridman]

As _Val_ wrote this happens because of the Migrate Export.

If you run the same command with -x it will not create a migrate export file and will not need to stop the Check Point products:

-x Don't create migrate export or MDS export, for Management or Multi-Domain Management, R80 version or above only

I think it would be helpful to give the user the notification and an option to quit the action before starting (I'll take it up with relevant owner)

[the_rock]

I agree 100%...it would be very helpful if warning came up, for sure.

Andy

[Arik_Ovtracht]

Hi, owner here 🙂

We can add this to the next version of cpinfo.

[Arik_Ovtracht · Accepted solution]

Hi,

After checking, it appears that cpinfo doesn't actually stop the processes - the message is wrong.

The next version of cpinfo will have a fixed message.