Translation

English
For remote pollers, it is critical that the paths that you will be updating frequently, including the plugins, scripts, and resources paths have read/write access as the data collector will have to update these paths from the main web server content.
0/2500 · 250
English Ukrainian
Your Remote Cacti Poller information has not been included in your config.php file. Please review the config.php.dist, and set the variables: <i>$rdatabase_default, $rdatabase_username</i>, etc. These variables must be set and point back to your Primary Cacti database server. Correct this and try again.
Remote Poller Variables
The variables that must be set in the config.php file include the following:
The Installer automatically assigns a $poller_id and adds it to the config.php file.
Once the variables are all set in the config.php file, you must also grant the $rdatabase_username access to the main Cacti database server. Follow the same procedure you would with any other Cacti install. You may then press the 'Test Connection' button. If the test is successful you will be able to proceed and complete the install.
Additional Steps After Installation
It is essential that the Central Cacti server can communicate via MySQL to each remote Cacti database server. Once the install is complete, you must edit the Remote Data Collector and ensure the settings are correct. You can verify using the 'Test Connection' when editing the Remote Data Collector.
Critical Binary Locations and Versions
Make sure all of these values are correct before continuing.
One or more paths appear to be incorrect, unable to proceed
Directory Permission Checks
Please ensure the directory permissions below are correct before proceeding. During the install, these directories need to be owned by the Web Server user. These permission changes are required to allow the Installer to install Device Template packages which include XML and script files that will be placed in these directories. If you choose not to install the packages, there is an 'install_package.php' cli script that can be used from the command line after the install is complete.
After the install is complete, you can make some of these directories read only to increase security.
These directories will be required to stay read writable after the install so that the Cacti remote synchronization process can update them as the Main Cacti Web Site changes
If you are installing packages, once the packages are installed, you should change the scripts directory back to read only as this presents some exposure to the web site.
For remote pollers, it is critical that the paths that you will be updating frequently, including the plugins, scripts, and resources paths have read/write access as the data collector will have to update these paths from the main web server content.
Required Writable at Install Time Only
Not Writable
Required Writable after Install Complete
Potential permission issues
Please make sure that your webserver has read/write access to the cacti folders that show errors below.
If SELinux is enabled on your server, you can either permanently disable this, or temporarily disable it and then add the appropriate permissions using the SELinux command-line tools.
The user '%s' should have MODIFY permission to enable read/write.
An example of how to set folder permissions is shown here, though you may need to adjust this depending on your operating system, user accounts and desired permissions.
EXAMPLE:
Once installation has completed the CSRF path, should be set to read-only.
All folders are writable
Input Validation Whitelist Protection
Cacti Data Input methods that call a script can be exploited in ways that a non-administrator can perform damage to either files owned by the poller account, and in cases where someone runs the Cacti poller as root, can compromise the operating system allowing attackers to exploit your infrastructure.
Therefore, several versions ago, Cacti was enhanced to provide Whitelist capabilities on the these types of Data Input Methods. Though this does secure Cacti more thoroughly, it does increase the amount of work required by the Cacti administrator to import and manage Templates and Packages.
The way that the Whitelisting works is that when you first import a Data Input Method, or you re-import a Data Input Method, and the script and or arguments change in any way, the Data Input Method, and all the corresponding Data Sources will be immediatly disabled until the administrator validates that the Data Input Method is valid.
Component Translation Difference to current string
This translation Propagated Empty Cacti/core (v1.2.x)
The following string has the same context and source.
Propagated Translated Cacti/core Для віддалених опитувальників дуже важливо, щоб шляхи, які ви будете часто оновлювати, включаючи плагіни, сценарії та шляхи ресурсів, мали доступ для читання/запису, оскільки збирач даних повинен буде оновлювати ці шляхи з вмісту основного веб-сервера.

Loading…

No matching activity found.

Browse all component changes

Glossary

English Ukrainian
No related strings found in the glossary.

String information

Source string location
lib/installer.php:2312
String age
a year ago
Source string age
3 years ago
Translation file
locales/po/uk-UA.po, string 3480