Ad Widget

Collapse

Démarrage de Zabbix-Server impossible

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Actarus76
    Junior Member
    • May 2017
    • 17

    #1

    Démarrage de Zabbix-Server impossible

    Bonjour

    J'ai un Zabbix 3.2.0 et je n'arrive plus à démarrer mon server.

    Tentative de démarrage:
    systemctl start zabbix-server
    Job for zabbix-server.service failed because a configured resource limit was exceeded. See "systemctl status zabbix-server.service" and "journalctl -xe" for details.

    Je regarde donc ce que m'affiche journalctl -xe:

    Unit zabbix-server.service has begun starting up.
    Jun 01 12:08:22 XXX-Server systemd[1]: PID file /fs03/PRO/zabbix/run/zabbix_server.pid not readable (yet?) after start.
    Jun 01 12:08:22 XXX-Server systemd[1]: zabbix-server.service never wrote its PID file. Failing.
    Jun 01 12:08:22 XXX-Server systemd[1]: Failed to start Zabbix Server.
    -- Subject: Unit zabbix-server.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman.../systemd-devel
    --
    -- Unit zabbix-server.service has failed.
    --
    -- The result is failed.
    Jun 01 12:08:22 XXX-Server systemd[1]: Unit zabbix-server.service entered failed state.
    Jun 01 12:08:22 XXX-Server systemd[1]: zabbix-server.service failed.
    Jun 01 12:08:32 XXX-Server systemd[1]: zabbix-server.service holdoff time over, scheduling restart.
    Jun 01 12:08:32 XXX-Server systemd[1]: Starting Zabbix Server...
    -- Subject: Unit zabbix-server.service has begun start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman.../systemd-devel
    --
    -- Unit zabbix-server.service has begun starting up.
    Jun 01 12:08:32 XXX-Server systemd[1]: zabbix-server.service: Supervising process 30455 which is not our child. We'll most likely not notice when it exits.
    Jun 01 12:08:32 XXX-Server systemd[1]: Started Zabbix Server.
    -- Subject: Unit zabbix-server.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman.../systemd-devel
    --
    -- Unit zabbix-server.service has finished starting up.
    --
    -- The start-up result is done.
    Jun 01 12:08:32 XXX-Server systemd[1]: zabbix-server.service: main process exited, code=exited, status=1/FAILURE
    Jun 01 12:08:32 XXX-Server kill[30457]: Usage:
    Jun 01 12:08:32 XXX-Server kill[30457]: kill [options] <pid|name> [...]
    Jun 01 12:08:32 XXX-Server kill[30457]: Options:
    Jun 01 12:08:32 XXX-Server kill[30457]: -a, --all do not restrict the name-to-pid conversion to processes
    Jun 01 12:08:32 XXX-Server kill[30457]: with the same uid as the present process
    Jun 01 12:08:32 XXX-Server kill[30457]: -s, --signal <sig> send specified signal
    Jun 01 12:08:32 XXX-Server kill[30457]: -q, --queue <sig> use sigqueue(2) rather than kill(2)
    Jun 01 12:08:32 XXX-Server kill[30457]: -p, --pid print pids without signaling them
    Jun 01 12:08:32 XXX-Server kill[30457]: -l, --list [=<signal>] list signal names, or convert one to a name
    Jun 01 12:08:32 XXX-Server kill[30457]: -L, --table list signal names and numbers
    Jun 01 12:08:32 XXX-Server kill[30457]: -h, --help display this help and exit
    Jun 01 12:08:32 XXX-Server kill[30457]: -V, --version output version information and exit
    Jun 01 12:08:32 XXX-Server kill[30457]: For more details see kill(1).
    Jun 01 12:08:32 XXX-Server systemd[1]: zabbix-server.service: control process exited, code=exited status=1
    Jun 01 12:08:32 XXX-Server systemd[1]: Unit zabbix-server.service entered failed state.
    Jun 01 12:08:32 XXX-Server systemd[1]: zabbix-server.service failed.

    Dans le fichier zabbix_server.log j'ai:

    30791:20170601:121025.385 Jabber notifications: NO
    30791:20170601:121025.385 Ez Texting notifications: YES
    30791:20170601:121025.385 ODBC: NO
    30791:20170601:121025.385 SSH2 support: YES
    30791:20170601:121025.385 IPv6 support: YES
    30791:20170601:121025.385 TLS support: YES
    30791:20170601:121025.385 ******************************
    30791:20170601:121025.385 using configuration file: /fs03/PRO/zabbix/etc/zabbix_server.conf
    30791:20170601:121025.385 cannot allocate shared memory of size 228170138: [12] Cannot allocate memory
    30791:20170601:121025.385 cannot allocate shared memory for configuration cache


    Quelqu'un a t il une idée pour résoudre ce problème???

    D'avance merci.
  • tiramiseb
    Senior Member
    • Sep 2012
    • 427

    #2
    Salut,

    Originally posted by Actarus76
    a configured resource limit was exceeded.
    C'est plutôt clair comme message, non ?

    30791:20170601:121025.385 cannot allocate shared memory of size 228170138: [12] Cannot allocate memory
    30791:20170601:121025.385 cannot allocate shared memory for configuration cache
    Et ça c'est cohérent avec le message d'au-dessus.

    Quelqu'un a t il une idée pour résoudre ce problème???
    Une recherche Google rapide sur "cannot allocate shared memory of size" retourne :

    Join the friendly and open Zabbix community on our forums and social media platforms.
    Traducteur principal de Zabbix en français ces derniers temps - Blog personnel - Boutique de domotique "DIY"

    Comment

    Working...