(6) all strings have to be reviewed by someone experienced && experienced in English
<dimir> AKA Rich :-D
<zalex> yes, because SlaVa took several strings from the description of my testing cases. They were NOT the strings for the GUI, they were only my thought
<zalex> at least the line "Server in "localhost" and daemon not running." should be reviewed. Original version (my ) was "Server is Localhost and daemon not running". is <-> in
<zalex> pavels, who is reviewer? all strings were reviewed? no any correction after last SlaVa's changes? REOPENED
<pavels> For some reason I've thought that you've done it already. My fault.
<pavels> Currently the PHP errors are replaced as follows:
<richlv> rewrote & fixed some of the messages - suggested to use the following
PHP: Connection refused
ZBX: Connection to Zabbix server "localhost" refused. Possible reasons: 1. Incorrect server IP/DNS in the "zabbix.conf.php"; 2. Security environment (for example, SELinux) is blocking the connection; 3. Zabbix server daemon not running; 4. Firewall is blocking the connection. Error Description: Connection refused
PHP: No route to host
ZBX: Zabbix server "localhost" can not be reached. Possible reasons: 1. Incorrect server IP/DNS in the "zabbix.conf.php"; 2. Incorrect network configuration. Error Description: No route to host
PHP: Connection timed out
ZBX: Connection to Zabbix server "localhost" timed out. Possible reasons: 1. Incorrect server IP/DNS in the "zabbix.conf.php"; 2. Firewall is blocking the connection. Error Description: Connection timed out
PHP: Name or service not known
ZBX: Connection to Zabbix server "localhost" failed. Possible reasons: 1. Incorrect server IP/DNS in the "zabbix.conf.php"; 2. Incorrect DNS server configuration; Error Description: php_network_getaddresses: getaddrinfo failed: Name or service not known
<pavels> We should probably add a default message, that doesn't cover these specific cases.
<richlv> in that case we should simply print out whatever error we got from php
<zalex> Suggested by Rich messages reviewed, excellent! Rich, are you sure in the "PHP: Connection refused -> ZBX: 4. Firewall is blocking the connection" ?
As I know "Connection refused" it's an interpretation of ICMP message from TCP/IP host stack or firewall that requested TCP port is not opened or not allowed. So, if a firewall is, then it will silently block any traffic (in most cases) and we have to see Connection timeout. Maybe it worth to add one word "TCP": Firewall is blocking TCP connection. ?
<richlv> firewalls can reject or drop packets, you will see timeout in one case and, connection refused in another. i'd omit tcp, as zabbix connections always are tcp - if we go that way, message will become very complex
<SlaVa>RESOLVED r24160 with "Firewall is blocking TCP connection" variant ...
<zalex> missing quotes for sever name %s in S_NOT_RUN. Would bu useful to see it as Rich suggested. "localhost" name hardcoded for S_TIME_OUT
<pavels> Still missing the quotes in S_NOT_RUN.
<Slava>RESOLVED r 24239