Автор: admin

Процесс kworker нагружает процессор

9 июня, 2020 от admin·Нет комментариев

Для отключения уведомлений смотреть

$ sudo grep bled /sys/firmware/acpi/interrupts/gpe*
/sys/firmware/acpi/interrupts/gpe01:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe02:       0  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe06:       5  EN     enabled      unmasked
/sys/firmware/acpi/interrupts/gpe07:       0         enabled      unmasked
/sys/firmware/acpi/interrupts/gpe09:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe0D:       0         disabled     unmasked
/sys/firmware/acpi/interrupts/gpe13:154054570  EN STS enabled      unmasked
/sys/firmware/acpi/interrupts/gpe19:     220  EN     enabled      unmasked

$ sudo grep bled /sys/firmware/acpi/interrupts/gpe*

/sys/firmware/acpi/interrupts/gpe01: 0 EN enabled unmasked

/sys/firmware/acpi/interrupts/gpe02: 0 EN enabled unmasked

/sys/firmware/acpi/interrupts/gpe06: 5 EN enabled unmasked

/sys/firmware/acpi/interrupts/gpe07: 0 enabled unmasked

/sys/firmware/acpi/interrupts/gpe09: 0 disabled unmasked

/sys/firmware/acpi/interrupts/gpe0D: 0 disabled unmasked

/sys/firmware/acpi/interrupts/gpe13:154054570 EN STS enabled unmasked

/sys/firmware/acpi/interrupts/gpe19: 220 EN enabled unmasked

Отключить gpe13

echo "disable" | sudo tee /sys/firmware/acpi/interrupts/gpe13

1	echo "disable" \| sudo tee /sys/firmware/acpi/interrupts/gpe13

NTFS-раздел монтируется только на чтение

21 декабря, 2019 от admin·Нет комментариев

В графической утилите не видно, что диск не может смонтироваться для записи из-за ошибки. Зато в консоли сразу видна причина:

$ sudo mount /mnt/mydisk
The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Falling back to read-only mount because the NTFS partition is in an
unsafe state. Please resume and shutdown Windows fully (no hibernation
or fast restarting.)

$ sudo mount /mnt/mydisk

The disk contains an unclean file system (0, 0).

Metadata kept in Windows cache, refused to mount.

Falling back to read-only mount because the NTFS partition is in an

unsafe state. Please resume and shutdown Windows fully (no hibernation

or fast restarting.)

Лечиться это просто запуском утилиты:

sudo ntfsfix /dev/sdb5

1	sudo ntfsfix /dev/sdb5

Права к файлам в Linux

28 ноября, 2019 от admin·Нет комментариев

Проверить есть ли у пользователя права на чтение файла:

sudo -u nginx test -r /var/www/site1/index.php || echo "No permission to the file"

1	sudo -u nginx test -r /var/www/site1/index.php \|\| echo "No permission to the file"

На чтение каталога:

sudo -u nginx test -x /var/www/site1 || echo "No permission to the directory"

1	sudo -u nginx test -x /var/www/site1 \|\| echo "No permission to the directory"

Настройка соединения с Bluetooth-гарнитурой

7 февраля, 2019 от admin·Нет комментариев

Список доступных команд для управления bluetooth

bluetoothctl help

1	bluetoothctl help

Подключение нового устройства

$ bluetoothctl
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:10:20:30:40:50 Discovering: yes
...
[NEW] Device 10:20:30:40:50:60 My device
...
[bluetooth]# pair 10:20:30:40:50:60
Attempting to pair with 10:20:30:40:50:60
[CHG] Device 10:20:30:40:50:60 Connected: yes
[CHG] Device 10:20:30:40:50:60 UUIDs: 00002233-0000-0000-0000-0000549e3568
...
[CHG] Device 10:20:30:40:50:60 ServicesResolved: yes
[CHG] Device 10:20:30:40:50:60 Paired: yes
Pairing successful
[CHG] Device 10:20:30:40:50:60 ServicesResolved: no
[CHG] Device 10:20:30:40:50:60 Connected: no
...
[bluetooth]# connect 10:20:30:40:50:60
Attempting to connect to 10:20:30:40:50:60
[CHG] Device 10:20:30:40:50:60 Connected: yes
Connection successful
[CHG] Device 10:20:30:40:50:60 ServicesResolved: yes
...

$ bluetoothctl

[bluetooth]# scan on

Discovery started

[CHG] Controller 00:10:20:30:40:50 Discovering: yes

...

[NEW] Device 10:20:30:40:50:60 My device

...

[bluetooth]# pair 10:20:30:40:50:60

Attempting to pair with 10:20:30:40:50:60

[CHG] Device 10:20:30:40:50:60 Connected: yes

[CHG] Device 10:20:30:40:50:60 UUIDs: 00002233-0000-0000-0000-0000549e3568

...

[CHG] Device 10:20:30:40:50:60 ServicesResolved: yes

[CHG] Device 10:20:30:40:50:60 Paired: yes

Pairing successful

[CHG] Device 10:20:30:40:50:60 ServicesResolved: no

[CHG] Device 10:20:30:40:50:60 Connected: no

...

[bluetooth]# connect 10:20:30:40:50:60

Attempting to connect to 10:20:30:40:50:60

[CHG] Device 10:20:30:40:50:60 Connected: yes

Connection successful

[CHG] Device 10:20:30:40:50:60 ServicesResolved: yes

...

Список устройств

$ bluetoothctl devices
Device 10:20:30:40:50:61 HP-345
Device 10:20:30:40:50:62 Redmi
Device 10:20:30:40:50:60 My device

$ bluetoothctl devices

Device 10:20:30:40:50:61 HP-345

Device 10:20:30:40:50:62 Redmi

Device 10:20:30:40:50:60 My device

Подключиться к устройству

$ bluetoothctl connect 10:20:30:40:50:60

1	$ bluetoothctl connect 10:20:30:40:50:60

Отключиться

$ bluetoothctl disconnect 10:20:30:40:50:60

1	$ bluetoothctl disconnect 10:20:30:40:50:60

Защищено: Литература по моделированию

17 декабря, 2018 от admin·Введите пароль для просмотра комментариев.

Ротация логов — logrotate

12 октября, 2018 от admin·Нет комментариев

Для ротации логов достаточно добавить конфигурационный файл в каталог /etc/logrotate.d. Например, /etc/logrotate.d/mylittleservice

/custom/log/path/mylittleservice.log {
    daily
    rotate 7
    dateext
    missingok
    notifempty
    delaycompress
    create 0664 little little
    su root apache
}

/custom/log/path/mylittleservice.log {

daily

rotate 7

dateext

missingok

notifempty

delaycompress

create 0664 little little

su root apache

}

daily — ежедневный
rotate 7 — глубина 7 (7 дней)
dateext — в расширении будет дата, а не цифра
missingok
notifempty
delaycompress
create 0664 little little — создать с правами для пользователя little и группы little
su root little — если в папке права не только для root

Помощники в изучении English

25 сентября, 2018 от admin·Нет комментариев

https://www.grammarly.com/ — проверка орфографии и грамматики
https://howjsay.com/ — произношение от носителей языка
https://forvo.com/ — произношение в разных странах

Работа composer за прокси-сервером

10 сентября, 2018 от admin·Нет комментариев

После установки прокси-сервера перестал работать composer:

$ composer diagnose
Checking composer.json: WARNING
No license specified, it is recommended to do so. For closed-source software you may use "proprietary" as license.
Checking platform settings: OK
Checking git settings: OK
Checking http connectivity to packagist: OK
Checking https connectivity to packagist: WARNING
[Composer\Downloader\TransportException] The "https://packagist.org/packages.json" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages:
error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
Failed to enable crypto
failed to open stream: operation failed
Checking HTTP proxy: FAIL
[Composer\Downloader\TransportException] The "https://packagist.org/packages.json" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages:
error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
Failed to enable crypto
failed to open stream: operation failed
Checking HTTP proxy support for request_fulluri: OK
Checking HTTPS proxy support for request_fulluri: WARNING
Unable to assess the situation, maybe github is down (The "https://api.github.com/repos/Seldaek/jsonlint/zipball/1.0.0" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages:
error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
Failed to enable crypto
failed to open stream: operation failed)
Checking github.com rate limit: FAIL
[Composer\Downloader\TransportException] The "https://api.github.com/rate_limit" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages:
error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
Failed to enable crypto
failed to open stream: operation failed
Checking disk free space: OK

$ composer diagnose

Checking composer.json: WARNING

No license specified, it is recommended to do so. For closed-source software you may use "proprietary" as license.

Checking platform settings: OK

Checking git settings: OK

Checking http connectivity to packagist: OK

Checking https connectivity to packagist: WARNING

[Composer\Downloader\TransportException] The "https://packagist.org/packages.json" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages:

error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

Failed to enable crypto

failed to open stream: operation failed

Checking HTTP proxy: FAIL

[Composer\Downloader\TransportException] The "https://packagist.org/packages.json" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages:

error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

Failed to enable crypto

failed to open stream: operation failed

Checking HTTP proxy support for request_fulluri: OK

Checking HTTPS proxy support for request_fulluri: WARNING

Unable to assess the situation, maybe github is down (The "https://api.github.com/repos/Seldaek/jsonlint/zipball/1.0.0" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages:

error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

Failed to enable crypto

failed to open stream: operation failed)

Checking github.com rate limit: FAIL

[Composer\Downloader\TransportException] The "https://api.github.com/rate_limit" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages:

error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

Failed to enable crypto

failed to open stream: operation failed

Checking disk free space: OK

Решение: /etc/profile добавить строки:

export https_proxy=http://proxy:3128/
export http_proxy=http://proxy:3128/
export ftp_proxy=ftp://proxy:3128/

export https_proxy=http://proxy:3128/

export http_proxy=http://proxy:3128/

export ftp_proxy=ftp://proxy:3128/

Сломался composer

28 августа, 2018 от admin·Нет комментариев

$ composer
PHP Fatal error:  Uncaught Error: Call to undefined function Composer\Json\json_decode() in /usr/share/php/Composer/Json/JsonFile.php:270
Stack trace:
#0 /usr/share/php/Composer/Json/JsonFile.php(101): Composer\Json\JsonFile::parseJson('{\n    "github-o...', '/home/vvs/.conf...')
#1 /usr/share/php/Composer/Factory.php(199): Composer\Json\JsonFile->read()
#2 /usr/share/php/Composer/Factory.php(420): Composer\Factory::createConfig(Object(Composer\IO\ConsoleIO))
#3 /usr/share/php/Composer/Console/Application.php(453): Composer\Factory::createGlobal(Object(Composer\IO\ConsoleIO), false)
#4 /usr/share/php/Composer/Console/Application.php(149): Composer\Console\Application->getPluginCommands()
#5 /usr/share/php/Symfony/Component/Console/Application.php(127): Composer\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#6 /usr/share/php/Composer/Console/Application.php(100): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Inp in /usr/share/php/Composer/Json/JsonFile.php on line 270

Fatal error: Uncaught Error: Call to undefined function Composer\Json\json_decode() in /usr/share/php/Composer/Json/JsonFile.php:270
Stack trace:
#0 /usr/share/php/Composer/Json/JsonFile.php(101): Composer\Json\JsonFile::parseJson('{\n    "github-o...', '/home/vvs/.conf...')
#1 /usr/share/php/Composer/Factory.php(199): Composer\Json\JsonFile->read()
#2 /usr/share/php/Composer/Factory.php(420): Composer\Factory::createConfig(Object(Composer\IO\ConsoleIO))
#3 /usr/share/php/Composer/Console/Application.php(453): Composer\Factory::createGlobal(Object(Composer\IO\ConsoleIO), false)
#4 /usr/share/php/Composer/Console/Application.php(149): Composer\Console\Application->getPluginCommands()
#5 /usr/share/php/Symfony/Component/Console/Application.php(127): Composer\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#6 /usr/share/php/Composer/Console/Application.php(100): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Inp in /usr/share/php/Composer/Json/JsonFile.php on line 270

$ composer

PHP Fatal error: Uncaught Error: Call to undefined function Composer\Json\json_decode() in /usr/share/php/Composer/Json/JsonFile.php:270

Stack trace:

#0 /usr/share/php/Composer/Json/JsonFile.php(101): Composer\Json\JsonFile::parseJson('{\n "github-o...', '/home/vvs/.conf...')

#1 /usr/share/php/Composer/Factory.php(199): Composer\Json\JsonFile->read()

#2 /usr/share/php/Composer/Factory.php(420): Composer\Factory::createConfig(Object(Composer\IO\ConsoleIO))

#3 /usr/share/php/Composer/Console/Application.php(453): Composer\Factory::createGlobal(Object(Composer\IO\ConsoleIO), false)

#4 /usr/share/php/Composer/Console/Application.php(149): Composer\Console\Application->getPluginCommands()

#5 /usr/share/php/Symfony/Component/Console/Application.php(127): Composer\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))

#6 /usr/share/php/Composer/Console/Application.php(100): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Inp in /usr/share/php/Composer/Json/JsonFile.php on line 270

Fatal error: Uncaught Error: Call to undefined function Composer\Json\json_decode() in /usr/share/php/Composer/Json/JsonFile.php:270

Stack trace:

#0 /usr/share/php/Composer/Json/JsonFile.php(101): Composer\Json\JsonFile::parseJson('{\n "github-o...', '/home/vvs/.conf...')

#1 /usr/share/php/Composer/Factory.php(199): Composer\Json\JsonFile->read()

#2 /usr/share/php/Composer/Factory.php(420): Composer\Factory::createConfig(Object(Composer\IO\ConsoleIO))

#3 /usr/share/php/Composer/Console/Application.php(453): Composer\Factory::createGlobal(Object(Composer\IO\ConsoleIO), false)

#4 /usr/share/php/Composer/Console/Application.php(149): Composer\Console\Application->getPluginCommands()

#6 /usr/share/php/Composer/Console/Application.php(100): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Inp in /usr/share/php/Composer/Json/JsonFile.php on line 270

PHP-CLI запускается несколько раз (дважды). Второй раз не считываются конфигурационные файлы из /etc/php.d.

Запускается дважды из-за того, что Composer обнаруживает подключенное расширение xdebug. Он копирует /etc/php.ini во временную папку /tmp и запускает себя повторно. Но повторно уже не считывает дополнительные конфигурационные файлы.

Как одно из решений не отключать xdebug. В этом случае composer хоть и работает медленней, но работает:

$ export COMPOSER_ALLOW_XDEBUG=1 && composer

1	$ export COMPOSER_ALLOW_XDEBUG=1 && composer

Восстановление urlrewrite.php в Битриксе

1 августа, 2018 от admin·Нет комментариев

Жизнь непредсказуема порой. Файл urlrewrite.php рекомендуют исключать из версионного контроля. Но его можно легко потерять. Например, попытаться установить какой-нибудь «мегамодуль».

Поэтому нужно знать как восстанавливать urlrewrite.php. В административной панели Настройки продукта — Обработка адресов — Правила обработки — Пересоздание.

Похоже, что эта команда проходит по всем компонентам в публичке, у которых установлен параметр SEF_FOLDER, и добавляет соответствующие записи в urlrewrite.php.

ВВСки

Записки разработчика

Автор: admin

Процесс kworker нагружает процессор

NTFS-раздел монтируется только на чтение

Права к файлам в Linux

Настройка соединения с Bluetooth-гарнитурой

Защищено: Литература по моделированию

Ротация логов — logrotate

Помощники в изучении English

Работа composer за прокси-сервером

Сломался composer

Восстановление urlrewrite.php в Битриксе