Владимир (Все сообщения пользователя)

# INFO: Using main config file /home/bitrix/dehydrated/config
Processing *ДОМЕН*
 + Checking domain name(s) of existing cert... unchanged.
 + Checking expire date of existing cert...
 + Valid till Nov 22 07:39:42 2025 GMT (Longer than 20 days). Skipping renew!

use Bitrix\Main\Mail\Event;
$arFields = array(
    "EVENT_NAME" => "EPIR_SEND_FORM_7",
    "LID" => "s1",
    "C_FIELDS" => array(
    "EMAIL"    => "почта админа",
    "BCC"    => "почта админа",
    "DEFAULT_EMAIL_FROM"    => "почта админа"
    ),
    "DUPLICATE"=>"Y",
);
$result=Event::send($arFields);
if($result->GetId()){
    echo 'Успешно отправлено!';
}else{
    echo 'Отправка не удалась!';
}

Loaded plugins: etckeeper, fastestmirror, versionlock
No old kernels to remove
Loaded plugins: etckeeper, fastestmirror, merge-conf, versionlock
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=genclo error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64

iptables -A INPUT -s xxx.xxx.xxx.xxx -j DROP

service iptables save