[ZBX-10685] Escalator crash sending mail Zabbix 3.0.1 Centos 7 Created: 2016 Apr 19 Updated: 2017 May 30 Resolved: 2016 Apr 20 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Trivial |
| Reporter: | Jerrod Tracy | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | crash, smtp | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
DB Records.png
zabbix-server
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
We're having an issue similar to Basically the server crashes whenever it send's an alert email. It was sending email fine last week then I stopped it because I had it reporting on all events. I changed it to only send on Diaster events and the first pass it ran crashed the server. I'm going to test sending for other severity level's to see if mail will send. I've attached logs, screenshot of database, and what I think you're looking for on binary's (If not please let me know where the best place to look would be, I just did an rpm install.) |
| Comments |
| Comment by Aleksandrs Saveljevs [ 2016 Apr 20 ] |
|
Backtrace for easier searching: 7721:20160418:144012.217 === Backtrace: === 7721:20160418:144012.217 20: /usr/sbin/zabbix_server: alerter [sending alerts](print_fatal_info+0x287) [0x487d77] 7721:20160418:144012.217 19: /usr/sbin/zabbix_server: alerter [sending alerts]() [0x488076] 7721:20160418:144012.217 18: /lib64/libc.so.6(+0x35670) [0x7f5120b7c670] 7721:20160418:144012.217 17: /lib64/libnss3.so(PK11_DigestOp+0x1f) [0x7f511e13261f] 7721:20160418:144012.217 16: /lib64/libcurl.so.4(+0x4274a) [0x7f512166a74a] 7721:20160418:144012.217 15: /lib64/libcurl.so.4(+0x4e519) [0x7f5121676519] 7721:20160418:144012.217 14: /lib64/libcurl.so.4(+0x484cc) [0x7f51216704cc] 7721:20160418:144012.217 13: /lib64/libcurl.so.4(+0x4721e) [0x7f512166f21e] 7721:20160418:144012.217 12: /lib64/libcurl.so.4(+0x32268) [0x7f512165a268] 7721:20160418:144012.217 11: /lib64/libcurl.so.4(curl_multi_perform+0xd1) [0x7f512165b121] 7721:20160418:144012.217 10: /lib64/libcurl.so.4(curl_easy_perform+0xf3) [0x7f51216524a3] 7721:20160418:144012.217 9: /usr/sbin/zabbix_server: alerter [sending alerts]() [0x48b197] 7721:20160418:144012.217 8: /usr/sbin/zabbix_server: alerter [sending alerts](send_email+0x1a9) [0x48b3d9] 7721:20160418:144012.217 7: /usr/sbin/zabbix_server: alerter [sending alerts](execute_action+0x33f) [0x41e1bf] 7721:20160418:144012.217 6: /usr/sbin/zabbix_server: alerter [sending alerts](alerter_thread+0x305) [0x41e635] 7721:20160418:144012.217 5: /usr/sbin/zabbix_server: alerter [sending alerts](zbx_thread_start+0x57) [0x488b27] 7721:20160418:144012.217 4: /usr/sbin/zabbix_server: alerter [sending alerts](MAIN_ZABBIX_ENTRY+0x41d) [0x41da8d] 7721:20160418:144012.217 3: /usr/sbin/zabbix_server: alerter [sending alerts](daemon_start+0x1da) [0x4872da] 7721:20160418:144012.217 2: /usr/sbin/zabbix_server: alerter [sending alerts](main+0x39f) [0x41812f] 7721:20160418:144012.217 1: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f5120b68b15] 7721:20160418:144012.217 0: /usr/sbin/zabbix_server: alerter [sending alerts]() [0x4183e5] |
| Comment by Aleksandrs Saveljevs [ 2016 Apr 20 ] |
|
According to the backtrace, this issue does not seem to have anything to do with |
| Comment by Aleksandrs Saveljevs [ 2016 Apr 20 ] |
|
Closing as a duplicate of |
| Comment by Aleksandrs Saveljevs [ 2016 Apr 20 ] |
|
You can remove the log now if it contains any private information. |