I tried to reproduce it with current trunk and 2.0.2 release.

I'm not sure my was scenario identical to Maxim's so I'll describe it in short:

1. I have a windows host (with discs C and D) with configured just one regular item key "vfs.fs.size[C:,pfree]" which is working.
2. I've linked a new 2.0.0 template "Template OS Windows" to the host (one discovery rule (60 seconds update interval), one item prototype, one trigger prototype).
3. I got additional lld-item (for disc D) and two lld-triggers (for discs C and D).
Note that I got the lld-trigger for disc D, which belongs to the regular item, which was existed before I linked the template.
It's NOT very good, moreover I consider this as a bug.
4. But after waiting tens of minutes I didn't get duplicated lld-triggers.

An error status of the discovery rule is always "Cannot create item [vfs.fs.size[C:,pfree]]: item already exists"

Maxim, make sure that you are really using 2.0.2 and your case in not like a ZBX-5148.

Or where is my error in my attempt to reproduce it ?

Added:
Note that after "unlink and clear" the template, lld-triggers (wrongly linked to regular items) will stay (with flag=4 in DB) but visually they look like regular triggers.

When I try to open such trigger by just click (these is a link already as for regular trigger) I receive an error:
ERROR: No permissions to referred object or it does not exist!

Luckily it's possible delete such incorrect triggers using checkboxes and a drop-down delete action.

zalex_ua the bug observed here moved to ZBX-5781
This comment is CLOSED.

Ok, it seems my scenario to reproduce bug is wrong, also I believe it is not connected to ZBX-5148.
I'll try to reproduce correct scenario and comment here, for now please see attached picture what I have on host.

As you can see here there are many identical triggers for for each item. All these items are static in Template (also I have the same items in LLD)

See lld_bug1 picture to see my items, also here there are discovered items for disk E because I have no such items in WIN template.

Maxim, it's hard to imagine what is going on there.

I'm afraid we need a clean scenario how to reproduce this issue. Maybe you could try setup a new clean DB and try to reproduce it on your side as you know all details ?

Just FYI - there was a change (from 2.0.0 to 2.0.1) on agent side, maybe it somehow related, see ZBX-5094
Describe please history of installed/upgraded agent versions on this host.

Btw, thank you for good speech on zabconf2012
If you could bring remote access to this system to check it, it would be great.

On this host there was agent 1.8.2 and then I upgrade it to 2.0.2

$ zabbix_agentd.exe -V
Zabbix Agent Win32 (service) v2.0.2 (revision 29212) (31 July 2012)
Compilation time: Jul 31 2012 11:56:50

Unfortunatelly I didn't have time to work on reproducing this bug this week, please hold on.

is that cygwin ?

zalex_ua it's even more strange - cygdrive + .exe

I just show you agent version in ssh cygwin session, i believe issue not connected to cygwin.

Cool !
Would be better to hide that shell path from our eyes

I have success in reproducing the bug.
My Scenario is correct, so i will try to provide you additional info.

Server version
Zabbix server v2.0.2 (revision 29214) (31 July 2012)

• Compilation time: Sep 24 2012 09:17:21
• Agent see comment above.

On windows:
1. Create items on host for disks spaces (free,pfree)
2. Create triggers for these items on host with names different from discovery trigger names
#Comment: p.1 and p.2 should be not templated.

3. Now create template and in this template:
4. Create discovery rule for the same items as in p.1 with items and triggers
5. Link template to this host

Discovery period - 120 sec
Left this host for some hours, for me I just left it for one day, for one day I have + 3500 triggers with 120 secs period

I'll retest right now.

One important thing I miss, this host should be monitored by proxy.

Zabbix proxy v2.0.2 (revision 29214) (31 July 2012)
Compilation time: Sep 4 2012 13:42:14

I cannot reproduce it following updated scenario with or without a proxy (active mode, btw).
Please export to XML two resources:
the host with just 2 items and triggers.
the template you are linking to the host.

Just in case, the proxy is active or passive ?

Also try please it once again on fresh, just created 2.0 database.

Zabbix proxy - active
Zabbix server was upgraded from 1.8.10 to 2.0.2 and also important thing I miss it was converted to node.
I will try to find time to reproduce bug on fresh database, but I belive its connected with upgrade.

I don't think the DM (nodes) can be related here.

We are waiting your reproduction for now.

I am also seeing this issue of duplicate LLD triggers for Windows file system LLD discovery.

Here are my details and steps that created issue:

Upgraded server to 2.0.4 from 1.8.12. Just enabled LLD after upgrading all clients to 2.0.4

Zabbix server v2.0.4 (revision 31984) (08 December 2012)
Zabbix Agent Win64 (service) v2.0.4 (revision 31980) (08 December 2012)

c_Template_OS_Windows template has non-LLD item for vfs.fs.size[c:,pfree]
c_Template_OS_Windows template has non-LLD trigger on vfs.fs.size[c:,pfree]

Added LLD item prototypes to c_Template_OS_Windows template for:
vfs.fs.size[

,total]
vfs.fs.size[

,used]

LLD items populated to hosts where discovered multiple drives.

Got expected "Cannot create item [vfs.fs.size[C:,pfree]]: item already exists" for existing non-LLD item.

Added LLD trigger prototype to c_Template_OS_Windows template for:
{c_Template_OS_Windows:vfs.fs.size[

,pused] and now see all the 'pfree' triggers plus the 'pused' triggers.
Any additional changes to LLD trigger create additional trigger on hosts. (IE: Changed severity from High to Average, now 2 triggers show on hosts; one high, one average)

Majority of LLD triggers show as 'Disabled' with 'Trigger just added. No status update so far' in error.

All the duplicate triggers are associated with the non-LLD item for vfs.fs.size[c:,pfree]

Attached screenshot of example host triggers (HostTriggers_161.jpg), template trigger prototype (TemplateTriggerPrototype.jpg), and template XML (zbx_c_Template_OS_Windows.xml).

Please let me know if more information is necessary to troubleshoot.

Thanks

Added attachment. Example host export linked to trouble template.

Christopher, this is a known problem and reproduced already, reported in ZBX-5781

There is one important thing - uppercase or lowercase drive letter for existing non-lld items.

Disregarding that this issue has been created earlier than the ZBX-5781, but I'd close it as duplicate

I'm closing it as duplicate of ZBX-5781.
Hope all are agree