[ZBX-3628] server crash in escalator while expanding macros Created: 2011 Mar 18 Updated: 2017 May 30 Resolved: 2011 Mar 23 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | None |
Fix Version/s: | 1.8.5 |
Type: | Incident report | Priority: | Blocker |
Reporter: | Vyacheslav | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
CentOS release 5.4 Zabbix 1.8.5rc1 (revision 18438). |
Attachments: | diz.dmp.bz2 zabbix_server.log | ||||||||
Issue Links: |
|
Description |
server crashed when nodata() used with new items. |
Comments |
Comment by Alexander Vladishev [ 2011 Mar 18 ] |
Thank you for reporting this issue. Please attach a disassembly listing of zabbix_server. This listing can be produced with `objdump -D -S zabbix_server` |
Comment by Vyacheslav [ 2011 Mar 18 ] |
ok, take it |
Comment by Vyacheslav [ 2011 Mar 18 ] |
first time I got this bug on Zabbix 1.8.4 (release) |
Comment by richlv [ 2011 Mar 18 ] |
quite likely same as |
Comment by Vyacheslav [ 2011 Mar 18 ] |
don't know, but this happens just after I imported about 15 snmp host via single xml-file |
Comment by Alexander Vladishev [ 2011 Mar 21 ] |
Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-3628 |
Comment by Vyacheslav [ 2011 Mar 21 ] |
I think this revision is broken, it shows compilation error on target centos and my desktop gentoo x64: Making install in zbxdbhigh |
Comment by Aleksandrs Saveljevs [ 2011 Mar 21 ] |
You should run "make dbschema" before "make" or "make install". |
Comment by Vyacheslav [ 2011 Mar 21 ] |
tnx Aleksandrs, it helps. #0] cannot be evaluated: Evaluation failed for function: {lenina_9:net.speed.if16.abschange(0)} |
Comment by Aleksandrs Saveljevs [ 2011 Mar 22 ] |
Vyacheslav, changes in this development branch should not have affected evaluation of functions. In particular, abschange() can only fail if item does not have a previous value. So you can probably safely disregard that error message. |
Comment by Alexander Vladishev [ 2011 Mar 23 ] |
Fixed in version pre1.8.5, r18609. |