ViPR SRM Windows binary 5.x: Backend services may fail to start automatically

ViPR SRM Windows binary 5.x: Backend services may fail to start automatically


Info
Summary: Backend services may fail to start automatically due to elongated start-up times of the MySQL service. Add the mysql service as a
dependency to the APGBackendApg1 service to fix the issue.

Detailed Article

Symptoms:

The Backend (apg) service on the Primary Backend host or Backend services (apg1 - apg4) on Additional Backend hosts may not start
automatically in the following situations:
- The VM is rebooted.
- The manage-modules.cmd services start all command is issued.
- The manage-modules.cmd service restart all command is issued.

The affected services are starting when later started through the Dell Storage Resource Manager (SRM) UI or with individually tailored manage-modules.sh service commands (example: manage-modules.cmd service start backend apg1)

The cache-0-0.log of the affected backend service shows that backend service start-up failed due to the MySQL service not being ready to accept connections:

INFO -- [2025-02-04 11:52:22 EST] -- Cache::start(): Launching APG Backend v8.0.0 r282224f...
INFO -- [2025-02-04 11:52:24 EST] -- StorageConnector::initialize(): Initializing persistent storage connector 'MySqlStorageConnector'...
INFO -- [2025-02-04 11:52:24 EST] -- StorageConnector::initialize(): Configuring storage connector
'com.watch4net.apg.v2.cache.io.plugins.MySqlStorageConnector v8.0.0 r282224f' with 'conf/mysql.xml'...
INFO -- [2025-02-04 11:52:36 EST] -- StorageConnector::initialize(): Initializing storage connector 'MySqlStorageConnector'...
INFO -- [2025-02-04 11:52:36 EST] -- MySqlStorageConnector::init(): Checking database connection...
SEVERE -- [2025-02-04 11:52:38 EST] -- Cache::start(): APG Backend startup failed!
com.watch4net.apg.v2.common.io.InOutException: Error while initializing 'MySqlStorageConnector'!

Start-up delay of more than 10 s can be observed in the MySQL log at /ProgramFile/APG/Databases/MySQL/Default/data/(hostname).err.


Cause:

Recent versions of SRM incorporate updated MySQL 8.x databases. Start-up times for MySQL 8.x service may exceed a previously specified
limit of 10 s. This may lead to the backend services getting started before the MySQL service has come up fully and is ready to accept
connections.

Resolution:

The workaround was to add the mysql service as a dependency to the APGBackendApg1 service and left others as default. this appeared to
be successful. The edited APGBackendApgX service was the only one to start after a reboot.
1. login to the Backend host.
2. Open the registry editor.
3. Browse to the Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\APGBackendApg1
4. double click on the DependOnService key and add the APGMysqlDefault on its own line and save. Be careful to not change the existing
dependencies.

5. The same steps can be performed on the remaining BE's APG 2-4
6. Reboot the server and verify all services up and running: manage-modules.cmd services status all