Ryan Armstrong
Ryan Armstrong
@zentavr Could you please raise a PR with your deb code?
I apologize I haven't had the bandwidth to do this. Package maintaining tends to require a lot of commitment that I can't offer right now (testing on multiple-OSes is the...
What is the output for: `$ pkg-config dbus-1 --modversion`?
I suspect you mean sending a sample using the 'Zabbix Sender' protocol? If so, that is outside the scope of this package. This package provides access to the Zabbix API,...
What operating system and version of Go and Zabbix are you using?
I can reproduce this issue on Go 1.5.1, Zabbix 2.2.10 on CentOS 7.1. I'll advise what I find. Might be an issue with go routines firing up in the `net`...
System call trace: ``` [pid 12184] select(6, [4 5], NULL, NULL, NULL) = 1 (in [4]) [pid 12184] accept(4, {sa_family=AF_INET, sin_port=htons(47746), sin_addr=inet_addr("127.0.0.1")}, [16]) = 6 [pid 12184] getpeername(6, {sa_family=AF_INET, sin_port=htons(47746),...
Thanks Jan, that's really helpful. I'll dig right into this one ASAP.
Same issue occurs in https://github.com/spektroskop/zabbix-socket/. I haven't had time to debug yet, but I'm leaning towards an implementation conflict between Zabbix Agent Listener threads and Go routines (used by the...
Thanks for posting those details. Unfortunately I haven't been able to find a solution or even a workaround. The best I can offer is that it looks like a dead...