Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:dpi:dpi_options:opt_filtration:revmon_script:start [2020/02/05 17:29] – ↷ Page moved from en:dpi:dpi_options:base_functionality:opt_filtration:revmon_script:start to en:dpi:dpi_options:opt_filtration:revmon_script:start lexx26 | en:dpi:dpi_options:opt_filtration:revmon_script:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== 12 Script for monitoring reports of the Revisor blocked sites control system ====== | ||
| - | {{indexmenu_n> | ||
| - | Roskomnadzor does not provide an official API for auditing the Revisor (blocking sites control system checking that | ||
| - | the access to blacklisted sites is denied) reports, and operator access to such reports is | ||
| - | protected by captcha. For the convenience of reports monitoring, we suggest using this script: | ||
| - | |||
| - | Installation instructions: | ||
| - | |||
| - | 1. Download and dearchive the [[http:// | ||
| - | < | ||
| - | cd / | ||
| - | wget http:// | ||
| - | tar xvzf revmon.tgz | ||
| - | </ | ||
| - | 2. Install the mail client mutt. This command is applicable for CentOS, the way of installation in other operating systems will differ | ||
| - | < | ||
| - | yum install mutt | ||
| - | </ | ||
| - | 3. Specify the e-mail for sending reports | ||
| - | < | ||
| - | in the CONF/ | ||
| - | vasya@example.org | ||
| - | </ | ||
| - | 4. Specify the session cookie to load the reports using a script without reauthorizing | ||
| - | < | ||
| - | in the CONF/ | ||
| - | PHPSESSID=u53r9cn7d9f4hl9ro2odul51k3 | ||
| - | </ | ||
| - | Here's one way to get the value of a session cookie using the Chrome browser: | ||
| - | < | ||
| - | Go to the Revisor portal https:// | ||
| - | Log in typing in the captcha | ||
| - | Select " | ||
| - | Go to the "My Reports" | ||
| - | Select the " | ||
| - | Copy the value of this cookie and put it into CONF/ | ||
| - | Also, you can copy the cookies from the " | ||
| - | </ | ||
| - | 5. Configure cron to run the script every 5 minutes. Its is responsible for maintaining the session activity so that it does not expire and for loading reports once they are created | ||
| - | < | ||
| - | */5 * * * * / | ||
| - | </ | ||
| - | 6. Configure the cron in order to request the Revisor reports at the time you specify | ||
| - | < | ||
| - | 50 07,23 * * * / | ||
| - | </ | ||
| - | 7. Configure the reports cleaning being stored for more than a month in order to avoid disk overflow | ||
| - | < | ||
| - | 15 4 * * * /bin/find / | ||
| - | </ | ||
| - | |||
| - | Downloaded reports are stored in the ARCHIVE directory\\ | ||
| - | Application log is kept in the exec.log file\\ | ||
| - | Types of messages: | ||
| - | PING OK 31.05.2018 18:50 - request for a session\\ | ||
| - | REQUEST REPORT 31.05.2018 15:32 - request for the report\\ | ||
| - | SEND REPORT 793546 31.05.2018 18:45 - report is sent\\ | ||
| - | SESSION EXPIRED - the session expired, you need to update the session cookie, as specified in item 4 | ||