If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to REGISTER before you can post. To start viewing messages, select the forum that you want to visit from the selection below.
Using debugger I have found the reason.
Now, "-z <zabbix server>" is mandatory when with "-i <file>" it shouldn't be because zabbix server is in each line of the input file.
Using debugger I have found the reason.
Now, "-z <zabbix server>" is mandatory when with "-i <file>" it shouldn't be because zabbix server is in each line of the input file.
No, it's not
Not only the command-line changed, the format of the input file, obviously, too.
See this thread for details.
The zabbix-server is no longer included in the input file.
So, that's why the parameter "-z <zabbix server>" is now mandatory !
IMHO this is a bug.
OK, so it's a bug in usage message because it says that zabbix server is the first column of each line in input file and also it's not enough clear in options.
I read the user's manual of version 1.6 and it is also insufficient.
OK, so it's a bug in usage message because it says that zabbix server is the first column of each line in input file and also it's not enough clear in options.
I read the user's manual of version 1.6 and it is also insufficient.
Thank you!
I'll try to summarize our findings about the zabbix_sender 1.6:
The usage message should be fixed
The option "-z zabbix server" should not be mandatory on the command-line
The file format should stay the same or another option to choose the new format should be available and/or, at least, the documentation updated
What do you think ?
Does that summary cover all the problems we noticed and is it the right proposal for a solution ?
I agree with you, first point is prioritary but, in my case, points 2 and 3 are not important because I don't have so much scripts with zabbix_sender.
If most of administrators have a lot of scripts could be important to maintain compatibility.
Comment