Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-15844

Zabbix server inability to start on certain conditions - manager process is late after a child

    Details

    • Team:
      Team A
    • Sprint:
      Sprint 50 (Mar 2019), Sprint 51 (Apr 2019)
    • Story Points:
      0.5

      Description

      The story:

      Due to some unrelated to this issue problems (probably system overload or slow database connection establishment or something) Zabbix server on startup starts threads significantly slower then it has to.

      When there are hundreds of threads to start, the process might take 20-30 seconds. Which isn't a problem itself at all.

      The problem: if takes more then 10 seconds to start threads between the first "alerter" thread has been started and the alert manager thread, which happens quite later, then the alerter thread times out with 111 error, exiting and causing Zabbix server to stop.

      I propose the solution: start alert manager threads first. Which i assume might be accomplished by changing server.c code, in
      int get_process_info_by_thread(
      function responsible for the order of threads being started.

      And move lines

      else if (local_server_num <= (server_count += CONFIG_ALERTMANAGER_FORKS))
          {
              *local_process_type = ZBX_PROCESS_TYPE_ALERTMANAGER;
              *local_process_num = local_server_num - server_count + CONFIG_ALERTMANAGER_FORKS;
          }
       

      ahead of

      else if (local_server_num <= (server_count += CONFIG_ALERTER_FORKS))
          {
              *local_process_type = ZBX_PROCESS_TYPE_ALERTER;
              *local_process_num = local_server_num - server_count + CONFIG_ALERTER_FORKS;
          }
      

      I did so on my test environment, the problem with alert processes has gone, and i have found no other issues with it.

      Thanks

        Attachments

          Activity

            People

            • Assignee:
              ak Andrejs Kozlovs
              Reporter:
              makurov Mikhail Makurov
            • Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: