Last Modified: Nov 23, 2020
See more info
Known Affected Versions:
14.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 14.1.2, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 15.0.0, 15.0.1, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 15.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 15.1.1, 15.1.2, 16.0.0, 22.214.171.124, 16.0.1
Opened: Mar 07, 2019
When saving the configuration to a UCS file, the process tries save the IPS learning information stored in the MySQL database. MySQL runs only when particular modules are provisioned. If MySQL was previously running as a result of different provisioning, but is not currently running, saving the configuration to a UCS file succeeds, but the system reports a spurious message during the operation: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock.
The error message is cosmetic and has no impact on the UCS save process.
-- Saving the configuration to a UCS file. -- BIG-IP system provisioning only includes modules that do not require MySQL. These modules may include: + LTM + FPS + GTM (DNS) + LC + SWG + iLX + SSLo -- BIG-IP system was previously provisioned with a module that starts MySQL, which results in the creation of the file /var/db/mysqlpw. These modules may include: + APM + ASM + AVR + PEM + AFM + vCMP