Problem with beta 8 and up

[noteb]

I have a problem with beta 8 and up. The problem is that zabbix shuts down when multiple icmp-monitored hosts go down. After hosts go down zabbix continues to monitor them by moving them in queue and then dies with that messages in log (debug level = 4):
011088:20060529:093514 Executing query:select serviceupid from services_links where servicedownid=11
011088:20060529:093514 Executing query:select l.serviceupid,s.algorithm from services_links l,services s where s.serviceid=l.serviceupid and l.servicedownid=12
011088:20060529:093514 Executing query:select serviceupid from services_links where servicedownid=12
011088:20060529:093514 Executing query:select l.serviceupid,s.algorithm from services_links l,services s where s.serviceid=l.serviceupid and l.servicedownid=11
011088:20060529:093514 Executing query:select serviceupid from services_links where servicedownid=11
011088:20060529:093514 Executing query:select l.serviceupid,s.algorithm from services_links l,services s where s.serviceid=l.serviceupid and l.servicedownid=12
011088:20060529:093514 Executing query:select serviceupid from services_links where servicedownid=12
011088:20060529:093514 Executing query:select l.serviceupid,s.algorithm from services_links l,services s where s.serviceid=l.serviceupid and l.servicedownid=11
011088:20060529:093514 Executing query:select serviceupid from services_links where servicedownid=11
011088:20060529:093514 Executing query:select l.serviceupid,s.algorithm from services_links l,services s where s.serviceid=l.serviceupid and l.servicedownid=12
011088:20060529:093514 Executing query:select serviceupid from services_links where servicedownid=12
011088:20060529:093514 Executing query:select l.serviceupid,s.algorithm from services_links l,services s where s.serviceid=l.serviceupid and l.servicedownid=11
011088:20060529:093514 Executing query:select serviceupid from services_links where servicedownid=11
011083:20060529:093514 One server process died. Shutting down...
011083:20060529:093514 0. Killing PID=[11085]
011083:20060529:093514 1. Killing PID=[11087]
011083:20060529:093514 2. Killing PID=[11088]
011083:20060529:093514 3. Killing PID=[11089]
011083:20060529:093514 4. Killing PID=[11094]
011083:20060529:093514 5. Killing PID=[11095]
011083:20060529:093514 6. Killing PID=[11096]
011083:20060529:093514 7. Killing PID=[11101]
011083:20060529:093514 8. Killing PID=[11102]
011083:20060529:093514 9. Killing PID=[11103]
011083:20060529:093514 ZABBIX server is down.
011085:20060529:093514 Server [1]. Got QUIT or INT or TERM or PIPE signal. Exiting...
011087:20060529:093514 Server [2]. Got QUIT or INT or TERM or PIPE signal. Exiting...
011089:20060529:093514 Server [4]. Got QUIT or INT or TERM or PIPE signal. Exiting...
011094:20060529:093514 Server [5]. Got QUIT or INT or TERM or PIPE signal. Exiting...
011095:20060529:093514 Server [6]. Got QUIT or INT or TERM or PIPE signal. Exiting...
011096:20060529:093514 Server [7]. Got QUIT or INT or TERM or PIPE signal. Exiting...
011101:20060529:093514 Server [8]. Got QUIT or INT or TERM or PIPE signal. Exiting...
011102:20060529:093514 Server [9]. Got QUIT or INT or TERM or PIPE signal. Exiting...
011103:20060529:093514 Server [10]. Got QUIT or INT or TERM or PIPE signal. Exiting...


Bold messages repeat many times!

Please help me to resolve this bug/error (I don't know what is that, may be I configured something wrong).
zabbix server configured to use mysql socket connection (not tcp).

[Alexei]

Perhaps there is a loop in your definition of IT Services?

[noteb]

Perhaps there is a loop in your definition of IT Services?

Thank you for your attention on my problem.
I had that problem when I used beta 8 without any IT-services configured.
Now, for test, I deleted all IT-services, but the problem persists with the same log messages.

What it can be? I'm currently using beta 11.

[noteb]

Anybody knows where is the problem?

[noteb]

I have just installed beta 12 and the problem persists.
I'm in panic.