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

Zabbix server crashes in FreeBSD 12.0

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Won't fix
    • Icon: Blocker Blocker
    • None
    • 3.0.25, 4.0.3
    • Server (S)
    • None
    • FreeBSD 12.0+

      Steps to reproduce:

      1. Upgrade to FreeBSD 12.0**
      2. Build zabbix4_server or zabbix34_server from ports (use pgsql driver)
      3. Run zabbix server: service zabbix_server start

      Result:

       10261:20190205:210917.996 cannot send list of active checks to "127.0.0.1": host [Zabbix server] not found
       10240:20190205:210918.223 Got signal [signal:11(SIGSEGV),reason:2,refaddr:0x800f72510]. Crashing ...
       10240:20190205:210918.223 ====== Fatal information: ======
       10240:20190205:210918.223 program counter not available for this architecture
       10240:20190205:210918.223 === Registers: ===
       10240:20190205:210918.223 register dump not available for this architecture
       10240:20190205:210918.223 === Backtrace: ===
       10240:20190205:210918.224 3: 0x3764a7 <zbx_backtrace+0x37> at /usr/local/sbin/zabbix_server
       10240:20190205:210918.224 2: 0x3765ed <zbx_log_fatal_info+0x7d> at /usr/local/sbin/zabbix_server
       10240:20190205:210918.224 1: 0x37698b <zbx_set_common_signal_handlers+0x2bb> at /usr/local/sbin/zabbix_server
       10240:20190205:210918.224 0: 0x8006094c4 <_pthread_sigmask+0x544> at /lib/libthr.so.3
       10240:20190205:210918.224 === Memory map: ===
       10240:20190205:210918.224 memory map not available for this platform
       10240:20190205:210918.224 ================================
      

      Expected:
      zabbix_server should be up and running.

        1. zabbix_server.log
          143 kB
          Robert Ayrapetyan

            edgar.akhmetshin Edgar Akhmetshin
            Ayrapetyan Robert Ayrapetyan
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: