Patching service default level in INFO. At this level, not enough information available to figure you why the patch update status reports as ERROR
Gateway 11.x
How to enable FINE logging
STEPS:
Stop PMS service:
# service pms stop
Modify /opt/SecureSpan/PatchManagement/etc/conf/pms_logging.properties
Before:
.
# Set the default logging level for new FileHandler instances
java.util.logging.FileHandler.level = CONFIG
.
# Set the default logging level for the root logger
.level = INFO
# Set the default logging level for the PMS output
com.broadcom.debian.patch.level = CONFIG
After:
# Specify the handlers to create in the root logger
handlers = java.util.logging.FileHandler
# Set the default logging level for new FileHandler instances
java.util.logging.FileHandler.level = FINE
java.util.logging.FileHandler.pattern = /opt/SecureSpan/PatchManagement/var/logs/patch_cli_%g_%u.log
java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter
java.util.logging.FileHandler.formatter.format = %1$tY-%1$tm-%1$tdT%1$tH:%1$tM:%1$tS.%1$tL%1$tz %2$-7s %5$d %3$s: %4$s%n
java.util.logging.FileHandler.limit = 1000000
java.util.logging.FileHandler.append = true
java.util.logging.FileHandler.count = 5
# Set the default logging level for the root logger
.level = FINE
# Set the default logging level for the Patch client output
com.broadcom.debian.patch.level = FINE
START pms service
# service pms start
Check the version of PMS
# dpkg -l | grep patch-management
ii patch-management 2.0.0-20250318021540 all patch-management
PMS service for the Appliance Gateway, we can start, stop, and view status of the Patch Management Service using:
# service pms start
# service pms stop
# service pms status