[ZBX-10886] Monitoring SQLserver 2008 cause crash in zabbix server Created: 2016 Jun 07 Updated: 2017 May 30 Resolved: 2016 Oct 13 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | 3.0.3 |
Fix Version/s: | None |
Type: | Incident report | Priority: | Trivial |
Reporter: | Leandro Moreira | Assignee: | Unassigned |
Resolution: | Won't fix | Votes: | 0 |
Labels: | crash, items, odbc | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Debian jessie 8.4, with oracle driver (10.2.0.4) and SQLServer driver(msodbcsql-13.0.0.0.tar.gz) instaled |
Attachments: | zabbix_server.zip |
Description |
when I set the zabbix to run on a bank sqlserver 2008, a query (select getdate ();) zabbix the server performs a query without problems, but in the second run, it displays the following message: 10646: 20,160,607: 104839,621 Got signal [signal 11 (SIGSEGV), reason: 1, refaddr: 0x18]. Crashing ... 10646: 20,160,607: 104839,621 ====== Fatal information: ====== 10646: 20,160,607: 104839,627 Program counter: 0x7f63c533849a 10646: 20,160,607: 104839,627 === Registers: === 10646: 20160607: 104839,627 r8 = 0 = 0 = 0 10646: 20,160,607: 104839,627 r9 = 17df6b0 = 25,032,368 = 25,032,368 10646: 20,160,607: 104839,627 r10 = 7ffd6dc69670 = 140726445184624 = 140726445184624 10646: 20,160,607: 104839,627 r11 = 7f63cd3c1110 = 140066621755664 = 140066621755664 10646: 20,160,607: 104839,627 r12 = 7ffd6dc69950 = 140726445185360 = 140726445185360 10646: 20,160,607: 104839,627 r13 = 7ffd6dc69940 = 140726445185344 = 140726445185344 10646: 20160607: 104839,627 r14 = 0 = 0 = 0 10646: 20,160,607: 104839,627 r15 = 7ffd6dc69910 = 140726445185296 = 140726445185296 10646: 20,160,607: 104839,627 rdi 7ffd6dc69940 = = = 140726445185344 140726445185344 10646: 20,160,607: 104839,627 RSI = 13f = 319 = 319 10646: 20,160,607: 104839,627 rbp 7ffd6dc69a10 = = = 140726445185552 140726445185552 10646: 20,160,607: 104839,627 rbx 7f63c55ba2c0 = = = 140066489606848 140066489606848 10646: 20,160,607: 104839,628 rdx = 7f63c52cb3e0 = 140066486531040 = 140066486531040 10646: 20,160,607: 104839,628 rax = 0 = 0 = 0 10646: 20,160,607: 104839,628 rcx = fffffffffff6f4f0 = 18446744073708958960 = -592 656 10646: 20,160,607: 104839,628 rsp = 7ffd6dc698c0 = 140726445185216 = 140726445185216 10646: 20,160,607: 104839,628 rip 7f63c533849a = = = 140066486977690 140066486977690 10646: 20,160,607: 104839,628 efl = 10297 = 66199 = 66199 10646: 20160607: 104839,628 csgsfs = 33 = 51 = 51 10646: 20,160,607: 104839,628 err = 4 = 4 = 4 10646: 20160607: 104839,628 and trapno = 14 = 14 = 10646: 20,160,607: 104839,628 oldmask = 0 = 0 = 0 10646: 20160607: 104839,628 a2 = 18 = 24 = 24 10646: 20,160,607: 104839,628 Backtrace ===: === Customer donwload the link: https://www.microsoft.com/en-us/download/details.aspx?id=36437. I tested both versions and the problem persists, the strange thing is that on another server work, performing the same installation procedures. I thank all if they can give me any tips on how to solve. |
Comments |
Comment by Glebs Ivanovskis (Inactive) [ 2016 Aug 09 ] |
Very little can be said, seems like attached zabbix_server objdump does not match logfile. Quote from logfile itself seems to be corrupted. Which version of UnixODBC do you use? Can you attach a proper crash log and zabbx_server objdump (preferably with debug information)? |
Comment by Leandro Moreira [ 2016 Oct 13 ] |
Dear, thank you for your answer Thanks for your attention. |
Comment by Leandro Moreira [ 2016 Oct 13 ] |
For SQL Server 2008 databases configured the freetds tool for access to the database and solved the problem for SQL Server versions higher than 2008, Microsoft SQL Driver works without any problems. |
Comment by Glebs Ivanovskis (Inactive) [ 2016 Oct 13 ] |
Reopening to change Resolution. |
Comment by Glebs Ivanovskis (Inactive) [ 2016 Oct 13 ] |
Closing as Won't Fix. |