VM Lab R82 ElasticXL - Lightshot Partition is out of space

[nadmin]

Hello, I'm rebuilding my Check Point Lab on the latest version of the XCP-ng xen hypervisor. It was great on R81.20 and ClusterXL. New challenge is R82 and ElasticXL.

First issue using ElasticXL with the second gateway not showing up as a pending gateway. Solution was to patch the exl_detectiond.py as noted in the previous thread https://community.checkpoint.com/t5/Security-Gateways/R82-elasticXL-lab/td-p/219343 (deals with open servers, looks like a bug)

Second issue is adding the second gateway fails due to failed cloning process.

/var/log/lightshot.log shows "Lightshot Partition is out of space".

Reviewing the script I ran these commands to confirm:

mount /dev/vg_splat/lv_log_lightshot /mnt/lightshot

df -h

[...]

/dev/mapper/vg_splat-lv_log_lightshot  14G  14G 124K  100% /mnt/lightshot

This confirms only 14G was on the partition even though during setup 79GB of the 128GB drive was reserved for Backup and Upgrade. I increased the drive to 300GB so that 209GB was reserved for Backup and Upgrade. Same issue, out of space, 14GB on the lightshot partition.

I understand that some people here have got ElasticXL with multiple VMs working. VMware Workstation, for example in combination with network adapter workarounds.

Q1) has anyone see this issue "Lightshot Partition is out of space" in VMs before?

Q2) if so, any suggestions on how to fix it?

Notes: I am using thick provisioning on the VM storage and there is plenty of space on the storage volume. I also built this VM from scratch, not cloning from a checkpoint-template like I do customarily. (yes i tried my template but it failed too, and i wanted to avoid using fast-clone)

If you would like to play along and see the complete build: https://github.com/doritoes/NUC-Labs/blob/xcp-ng-8.3/XCP-ng/8_Checkpoint.md

I'm willing to retry on VMware, proxymox, VirtualBox (probably not hyperv). Since this looks like a partition issue, I wanted to check here before heading that way.

Thank you!

PS: Please add a Label for ElasticXL

[ShaiF · Accepted solution]

Hi @nadmin,

The lightshot partition size should dynamically adjust based on your image size on the SMO.
Since you’re working with an unsupported hypervisor/VM (as you have a GA take installed), this mechanism might not function as expected.

To resolve this, you can manually increase the partition size from the new member’s CLISH using the following command:

set lightshot-partition size <size in GB>

Regards,
Shai.

[the_rock]

Just do exactly what @ShaiF had said. I had to do that once in eve-ng lab.