Segmentation Fault Running zabbix_sender

[kmh27]

I just upgraded to 1.1 beta 1 on Red Hat.

Server and agents all seem to be working fine, but we make extensive use of zabbix_sender in our environment and I'm unable to get it to work after upgrading.

My build does not include snmp (although I'm about to add it just in case that's somehow related) and i'm not statically linking.

./configure --enable-server --with-mysql --enable-agent --prefix=/usr/local/zabbix

When I run ./zabbix_sender localhost 10051 Server.Name key 1
With a valid server and key I get:
Segmentation fault

The only other references I saw to this in the forum was someone stating he was using the wrong parms. But I'm pretty sure I'm adhering to the usage guidelines:
Usage: zabbix_sender <Zabbix server> <port> <server> <key> <value>
If no arguments are given, zabbix_sender expects list of parameters
from standard input.

I'm guessing it's something in the server code or communication. Here are some example runs, server is listening on 10051. 's' is not a valid server and 'k' is not a valid key, but they produce same results as valid servers/keys
[zabbix@localhost bin]$ ./zabbix_sender localhost 10051 s k 1
Segmentation fault
[zabbix@localhost bin]$ ./zabbix_sender localhost 10058 s k 1
[zabbix@localhost bin]$

Please help!

[kmh27]

Workaround

I reverted just zabbix_sender back to my previously installed alpha 5 and it seems to work fine.

Note I am aware of the change in argument syntax "server:key value" vs. "server key value".

So I'm still not sure what was causing this. I'll run a diff on zabbix_sender code to see if i spot anything.

[StanZoid]

Another sender memory fault

I too just upgraded to 1.1 beta 1 on Red Hat. When I try to use zabbix_sender in any way, I get the message "Memory fault." I suspect that this is related to the segmentation fault mentioned in this thread.

System info: Linux <server> 2.6.9-5.EL #1 Wed Jan 5 19:22:18 EST 2005 i686 athlon i386 GNU/Linux

A lot of implementation is on hold pending resolution of this problem, so I'm eagerly awaiting word.

Thanks!