Describe the bug

The DB requirements are checked against the local database only, but the Remote Poller also requires access to "mysql.time_zone_name" table but this isn't checked during Remote Poller installation. It happens because the DB check stage happens before the Remote Poller configuration OR the Cacti itself should be updated to use only the local DB 'mysql.time_zone_name' table instead of relying on the DB remote one.

To Reproduce

Steps to reproduce the behavior:

1. Go to Cacti Web Installer.

2. Click on 'Next', check the DB requirements.

3. See error if upgrading an existing Remote Poller instance without "mysql.time_zone_name" 'SELECT' access or the local one should be used instead or Cacti should always use the local "mysql.time_zone_name" table instead of relying on the remote (Main Poller) one.

Expected behavior

The "mysql.time_zone_name" 'SELECT' access should be checked on a later stage during Remote Poller first install.

Screenshots

None.

Desktop (please complete the following information)

• OS: Windows Server 2012

• Browser Chrome

• Version 109

Additional context

None.