Zabbix 1.4 - server dies when "autodiscover process" tries to run action

[Maximum]

Hi,

What I have done:
1.fresh install of zabbix 1.4 on Ubuntu 6.06 LTS Server edition Kernel 2.6.15-26-server #1 SMP
2. installed the windows client on a windows 2003 32-bit SP2 machine
3. activated auto-discovery in zabbix and it found my host
4. activated the default action "Auto discovery, Windows servers."
5. tailed the zabbix server log and when the auto discovery again reached my windows 2003 servers IP the zabbix server process died.

the last lines from my log:

31317:20070609:131305 IP [192.168.100.33]
31317:20070609:131305 Query [select dcheckid,druleid,type,key_,snmp_community,ports from dchecks where druleid=2]
31317:20070609:131305 In process_check(ip:192.168.100.33, ports:10050, type:9)
31317:20070609:131305 In discover_service(ip:192.168.100.33, port:10050, type:9)
31317:20070609:131305 In get_value_agent(host:192.168.100.33,ip:192.168.100 .33,key:system.uname
31317:20070609:131305 Sending [system.uname
]
31317:20070609:131305 Before read
31317:20070609:131305 End get_value_agent(result:Windows STOAVI01 5.2.3790 Windows Server 2003 Service Pack 1 Intel IA-32)
31317:20070609:131305 End discover_service()
31317:20070609:131305 In update_service(ip:192.168.100.33, port:10050, status:up)
31317:20070609:131305 In register_host(ip:192.168.100.33)
31317:20070609:131305 Query [select dhostid,druleid,ip,status,lastup,lastdown from dhosts where ip='192.168.100.33' and dhostid>=100000000000000*0 and dhostid<=(100000000000000*0+99999999999999) ]
31317:20070609:131305 Host is already in database
31317:20070609:131305 End register_host()
31317:20070609:131305 In register_service(ip:192.168.100.33,port:10050)
31317:20070609:131305 Query [select dserviceid,dhostid,type,port,status,lastup,lastdow n,value,key_ from dservices where dhostid=3 and type=9 and port=10050 and key_='system.uname']
31317:20070609:131305 Service is already in database
31317:20070609:131305 End register_service()
31317:20070609:131305 In add_service_event()
31317:20070609:131305 In process_event(eventid:0,object:2,objectid:3)
31317:20070609:131305 In DBget_maxid(events,eventid)
31317:20070609:131305 Query [select nextid from ids where nodeid=0 and table_name='events' and field_name='eventid']
31317:20070609:131305 Query [update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='eventid']
31317:20070609:131305 Query [select nextid from ids where nodeid=0 and table_name='events' and field_name='eventid']
31317:20070609:131305 713
31317:20070609:131305 Query [insert into events(eventid,source,object,objectid,clock,value) values(713,1,2,3,1181387585,0)]
31317:20070609:131305 In process_actions(sourceISCOVERY,eventid:713)
31317:20070609:131305 Processing actions
31317:20070609:131305 Query [select actionid,evaltype,status,eventsource from actions where status=0 and eventsource=1 and actionid>=100000000000000*0 and actionid<=(100000000000000*0+99999999999999) ]
31317:20070609:131305 In check_action_conditions (actionid:3)
31317:20070609:131305 Query [select conditionid,actionid,conditiontype,operator,value from conditions where actionid=3 order by conditiontype]
31317:20070609:131305 In check_action_condition [actionid:3,conditionid:14,cond.value:9]
31317:20070609:131305 CONDITION_TYPE_DSERVICE_TYPE [0:9]
31317:20070609:131305 Query [select dserviceid from dservices where type=9 and dserviceid=3]
31128:20070609:131305 One child process died. Exiting ...
31251:20070609:131305 Got signal. Exiting ...
31250:20070609:131305 Got signal. Exiting ...
31284:20070609:131305 Got signal. Exiting ...
31247:20070609:131305 Got signal. Exiting ...
31266:20070609:131305 Got signal. Exiting ...
31281:20070609:131305 Got signal. Exiting ...
31253:20070609:131305 Got signal. Exiting ...
31285:20070609:131305 Got signal. Exiting ...
31275:20070609:131305 Got signal. Exiting ...
31256:20070609:131305 Got signal. Exiting ...
31268:20070609:131305 Got signal. Exiting ...
31314:20070609:131305 Got signal. Exiting ...
31264:20070609:131305 Got signal. Exiting ...
31311:20070609:131305 Got signal. Exiting ...
31262:20070609:131305 Got signal. Exiting ...
31288:20070609:131305 Got signal. Exiting ...
31258:20070609:131305 Got signal. Exiting ...
31249:20070609:131305 Got signal. Exiting ...
31287:20070609:131305 Got signal. Exiting ...
31254:20070609:131305 Got signal. Exiting ...
31291:20070609:131305 Got signal. Exiting ...
31279:20070609:131305 Got signal. Exiting ...
31290:20070609:131305 Got signal. Exiting ...
31260:20070609:131305 Got signal. Exiting ...
31248:20070609:131305 Got signal. Exiting ...
31270:20070609:131305 Got signal. Exiting ...
31128:20070609:131307 ZABBIX Server stopped

my auto discovery action:

Name: Auto discovery. Windows servers.
Event source: Triggers Discovery
Type of calculation [AND / OR] "(A) and (B) and (c)"
Conditions
(A) Service type = "ZABBIX agent"
(B) Discovery status = "Up"
(C) Received value like "Windows"

Operations
Add to group "Windows servers"

Status Enabled


My first guess was that the problem had something to do with adding the host to the "windows servers" group, I removed that operation and still got the same result.

After that I re-added the "add to group" operation and deleted the "link to template" operation.
Still same result.


Any Ideas ?

Best regards /Maximum

[Maximum]

Does the auto discovery work for anyone ?

Hi,

I still have the problem above, and can´t seem to find a solution.
Am I the only one who uses the auto discovery feature or is there anyone who manage to get it up and running ?
If you got it working, which distribution/kernel do you use ?

Best regards /Maximum

[Alexei]

There are several problems with DM in 1.4. Most (all?) of them are already fixed in the latest code which, along with updated manual, will be released as 1.4.1 soon.

[welkin]

I have the same Problem and Auto Discovery is very important for me. Also IT-Services is one of the things which need fixing. Can you tell me when 1.4.1 is gonna be released?
mfg
welkin