Hi Robert, On Thursday 16 July 2015 19:18:03 Robert Gladewitz wrote: > thank you for the answere. For sure, you can reproduce this errors. I > have done the folowing steps again and the error was happening: > > 1. Import the Schema and Standard in mysql. > 2. Set Zabbix Server as node 1 (zabbix_server -n1) > 3. Import my exported templates > 4. import my exported hosts > > So, now you show you ids table and find out, thats last ids for node 0 > and node 1 are showing! Now you can try edit or create a item or trigger > - the error message with duplicate key will show! Also you can see error > message in the zabbix_server.log for the recovered entries will show!
I see... But it is not just about reproducing. I will have to look for
isolated fix for this problem in upstream repository and see if it can be
backported and applied to version 2.2.7. Then (provided that fix is not
intrusive) I will have to do some regression tests and try to convince
release team to include the fix. Considering that only few users are affected
chances to introduce fix to "stable" are low -- that's how "stable" releases
are protected from regressions. All of this is possible to do but requires
great deal of time and effort so realistically it is just not going to
happen.
> In our policy, it is not allow use versions not supported by main stable
> version on debian (or other distributions). This means, wie have to use
> the debian package versions.
This is a very nice policy indeed. Respect. :)
> I have try this on a testsystem - the error
> ost not happening on version 2.4.4.
This is a good news. Perhaps if I upload 2.4.5 to "jessie-backports" it could
fix the problem for you. However (unless you can arrange some funding for
this work) it will take months before I'll be able to allocate time to
prepare backport. You can read more about backports here:
http://backports.debian.org/
--
Cheers,
Dmitry Smirnov.
---
Perhaps is is better to be irresponsible and right, than to be responsible
and wrong.
-- Winston Churchill
signature.asc
Description: This is a digitally signed message part.
