Ошибка юнита zabbix server service

Добрый день!

Установил Centos 8, после все что нужно для Zabbix.
Но не запускается Zabbix-Server.

journalctl -xe

апр 29 16:19:24 localhost.localdomain setroubleshoot[7451]: AnalyzeThread.run(): Set alarm timeout to 10
апр 29 16:19:27 localhost.localdomain systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
апр 29 16:19:27 localhost.localdomain systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 647.
-- Subject: Назначен автоматический перезапуск юнита
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Назначен автоматический перезапуск юнита zabbix-server.service, так как для него был задан 
-- параметр Restart=.
апр 29 16:19:27 localhost.localdomain systemd[1]: Stopped Zabbix Server.
-- Subject: Завершена остановка юнита zabbix-server.service.
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Процесс остановки юнита zabbix-server.service был завершен.
апр 29 16:19:27 localhost.localdomain systemd[1]: Starting Zabbix Server...
-- Subject: Начинается запуск юнита zabbix-server.service
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Начат процесс запуска юнита zabbix-server.service.
апр 29 16:19:27 localhost.localdomain setroubleshoot[7451]: AnalyzeThread.run(): Cancel pending alarm
апр 29 16:19:27 localhost.localdomain zabbix_server[26672]: zabbix_server [26672]: Cannot initialize IPC services: Cannot access path "/var/run/zabbix": [13] Permission denied.
апр 29 16:19:27 localhost.localdomain systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
апр 29 16:19:27 localhost.localdomain systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- The unit zabbix-server.service has entered the 'failed' state with result 'exit-code'.
апр 29 16:19:27 localhost.localdomain systemd[1]: Failed to start Zabbix Server.
-- Subject: Ошибка юнита zabbix-server.service
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Произошел сбой юнита zabbix-server.service.
-- 
-- Результат: failed.
апр 29 16:19:27 localhost.localdomain xrdp-chansrv[16616]: [ERROR] clipboard_event_selection_request: unknown target text/plain;charset=utf-8

Скрин панели Zabbix, пишет что Zabbix сервер запущен — нет
608a8952b36b3277801396.jpeg


  • Вопрос задан

    более двух лет назад

  • 1243 просмотра

Пригласить эксперта

Cannot access path «/var/run/zabbix»: [13] Permission denied.

Что непонятного?

Тут не с заббиксом проблема, а с английским.
Белым по черному написано, что доступ запрещен. Проверяйте разрешения на указанные папки.

Привет! У меня схожая проблема.
Только она заключается в том, что заббикс не может подключиться к базе.
в логах:

connection to database 'zabbix' failed: [1045] Access denied for user 'zabbix'@'localhost' (using password: YES)
database is down: reconnecting in 10 seconds

Проверил, пользователь (пароль) правильный. Под атрибутами (с которыми подключаюсь к базе зашел в mysql), пробовал даже под рутом подключить заббикс к базе, тот же результат.
Не могу понять в чем проблема…
Прошу помочь.


  • Показать ещё
    Загружается…

25 июн. 2023, в 11:42

600 руб./за проект

25 июн. 2023, в 10:30

6000 руб./за проект

25 июн. 2023, в 10:26

15000 руб./за проект

Минуточку внимания

13
Посты

3
Пользователи

1
Likes

5,610
Просмотры

Guardian

(@guardian)

Active Member

Присоединился: 2 года назад

Коллеги, всем добрый день.
Такой вопрос, вдруг кто сталкивался.
Имеется Zabbix на ESXI, который успешно работает, с него делается снапшот.
Снапшот разворачивается на другом ESXI с другим именем виртуальной машины и на другом IP.
Соответственно, ничего не меняется, кроме самого IP виртуальной машины и имени (по сути).
Все настройки .conf, база данных, все остальное — неизменно.
Zabbix-agent успешно стартует

zabbix-agent.service — Zabbix Agent
Loaded: loaded (/lib/systemd/system/zabbix-agent.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2020-11-30 17:19:54 MSK; 17h ago
Docs: man:zabbix_agentd
Main PID: 430 (zabbix_agentd)
Tasks: 6 (limit: 4915)
CGroup: /system.slice/zabbix-agent.service
├─430 /usr/sbin/zabbix_agentd —foreground
├─449 /usr/sbin/zabbix_agentd: collector [idle 1 sec]
├─450 /usr/sbin/zabbix_agentd: listener #1 [waiting for connection]
├─451 /usr/sbin/zabbix_agentd: listener #2 [waiting for connection]
├─452 /usr/sbin/zabbix_agentd: listener #3 [waiting for connection]
└─453 /usr/sbin/zabbix_agentd: active checks #1 [idle 1 sec]

Nov 30 17:19:54 LDP-ZABBIXT-AP01 systemd[1]: Started Zabbix Agent.
Nov 30 17:19:57 LDP-ZABBIXT-AP01 zabbix_agentd[430]: Starting Zabbix Agent [Zabbix server]. Zabbix 4.0.19 (revision a566532084).

Zabbix-server — нет.

zabbix-server.service — LSB: Start zabbix-server daemon
Loaded: loaded (/etc/init.d/zabbix-server; generated; vendor preset: enabled)
Active: active (exited) since Mon 2020-11-30 17:45:32 MSK; 16h ago
Docs: man:systemd-sysv-generator(8)
Process: 842 ExecStop=/etc/init.d/zabbix-server stop (code=exited, status=0/SUCCESS)
Process: 880 ExecStart=/etc/init.d/zabbix-server start (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/zabbix-server.service

Nov 30 17:45:32 LDP-ZABBIXT-AP01 systemd[1]: Starting LSB: Start zabbix-server daemon…
Nov 30 17:45:32 LDP-ZABBIXT-AP01 systemd[1]: Started LSB: Start zabbix-server daemon.

В лог файл информация не пишется, PID не создаётся.
Zabbix 4.0.6

Кто-то сталкивался с подобным? Есть какие-либо мысли?

Zerox

(@zerox)

Prominent Member

Присоединился: 9 лет назад

Попробуй сделать reinstall пакета zabbix-server-mysql. Такое ощущение, что я уже видел что-то подобное и помогла перестановка. Именно после клона не стартовал сервер. 

STALKER_SLX

(@stalker_slx)

Estimable Member

Присоединился: 4 года назад

@guardian , если проблема таки решена — отмечайте данную тему «решенной», чтобы другим пользователям гугла было легче и быстрее найти свое решение!

I just installed Zabbix 5.0 LTS (The Latest verion of Zabbix) on RHEL-8 OS. On logging in the Zabbix front end, I gett a message saying «Zabbix server is not working». & bar below says:»Zabbix server not working.Information delayed may not be current».Kindly provide help?

Edit:My server port is 10051.

On entering «service zabbix start», I get output:

Redirecting to /bin/systemctl start zabbix.service
Failed to start zabbix.service:Unit zabbix.service not found.

& on entering «systemctl restart zabbix-server zabbix-agent httpd php-fpm», I get:

Job for zabbix-server.service failed because the control process exited with error code.
See "systemctl status zabbix-server.service" and "journalctl -xe" for details.

Output of «journalctl -xe»:

RHEL8 platform-python[5746]: SELinux is preventing zabbix_server from using the dac_override capability.
*** Plugin dac_overrride (91.4 confidence) suggests ************************

If you want to help identify if domain needs this access or you have a file with the wrong permissions on your system
Then turn on full auditing to get path information about the offending file and generate the error again.
Do

Turn on full auditing
#auditctl -w /etc/shadow -p w
Try to recreate AVC.Then execute
#ausearch -m avc -ts recent
If you see PATH record check ownership/permissions on file, and fix it,
otherwise report as a bugzilla

*** Plugin catchall (9.59 confidence) suggests *************************

If you believe that zabbix_server should have the dac_override capability by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
#ausearch -c 'zabbix_server' --raw | audit2allow -M my-zabbixserver
#semodule -X 300 -i my-zabbixserver.pp            

RHEL8 dbus-daemon[779]: [system] Activating service name='org.fedoraproject.Setroubleshootd' requested by ':1.40' (uid=0 pid=748 comm="/usr/sbin/sedispatch " label="sytem_u:system_r:auditd_t:s0") (using servicehelper)

On entering «systemctl status zabbix-server.service», I get output:

zabbix-server.service-Zabbix server: Loaded:....
                                     Active:....
                                     Process: 4959 ExecStart=/usr/sbin/zabbix_server -c $CONFILE (code=exited,status=1/FAILURE) 
RHEL8 systemd[1]:zabbix-server.service:Control process exited,code=exited status=1
RHEL8 systemd[1]:zabbix-server.service:Failed with result 'exit-code'.
RHEL8 systemd[1]:Failed to start Zabbix Server. What do I do now?

I just installed Zabbix-5.0 LTS on RHEL-8 OS. After logging in on the Zabbix fronend, I get message that «Zabbix server is not running:the information displayed may not be correct». Kindly help me with server installation.

My Zabbix server port is 10051.

On entering service zabbix start, I get output:

Redirecting to /bin/systemctl start zabbix.service
Failed to start zabbix.service:Unit zabbix.service not found.

and on entering systemctl restart zabbix-server zabbix-agent httpd php-fpm I get:

Job for zabbix-server.service failed because the control process exited with error code.
See "systemctl status zabbix-server.service" and "journalctl -xe" for details.

Output of «journalctl -xe»:

RHEL8 platform-python[5746]: SELinux is preventing zabbix_server from using the dac_override capability.

*** Plugin dac_overrride (91.4 confidence) suggests ************************
If you want to help identify if domain needs this access or you have a file with the wrong permissions on your system
Then turn on full auditing to get path information about the offending file and generate the error again.
Do

Turn on full auditing
#auditctl -w /etc/shadow -p w
Try to recreate AVC.Then execute
#ausearch -m avc -ts recent
If you see PATH record check ownership/permissions on file, and fix it,
otherwise report as a bugzilla

*** Plugin catchall (9.59 confidence) suggests *************************

If you believe that zabbix_server should have the dac_override capability by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
#ausearch -c 'zabbix_server' --raw | audit2allow -M my-zabbixserver
#semodule -X 300 -i my-zabbixserver.pp           

RHEL8 dbus-daemon[779]: [system] Activating service name='org.fedoraproject.Setroubleshootd' requested by ':1.40' (uid=0 pid=748 comm="/usr/sbin/sedispatch " label="sytem_u:system_r:auditd_t:s0") (using servicehelper)

On entering «systemctl status zabbix-server.service», I get output:

zabbix-server.service-Zabbix server: Loaded:....
                                   Active:....
                                   Process: 4959 
ExecStart=/usr/sbin/zabbix_server -c $CONFILE (code=exited,status=1/FAILURE)
RHEL8 systemd[1]:zabbix-server.service:Control process exited,code=exited status=1
RHEL8 systemd[1]:zabbix-server.service:Failed with result 'exit-code'.
RHEL8 systemd[1]:Failed to start Zabbix Server. What do I do now?

  • Type:


    Incident report

  • Status:

    Closed


  • Priority:


    Trivial

  • Resolution:

    Commercial support required


  • Affects Version/s:



    6.2.6

  • Fix Version/s:



    None

Steps to reproduce:

  1. [email protected]:~# systemctl restart zabbix-server
    Job for zabbix-server.service failed because the service did not take the steps required by its unit configuration.
    See «systemctl status zabbix-server.service» and «journalctl -xeu zabbix-server.service» for details.
    [email protected]:~# journalctl -xeu zabbix-server.service
    ░░ A start job for unit zabbix-server.service has begun execution.
    ░░
    ░░ The job identifier is 48958.
    Jan 24 12:57:07 nks-worker-2 systemd[1]: zabbix-server.service: Can’t open PID file /run/zabbix/zabbix_server.pid (yet?) after start: Operation not permitted
    Jan 24 12:57:07 nks-worker-2 systemd[1]: zabbix-server.service: Failed with result ‘protocol’.
    ░░ Subject: Unit failed
    ░░ Defined-By: systemd
    ░░ Support: http://www.ubuntu.com/support
    ░░
    ░░ The unit zabbix-server.service has entered the ‘failed’ state with result ‘protocol’.
    Jan 24 12:57:07 nks-worker-2 systemd[1]: Failed to start Zabbix Server.
    ░░ Subject: A start job for unit zabbix-server.service has failed
    ░░ Defined-By: systemd
    ░░ Support: http://www.ubuntu.com/support

Result:
i have attached the screen shot 
Expected:
See screenshot….
See attached patch file…

  1. Capture.PNG

    Capture.PNG
    43 kB
    2023 Jan 24 10:29


0

0

Сабж.

-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit zabbix-server.service has begun starting up.
 systemd[1]: zabbix-server.service: PID file /var/run/zabbix/zabbix_server.pid not readable (yet?) after start: No such file or directory
 zabbix_server[20496]: zabbix_server [20499]: cannot open "/var/log/zabbix-server/zabbix_server.log": [2] No such file or directory
 systemd[1]: zabbix-server.service: Daemon never wrote its PID file. Failing.
 systemd[1]: Failed to start Zabbix Server.
-- Subject: Unit zabbix-server.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit zabbix-server.service has failed.
--
-- The result is failed.
 systemd[1]: zabbix-server.service: Unit entered failed state.
 systemd[1]: zabbix-server.service: Failed with result 'resources'.
 sudo[20493]: pam_unix(sudo:session): session closed for user root
 sudo[20502]: user : TTY=pts/0 ; PWD=/lib/systemd/system ; USER=root ; COMMAND=/bin/journalctl -xe

zabbix-server.conf дефолтный, только данные для связи с Postgres вписал ( https://pastebin.com/727ecmGw ).

Сеё пытаюсь поднять на ubuntu server 16.04, что крутится в виртуалочке esxi. Заббикс ставил из официальных репов по официальной инструкции. SELinux выключен.
Что ему не нравится?

I’m having trouble starting zabbix server on centOS 7.

This is the status message I get after trying to start zabbix-server:

[root@monitor2:~] #systemctl status zabbix-server
zabbix-server.service - Zabbix Server
   Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; disabled)
   Active: failed (Result: start-limit) since Thu 2016-04-28 01:15:16 EDT; 20s ago
  Process: 23744 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=killed, signal=SEGV)
 Main PID: 31446 (code=exited, status=1/FAILURE)

Apr 28 01:15:16 monitor2 systemd[1]: zabbix-server.service: control process exited, code=killed status=11
Apr 28 01:15:16 monitor2 systemd[1]: Failed to start Zabbix Server.
Apr 28 01:15:16 monitor2 systemd[1]: Unit zabbix-server.service entered failed state.
Apr 28 01:15:16 monitor2 systemd[1]: zabbix-server.service holdoff time over, scheduling restart.
Apr 28 01:15:16 monitor2 systemd[1]: Stopping Zabbix Server...
Apr 28 01:15:16 monitor2 systemd[1]: Starting Zabbix Server...
Apr 28 01:15:16 monitor2 systemd[1]: zabbix-server.service start request repeated too quickly, refusing to start.
Apr 28 01:15:16 monitor2 systemd[1]: Failed to start Zabbix Server.
Apr 28 01:15:16 monitor2 systemd[1]: Unit zabbix-server.service entered failed state.

And this is what I see in the zabbix server log:

[root@monitor2:~] #tail /var/log/zabbix/zabbix_server.log
zabbix_server [24366]: [file:'log.c',line:271] lock failed: [43] Identifier removed
zabbix_server [24366]: [file:'log.c',line:271] lock failed: [43] Identifier removed
zabbix_server [24370]: [file:'log.c',line:271] lock failed: [43] Identifier removed
zabbix_server [24370]: [file:'log.c',line:271] lock failed: [43] Identifier removed
zabbix_server [24374]: [file:'log.c',line:271] lock failed: [43] Identifier removed
zabbix_server [24374]: [file:'log.c',line:271] lock failed: [43] Identifier removed
 24378:20160428:011714.312 [Z3001] connection to database 'zabbix' failed: [1045] Access denied for user 'zabbix'@'localhost' (using password: YES)
 24378:20160428:011714.312 database is down: reconnecting in 10 seconds
 19933:20160428:011714.593 [Z3001] connection to database 'zabbix' failed: [1045] Access denied for user 'zabbix'@'localhost' (using password: YES)
 19933:20160428:011714.593 database is down: reconnecting in 10 seconds

This is my /etc/zabbix/zabbix_server.conf file:

LogFile=/var/log/zabbix/zabbix_server.log
LogFileSize=0
PidFile=/var/run/zabbix/zabbix_server.pid
DBName=zabbix
DBUser=zabbix
DBPassword='secret'
SNMPTrapperFile=/var/log/snmptt/snmptt.log
ListenIP=127.0.0.1
AlertScriptsPath=/usr/lib/zabbix/alertscripts
ExternalScripts=/usr/lib/zabbix/externalscripts

And this is my /etc/zabbix/web/zabbix.conf.php

 <?php
// Zabbix GUI configuration file.
global $DB;

$DB['TYPE']     = 'MYSQL';
$DB['SERVER']   = '127.0.0.1';
$DB['PORT']     = '0';
$DB['DATABASE'] = 'zabbix';
$DB['USER']     = 'zabbix';
$DB['PASSWORD'] = 'secret';

// Schema name. Used for IBM DB2 and PostgreSQL.
$DB['SCHEMA'] = '';

$ZBX_SERVER      = 'zabbix.example.com';
$ZBX_SERVER_PORT = '10051';
$ZBX_SERVER_NAME = 'Zabbix';

$IMAGE_FORMAT_DEFAULT = IMAGE_FORMAT_PNG;
?>

And I can connect to the mysql database using the same credentials as I have listed in both config files:

[root@monitor2:~] #mysql -uzabbix -p -h 127.0.0.1
Enter password:
Welcome to the MariaDB monitor.  Commands end with ; or g.
Your MariaDB connection id is 36326
Server version: 10.0.22-MariaDB MariaDB Server

Copyright (c) 2000, 2015, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or 'h' for help. Type 'c' to clear the current input statement.

So I don’t know why the zabbix server fails to connect to the database.

I’d appreciate some help on this!

  • Ошибка юнита smbd service
  • Ошибка юнита networking service
  • Ошибка юнита mysql service
  • Ошибка юнита mariadb service
  • Ошибка юнита kesl supervisor service