sk121447 - How to perform an automated health check of a Gaia based system (results you don't really understand)

[Jerry]

aloha,

quick few I guess, wonder what you think folks,:

1. see enclosed. did 1 HC, resulted CPUSE build number warrning, you know why? coz I don't. Here is the fact what build number I run:

SMS1> show installer status
Agent:              enabled
Build number:       1439 (agent build is up to date)
Network connection:  Could not connect to the Check Point Cloud. Check your connection settings (Default Gateway,  DNS  and  Proxy )
Update from cloud:  last updated on Thu Aug  2 15:15:57 2018
License:            valid

*** am I really outdated? I believe the error in HC is due to the indirect-communication with CPUSE meaning that SMS's (MGMT HA) has no direct internet access to CPUSE? am I correct that this .sh checkes what this command does:

curl_cli -v -k https://updates.checkpoint.com/

2.  Result of Free Disk Space (I guess that 98% of use seem to me like a reason ...)  

[Expert@SMS1:0]# df -ahl
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_splat-lv_current
                       31G  9.8G   20G  34% /
proc                     0     0     0   -  /proc
sysfs                    0     0     0   -  /sys
devpts                   0     0     0   -  /dev/pts
/dev/sda1             289M   24M  251M   9% /boot
tmpfs                 4.9G  4.0K  4.9G   1% /dev/shm
/dev/mapper/vg_splat-lv_log
                      238G  220G  5.6G  98% /var/log
none                     0     0     0   -  /proc/sys/fs/binfmt_misc

***

have you tried yourself the output from that HC that you got shocked vs. surprised and what was it? anything unusual folks?

Cheers

Jerry

[Jerry]

found my bug ...

An updated version of CPUSE is available in sk92449 (as of 07-13-2018).
Local Build:  1439
Latest Build: 1511

[Nathan_Davieau]

I hardcode the latest CPUSE build using what is currently available in sk92449 since not all devices will have access to the internet to check.

The disk space on /var/log/ is at 98% which is over both thresholds that I have configured.

When a partition gets over 70%, the script will show "INFO" instead of "OK".

When a partition gets over 90%, the script will show "WARNING".