Сервис brainy-socket.service отключен.

[netserg]

При создании хост аккаунта получаю сообщение Сервис brainy-socket.service отключен. подскажите отчего? 5 минут назад все работало!) ничего не менял просто добавлял аккаунты и домены

[alenka]

systemctl status brainyphp-fpm
free -h
df -h
systemctl restart brainyphp-fpm

[netserg]

Спасибо перезагрузил - помогло

[netserg]

Снова получил
Сервис brainy-socket.service отключен
root@s2:~# systemctl status brainyphp-fpm
● brainyphp-fpm.service - The Brainy-FPM PHP Process Manager
Loaded: loaded (/lib/systemd/system/brainyphp-fpm.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2023-07-20 11:56:43 MSK; 5 days ago
Main PID: 1027 (php-fpm)
Status: "Processes active: 0, idle: 4, Requests: 3783, slow: 0, Traffic: 0req/sec"
Tasks: 5 (limit: 9414)
Memory: 89.3M
CPU: 37min 22.076s
CGroup: /system.slice/brainyphp-fpm.service
├─ 1027 php-fpm: master process (/usr/local/brainycp/src/compiled/php5/php-fpm.conf)
├─ 1435 php-fpm: pool brainyservice.conf
├─ 1436 php-fpm: pool brainyservice.conf
├─3129616 php-fpm: pool brainy.conf
└─3130362 php-fpm: pool brainy.conf

Jul 26 06:44:23 s2.host.ru sudo[3140847]: pam_unix(sudo:session): session closed for user root
Jul 26 06:44:23 s2.host.ru sudo[3140850]: root : TTY=unknown ; PWD=/usr/local/brainycp ; USER=root ; COMMAND=/usr/bin/stat -c %U /home/nets/var
Jul 26 06:44:23 s2.host.ru sudo[3140850]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 26 06:44:23 s2.host.ru sudo[3140850]: pam_unix(sudo:session): session closed for user root
Jul 26 06:44:23 s2.host.ru sudo[3140853]: root : TTY=unknown ; PWD=/usr/local/brainycp ; USER=root ; COMMAND=/usr/bin/stat -c %U /home/nets/lib64
Jul 26 06:44:23 s2.ost.ru sudo[3140853]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 26 06:44:23 s2.host.ru sudo[3140853]: pam_unix(sudo:session): session closed for user root
Jul 26 06:44:23 s2.host.ru sudo[3140856]: root : TTY=unknown ; PWD=/usr/local/brainycp ; USER=root ; COMMAND=/usr/bin/stat -c %U /home/nets/lib
Jul 26 06:44:23 s2.host.ru sudo[3140856]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 26 06:44:23 s2.host.ru sudo[3140856]: pam_unix(sudo:session): session closed for user root
root@s2:~#

[alenka]

Вы выше не показали вывод по всем командам.
Какая ос?
systemctl status brainy-socket.service
free -h
systemctl is-enabled brainy-socket.service

[netserg]

снова выскочила ошибка при попытке отредактировать хост аккаунт
вот данные:
ubuntu 20.04
root@s2:~# systemctl status brainy-socket.service
● brainy-socket.service - Brainy os socket daemon program
Loaded: loaded (/lib/systemd/system/brainy-socket.service; enabled; vendor preset: enabled)
Active: failed (Result: core-dump) since Sat 2023-07-29 16:41:39 MSK; 1min 24s ago
Process: 2340138 ExecStart=/usr/bin/brainy_socket --conf_file /etc/sysconfig/brainy-socket.conf --log_file /var/log/brain>
Main PID: 2340149 (code=dumped, signal=ABRT)
CPU: 3ms

Jul 29 16:41:39 s2.hosting.ru systemd[1]: Starting Brainy os socket daemon program...
Jul 29 16:41:39 s2.hosting.ru systemd[1]: Started Brainy os socket daemon program.
Jul 29 16:41:39 s2.hosting.ru systemd[1]: brainy-socket.service: Main process exited, code=dumped, status=6/ABRT
Jul 29 16:41:39 s2.hosting.ru systemd[1]: brainy-socket.service: Failed with result 'core-dump'.
lines 1-11/11 (END)

root@s2:~# free -h
total used free shared buff/cache available
Mem: 7.7Gi 4.1Gi 232Mi 812Mi 3.5Gi 2.6Gi
Swap: 8.0Gi 2.9Gi 5.1Gi

root@s2:~# systemctl is-enabled brainy-socket.service
enabled

[alenka]

Свяжитесь с нами через скайп.

[coliteam]

такая же проблема.
root@oni01:/var/log# uname -a
Linux ---- 5.15.0-107-generic #117-Ubuntu SMP Fri Apr 26 12:26:49 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

root@oni01:/# systemctl start brainy-socket
root@oni01:/# systemctl status brainy-socket
× brainy-socket.service - Brainy os socket daemon program
Loaded: loaded (/lib/systemd/system/brainy-socket.service; enabled; vendor preset: enabled)
Active: failed (Result: core-dump) since Fri 2024-05-31 13:44:42 UTC; 1s ago
Process: 2730100 ExecStart=/usr/bin/brainy_socket --conf_file /etc/sysconfig/brainy-socket.conf --log_file /var/log/brainy/brainy-socket.log --pid_file /run/brainy.pi>
Main PID: 2730102 (code=dumped, signal=ABRT)
CPU: 3ms

May 31 13:44:42 oni01.mycp.site systemd[1]: Starting Brainy os socket daemon program...
May 31 13:44:42 oni01.mycp.site systemd[1]: Started Brainy os socket daemon program.
May 31 13:44:42 oni01.mycp.site systemd[1]: brainy-socket.service: Main process exited, code=dumped, status=6/ABRT
May 31 13:44:42 oni01.mycp.site systemd[1]: brainy-socket.service: Failed with result 'core-dump'.

root@oni01:/var/log# free -h
total used free shared buff/cache available
Mem: 31Gi 2.1Gi 4.8Gi 748Mi 24Gi 27Gi
Swap: 15Gi 32Mi 15Gi

[sbury]

попробуйте перезагрузить сервер
Покажите вывод

Код: Выделить всё

cat /etc/os-release

сделать полное обновление системы после перезагрузки сервера. Дополнительно тут
viewtopic.php?f=7&t=5344

[coliteam]

Код: Выделить всё

PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

и там файлы от 2007 года.. 26kb


заменил другими из Almalinux 9.4 ~32kb и заработало...

Код: Выделить всё

NAME="AlmaLinux"
VERSION="9.4 (Seafoam Ocelot)"
ID="almalinux"
ID_LIKE="rhel centos fedora"
VERSION_ID="9.4"
PLATFORM_ID="platform:el9"
PRETTY_NAME="AlmaLinux 9.4 (Seafoam Ocelot)"
ANSI_COLOR="0;34"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:almalinux:almalinux:9::baseos"
HOME_URL="https://almalinux.org/"
DOCUMENTATION_URL="https://wiki.almalinux.org/"
BUG_REPORT_URL="https://bugs.almalinux.org/"

ALMALINUX_MANTISBT_PROJECT="AlmaLinux-9"
ALMALINUX_MANTISBT_PROJECT_VERSION="9.4"
REDHAT_SUPPORT_PRODUCT="AlmaLinux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.4"
SUPPORT_END=2032-06-01