Ad Widget

Collapse

zabbix 3.0 and systemd problem

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • sles
    Member
    • Oct 2005
    • 80
    #1

    zabbix 3.0 and systemd problem

    Hello!

    I already asked this question in russian section, but...

    I'm planning to migrate our current Centos zabbix installation to Centos 7 lxc container, so I built zabbix 3.0 from srpm and installed it.
    During start I got:

    [root@zabbix zabbix]# systemctl start zabbix-server
    Job for zabbix-server.service failed because a timeout was exceeded. See "systemctl status zabbix-server.service" and "journalctl -xe" for details.


    [root@zabbix zabbix]# systemctl status zabbix-server.service
    ● zabbix-server.service - Zabbix Server
    Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; disabled; vendor preset: disabled)
    Active: deactivating (final-sigterm) (Result: timeout)
    Process: 4491 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
    CGroup: /user.slice/user-0.slice/session-290.scope/system.slice/zabbix-server.service
    └─4493 /usr/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf

    фев 20 10:15:25 zabbix systemd[1]: Starting Zabbix Server...
    фев 20 10:15:25 zabbix systemd[1]: PID file /run/zabbix/zabbix_server.pid not readable (yet?) after start.
    фев 20 10:16:55 zabbix systemd[1]: zabbix-server.service start operation timed out. Terminating.


    But zabbix is started.

    Anyway, I think this error is not good.

    I'm completely newbie in this systemd ... :-(

    If you had the same problem, could you tell me how you solved it?

    Thank you!
    Tags: None
    • sles
      Member
      • Oct 2005
      • 80
      #2
      I found just after I posted this that I had slightly different pid names in config and service files :-( How could I miss it? :-(
      After I changed pid name everything is OK.
      Thank you!

        Comment

        • Ronald
          Junior Member
          • Jun 2012
          • 8
          #3
          Same here

          I got the same issue here.

          systemctl status zabbix-server
          ● zabbix-server.service - Zabbix Server
          Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
          Active: active (running) since Mon 2016-02-22 14:38:08 CET; 5s ago
          Process: 17913 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=0/SUCCESS)
          Process: 18249 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
          Main PID: 18251 (zabbix_server)
          CGroup: /system.slice/zabbix-server.service
          ├─18251 /usr/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
          ├─18255 /usr/sbin/zabbix_server: configuration syncer [waiting 60 sec for processes]
          ├─18256 /usr/sbin/zabbix_server: db watchdog [synced alerts config in 0.127574 sec, idle 60 sec]
          ├─18257 /usr/sbin/zabbix_server: poller #1 [got 0 values in 0.000005 sec, idle 1 sec]
          ├─18258 /usr/sbin/zabbix_server: poller #2 [got 0 values in 0.000009 sec, idle 1 sec]
          ├─18259 /usr/sbin/zabbix_server: poller #3 [got 1 values in 0.000996 sec, idle 1 sec]
          ├─18260 /usr/sbin/zabbix_server: poller #4 [got 0 values in 0.000005 sec, idle 1 sec]
          ├─18261 /usr/sbin/zabbix_server: poller #5 [got 0 values in 0.000009 sec, idle 1 sec]
          ├─18262 /usr/sbin/zabbix_server: unreachable poller #1 [got 0 values in 0.000004 sec, idle 5 sec]
          ├─18263 /usr/sbin/zabbix_server: trapper #1 [processed data in 0.000000 sec, waiting for connection]
          ├─18264 /usr/sbin/zabbix_server: trapper #2 [processed data in 0.000000 sec, waiting for connection]
          ├─18265 /usr/sbin/zabbix_server: trapper #3 [processed data in 0.000000 sec, waiting for connection]
          ├─18266 /usr/sbin/zabbix_server: trapper #4 [processed data in 0.000000 sec, waiting for connection]
          ├─18267 /usr/sbin/zabbix_server: trapper #5 [processed data in 0.000000 sec, waiting for connection]
          ├─18268 /usr/sbin/zabbix_server: icmp pinger #1 [got 0 values in 0.000004 sec, idle 5 sec]
          ├─18269 /usr/sbin/zabbix_server: alerter [sent alerts: 0 success, 0 fail in 0.003938 sec, idle 30 sec]
          ├─18270 /usr/sbin/zabbix_server: housekeeper [startup idle for 30 minutes]
          ├─18271 /usr/sbin/zabbix_server: timer #1 [processed 0 triggers, 0 events in 0.000000 sec, 0 maintenances in 0.000000 sec, idle 22 sec]
          ├─18272 /usr/sbin/zabbix_server: http poller #1 [got 0 values in 0.000850 sec, idle 5 sec]
          ├─18273 /usr/sbin/zabbix_server: discoverer #1 [processed 0 rules in 0.005664 sec, idle 60 sec]
          ├─18274 /usr/sbin/zabbix_server: history syncer #1 [synced 0 items in 0.000001 sec, idle 1 sec]
          ├─18275 /usr/sbin/zabbix_server: history syncer #2 [synced 0 items in 0.000001 sec, idle 1 sec]
          ├─18276 /usr/sbin/zabbix_server: history syncer #3 [synced 1 items in 0.001650 sec, idle 1 sec]
          ├─18277 /usr/sbin/zabbix_server: history syncer #4 [synced 0 items in 0.000001 sec, idle 1 sec]
          ├─18278 /usr/sbin/zabbix_server: escalator #1 [processed 0 escalations in 0.000868 sec, idle 3 sec]
          ├─18279 /usr/sbin/zabbix_server: proxy poller #1 [exchanged data with 0 proxies in 0.000003 sec, idle 5 sec]
          └─18280 /usr/sbin/zabbix_server: self-monitoring [processed data in 0.000005 sec, idle 1 sec]

          Feb 22 14:38:08 t-puppetclient.portbase.home systemd[1]: Starting Zabbix Server...
          Feb 22 14:38:08 t-puppetclient.portbase.home systemd[1]: PID file /run/zabbix/zabbix_server.pid not readable (yet?) after start.
          Feb 22 14:38:08 t-puppetclient.portbase.home systemd[1]: Started Zabbix Server.

          The zabbix-server is running fine in a test environment
          Before I migrate from zabbix 2.4 this issue must be solved.
          How did you correct it ?

          Thanks,

            Comment

            • sles
              Member
              • Oct 2005
              • 80
              #4
              As I said:

              I had different file name for pid in zabbix.conf and
              in systemd untit for zabbix - something like /usr/lib/systemd/system/zabbix-server , I don't remember exactly, because I decided to wait for centos 6 support :-) .
              I changed pid file name in config and thus solved problem...

                Comment

                • rennar
                  Junior Member
                  • May 2017
                  • 1
                  #5
                  Error Zabbix-server--Zabbix-agent

                  Soy nuevo en el mundo de Linux y Zabbix...

                  Buenos dias, ayer instale CentOS7 al mismo le coloque Zabbix 3.0, los servicios de Zabbix (server y agent), no levantan me podrian ayudar por favor...

                  [root@Tacorsa-Zabbix ~]# systemctl start zabbix-server
                  [root@Tacorsa-Zabbix ~]# systemctl status zabbix-server
                  ● zabbix-server.service - Zabbix Server
                  Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
                  Active: activating (auto-restart) (Result: exit-code) since vie 2017-05-26 08:05:14 -04; 9s ago
                  Process: 18498 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)
                  Process: 18526 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
                  Main PID: 18528 (code=exited, status=1/FAILURE)
                  CGroup: /system.slice/zabbix-server.service

                  may 26 08:05:14 Tacorsa-Zabbix systemd[1]: zabbix-server.service: main process exited, code=exited, status=1/FAILURE
                  may 26 08:05:14 Tacorsa-Zabbix systemd[1]: Unit zabbix-server.service entered failed state.
                  may 26 08:05:14 Tacorsa-Zabbix systemd[1]: zabbix-server.service failed.



                  [root@Tacorsa-Zabbix ~]# systemctl start zabbix-agent
                  [root@Tacorsa-Zabbix ~]# systemctl status zabbix-agent
                  ● zabbix-agent.service - Zabbix Agent
                  Loaded: loaded (/usr/lib/systemd/system/zabbix-agent.service; disabled; vendor preset: disabled)
                  Active: activating (auto-restart) (Result: exit-code) since vie 2017-05-26 08:17:29 -04; 5s ago
                  Process: 20183 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)
                  Process: 20178 ExecStart=/usr/sbin/zabbix_agentd -c $CONFFILE (code=exited, status=0/SUCCESS)
                  Main PID: 20180 (code=exited, status=1/FAILURE)
                  CGroup: /system.slice/zabbix-agent.service

                  may 26 08:17:29 Tacorsa-Zabbix systemd[1]: zabbix-agent.service: control process exited, code=exited status=1
                  may 26 08:17:29 Tacorsa-Zabbix kill[20183]: -V, --version output version information and exit
                  may 26 08:17:29 Tacorsa-Zabbix kill[20183]: For more details see kill(1).
                  may 26 08:17:29 Tacorsa-Zabbix systemd[1]: Unit zabbix-agent.service entered failed state.
                  may 26 08:17:29 Tacorsa-Zabbix systemd[1]: zabbix-agent.service failed.
                  [root@Tacorsa-Zabbix ~]#

                  [root@Tacorsa-Zabbix ~]# systemctl start zabbix-agent
                  [root@Tacorsa-Zabbix ~]# systemctl status zabbix-agent
                  ● zabbix-agent.service - Zabbix Agent
                  Loaded: loaded (/usr/lib/systemd/system/zabbix-agent.service; disabled; vendor preset: disabled)
                  Active: activating (auto-restart) (Result: exit-code) since vie 2017-05-26 08:17:29 -04; 5s ago
                  Process: 20183 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)
                  Process: 20178 ExecStart=/usr/sbin/zabbix_agentd -c $CONFFILE (code=exited, status=0/SUCCESS)
                  Main PID: 20180 (code=exited, status=1/FAILURE)
                  CGroup: /system.slice/zabbix-agent.service

                  may 26 08:17:29 Tacorsa-Zabbix systemd[1]: zabbix-agent.service: control process exited, code=exited status=1
                  may 26 08:17:29 Tacorsa-Zabbix kill[20183]: -V, --version output version information and exit
                  may 26 08:17:29 Tacorsa-Zabbix kill[20183]: For more details see kill(1).
                  may 26 08:17:29 Tacorsa-Zabbix systemd[1]: Unit zabbix-agent.service entered failed state.
                  may 26 08:17:29 Tacorsa-Zabbix systemd[1]: zabbix-agent.service failed.
                  [root@Tacorsa-Zabbix ~]#

                    Comment

                    • Atsushi
                      Senior Member
                      • Aug 2013
                      • 2028
                      #6
                      Hi rennar,
                      Is the following log output to the Zabbix server and agent log?

                      Code:
                      25766:20160404:163515.911 cannot set resource limit: [13] Permission denied
                      Please check and adjust your SELinux settings.

                        Comment

                        Previous template Next
                        Working...