Is it possible to change the temp directory cpinfo uses for generation?

[elbergfeldt]

Ran into a weird issue when generating a cpinfo file yesterday, it was failing due to limited amount of space in "/" root directory, although we were trying to generate it and store the output in /var/log/.

I'm assuming but couldn't find anything in the documentation that during the cpinfo file generation /tmp folder is used in the root directory and only the output gets stored in the specified output folder.

I was able to sort out the issue by clearing out some files in root, but was curious for future reference if it is possible to change the temp directory cpinfo uses for it's generation? 

[PhoneBoy]

The output file (with full path) can be specified with the -o option to cpinfo.

[Lesley]

Example: cpinfo -d -D -z -o /var/log/<NAME>.cpinfo

[elbergfeldt]

Yeah, the problem is we did use the -o flag to place the cpinfo in /var/log/, yet got the error message that 
"partitionPath / is critically low"  

[PhoneBoy]

That doesn't mean the root filesystem isn't used for some operations necessary to gather the output.
TAC might be able to suggest something here as I can't imagine you're the first person to encounter this issue.

[G_W_Albrecht]

As sk92739 says: The output file will be created in the current working directory

To which directory did you change before calling cpinfo ? Here the collection process starts.

[elbergfeldt]

We tried it many ways, using -o flag from /home/ directory, changing to /var/log/ and still using -o flag, and just without any flags at all in /var/log/ - they all generated the same error 

[Elad_Chomsky · Accepted solution]

Hi @elbergfeldt ,

CPinfo for his operation as mentioned @PhoneBoy , is running specific commands to collect information from the machine, some function on the root FS. Unfortunately due to that as a limitation we must make sure to not fill the root partition as well, Please open a ticket to CheckPoint, and we will try to see if we can provide you a workaround to still do the collection. 

[the_rock]

What I always do is this. If say /var/log has lots of space left, I do below:

cpinfo -o /var/log/cpinfofile.out

Thats it.

Andy

[dehaasm]

i am trying that but still doesnt generate cpinfo 

[Expert@sms:0]# df -h
Filesystem                       Size  Used Avail Use% Mounted on
/dev/mapper/vg_splat-lv_current   40G   36G  4.3G  90% /
/dev/sda1                        290M   45M  231M  17% /boot
tmpfs                             32G   39M   32G   1% /dev/shm
/dev/mapper/vg_splat-lv_log      1.8T  1.5T  299G  84% /var/log
cgroup                            32G     0   32G   0% /sys/fs/cgroup

[Expert@sms:0]# cpinfo -o /var/log/sms.cpinfo

This is Check Point CPinfo Build 914000259 for GAIA
Would you like to upload CPinfo file securely to Check Point Download Center? y/n: [y]n
WARNING: Disk space on partitionPath '/' is critically low.
Currently free disk space: 10.40%.
Please free up some space and re-run CPinfo.

exiting...

[the_rock]

I find that very odd. Makes no sense it would complain about disk space in root dir when you are clearly sending it to /var/log.

Andy

[elbergfeldt]

I think like Elad_Chomsky wrote the cpinfo will run specific commands in root to collect info from the machine, due to that there needs to be space available in root as well 

[G_W_Albrecht]

cpinfo collects all needed files in / and then compresses it, saving it to the given path and then uploading it if needed...