[ZBX-15781] Zabbix problem with SMTP authentication Created: 2019 Mar 07 Updated: 2019 Mar 10 Resolved: 2019 Mar 08 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | 4.2.0beta2 |
Fix Version/s: | None |
Type: | Problem report | Priority: | Blocker |
Reporter: | SuNova | Assignee: | Arturs Lontons |
Resolution: | Duplicate | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: |
![]() ![]() ![]() |
||||||||
Issue Links: |
|
Description |
Hello Please first see zabbix_log I attached. Before we were using smtp with no authentication because all warning mails we were sending were being sent to the same mail server (organization domain). Recently we had a problem which was requiring sending emails to some people outside the organization. As soon as that special problem happened, zabbix_server crashed. |
Comments |
Comment by Edgar Akhmetshin [ 2019 Mar 07 ] |
Hello SuNove, Please, provide operating system info (name and version), installation type (from sources or from packages), media type settings used and full password example with all characters. Also attach: ldd $(which zabbix_server) objdump -DSswx $(which zabbix_server) Regards, |
Comment by SuNova [ 2019 Mar 07 ] |
Hello Edgar, Here we go: [root@LCT-MON-Zabbix ~]# uname -a Linux LCT-MON-Zabbix 3.10.0-957.5.1.el7.x86_64 #1 SMP Fri Feb 1 14:54:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux [root@LCT-MON-Zabbix ~]# cat /etc/centos-release CentOS Linux release 7.6.1810 (Core) [root@LCT-MON-Zabbix ~]# yum list zabbix-server* Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.alastyr.com * epel: mirror.hoster.kz * extras: mirror.fibersunucu.com.tr * ius: ftp.upcnet.ro * updates: mirror.netdirekt.com.tr Installed Packages zabbix-server-pgsql.x86_64 4.2.0-0.4beta2.el7 @zabbix zabbix [root@LCT-MON-Zabbix ~]# ldd $(which zabbix_server) linux-vdso.so.1 => (0x00007ffff86f6000) libpq.so.5 => /usr/pgsql-11/lib/libpq.so.5 (0x00007f000a4bc000) libiksemel.so.3 => /lib64/libiksemel.so.3 (0x00007f000a2ae000) libxml2.so.2 => /lib64/libxml2.so.2 (0x00007f0009f44000) libodbc.so.2 => /lib64/libodbc.so.2 (0x00007f0009cdc000) libnetsnmp.so.31 => /lib64/libnetsnmp.so.31 (0x00007f00099da000) libssh2.so.1 => /lib64/libssh2.so.1 (0x00007f00097b0000) libOpenIPMI.so.0 => /lib64/libOpenIPMI.so.0 (0x00007f00094a3000) libOpenIPMIposix.so.0 => /lib64/libOpenIPMIposix.so.0 (0x00007f000929b000) libz.so.1 => /lib64/libz.so.1 (0x00007f0009085000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f0008e69000) libevent-2.0.so.5 => /lib64/libevent-2.0.so.5 (0x00007f0008c21000) libssl.so.10 => /lib64/libssl.so.10 (0x00007f00089af000) libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007f000854e000) libldap-2.4.so.2 => /lib64/libldap-2.4.so.2 (0x00007f00082f9000) liblber-2.4.so.2 => /lib64/liblber-2.4.so.2 (0x00007f00080ea000) libcurl.so.4 => /lib64/libcurl.so.4 (0x00007f0007e81000) libm.so.6 => /lib64/libm.so.6 (0x00007f0007b7f000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f000797b000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f0007762000) libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f0007500000) libc.so.6 => /lib64/libc.so.6 (0x00007f0007133000) libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007f0006ee6000) libldap_r-2.4.so.2 => /lib64/libldap_r-2.4.so.2 (0x00007f0006c87000) libgnutls.so.28 => /lib64/libgnutls.so.28 (0x00007f000694d000) libgcrypt.so.11 => /lib64/libgcrypt.so.11 (0x00007f00066cc000) libgpg-error.so.0 => /lib64/libgpg-error.so.0 (0x00007f00064c7000) liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f00062a1000) libltdl.so.7 => /lib64/libltdl.so.7 (0x00007f0006097000) libOpenIPMIutils.so.0 => /lib64/libOpenIPMIutils.so.0 (0x00007f0005e8d000) libgdbm.so.4 => /lib64/libgdbm.so.4 (0x00007f0005c84000) /lib64/ld-linux-x86-64.so.2 (0x00007f000ac46000) libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f000599b000) libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f0005797000) libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f0005564000) libsasl2.so.3 => /lib64/libsasl2.so.3 (0x00007f0005347000) libssl3.so => /lib64/libssl3.so (0x00007f00050f5000) libsmime3.so => /lib64/libsmime3.so (0x00007f0004ece000) libnss3.so => /lib64/libnss3.so (0x00007f0004ba1000) libnssutil3.so => /lib64/libnssutil3.so (0x00007f0004971000) libplds4.so => /lib64/libplds4.so (0x00007f000476d000) libplc4.so => /lib64/libplc4.so (0x00007f0004568000) libnspr4.so => /lib64/libnspr4.so (0x00007f000432a000) libidn.so.11 => /lib64/libidn.so.11 (0x00007f00040f7000) libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007f0003ee7000) libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f0003ce3000) libp11-kit.so.0 => /lib64/libp11-kit.so.0 (0x00007f00039b4000) libtasn1.so.6 => /lib64/libtasn1.so.6 (0x00007f00037a1000) libnettle.so.4 => /lib64/libnettle.so.4 (0x00007f0003570000) libhogweed.so.2 => /lib64/libhogweed.so.2 (0x00007f0003349000) libgmp.so.10 => /lib64/libgmp.so.10 (0x00007f00030d1000) libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f0002e9a000) librt.so.1 => /lib64/librt.so.1 (0x00007f0002c92000) libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f0002a6b000) libffi.so.6 => /lib64/libffi.so.6 (0x00007f0002863000) libfreebl3.so => /lib64/libfreebl3.so (0x00007f0002660000) [root@LCT-MON-Zabbix ~]# objdump -DSswx $(which zabbix_server) > /tmp/zabbix.dmp Dump and shot are attached. |
Comment by Vladislavs Sokurenko [ 2019 Mar 07 ] |
Backtrace for easier searching: 31360:20190307:091558.167 Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x50]. Crashing ... 31360:20190307:091558.168 === Backtrace: === 31360:20190307:091558.168 21: /usr/sbin/zabbix_server: alerter #3 started(zbx_backtrace+0x35) [0x5573d7a0d0d1] 31360:20190307:091558.168 20: /usr/sbin/zabbix_server: alerter #3 started(zbx_log_fatal_info+0x119) [0x5573d7a0d2ec] 31360:20190307:091558.168 19: /usr/sbin/zabbix_server: alerter #3 started(+0x18f601) [0x5573d7a0d601] 31360:20190307:091558.168 18: /lib64/libpthread.so.0(+0xf5d0) [0x7f387b6835d0] 31360:20190307:091558.168 17: /lib64/libnss3.so(PK11_DigestOp+0x1f) [0x7f38773e486f] 31360:20190307:091558.168 16: /lib64/libcurl.so.4(+0x43dfa) [0x7f387a6cfdfa] 31360:20190307:091558.168 15: /lib64/libcurl.so.4(+0x4fca9) [0x7f387a6dbca9] 31360:20190307:091558.168 14: /lib64/libcurl.so.4(+0x49c38) [0x7f387a6d5c38] 31360:20190307:091558.168 13: /lib64/libcurl.so.4(+0x4897e) [0x7f387a6d497e] 31360:20190307:091558.168 12: /lib64/libcurl.so.4(+0x334d8) [0x7f387a6bf4d8] 31360:20190307:091558.168 11: /lib64/libcurl.so.4(curl_multi_perform+0xd1) [0x7f387a6c03b1] 31360:20190307:091558.168 10: /lib64/libcurl.so.4(curl_easy_perform+0xf3) [0x7f387a6b7623] 31360:20190307:091558.168 9: /usr/sbin/zabbix_server: alerter #3 started(+0x19fff1) [0x5573d7a1dff1] 31360:20190307:091558.168 8: /usr/sbin/zabbix_server: alerter #3 started(send_email+0x252) [0x5573d7a1e38e] 31360:20190307:091558.168 7: /usr/sbin/zabbix_server: alerter #3 started(+0x4034a) [0x5573d78be34a] 31360:20190307:091558.168 6: /usr/sbin/zabbix_server: alerter #3 started(alerter_thread+0x377) [0x5573d78bebd7] 31360:20190307:091558.169 5: /usr/sbin/zabbix_server: alerter #3 started(zbx_thread_start+0x37) [0x5573d7a1a704] 31360:20190307:091558.169 4: /usr/sbin/zabbix_server: alerter #3 started(MAIN_ZABBIX_ENTRY+0xaba) [0x5573d78bda5d] 31360:20190307:091558.169 3: /usr/sbin/zabbix_server: alerter #3 started(daemon_start+0x31b) [0x5573d7a0c922] 31360:20190307:091558.169 2: /usr/sbin/zabbix_server: alerter #3 started(main+0x312) [0x5573d78bcfa1] 31360:20190307:091558.169 1: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f38799603d5] 31360:20190307:091558.169 0: /usr/sbin/zabbix_server: alerter #3 started(+0x3e0a9) [0x5573d78bc0a9] Looks like a duplicate of |
Comment by Arturs Lontons [ 2019 Mar 08 ] |
Hi, Closing as a duplicate of |
Comment by SuNova [ 2019 Mar 10 ] |
Hi, Well you are right, but in my personal opinion, this is about exception handling. I believe when alerter encounters such a failure, it should fail the action intended to be performed, not just getting crashed. Also, even if alterter crashes, I believe parent process (zabbix_server) should not get stopped, especially in a mission critical enterprise level monitoring system like Zabbix. Monitoring a monitoring system is not even an option in my opinion. With warmest regards. |