Problem with tools/scripts in 1.6

[rxm8028]

Greetings,

I recently upgraded from 1.4.5 to 1.6, and now I am attempting to configure scripts to use from the clickable tools menu on one of my maps. I can add a script like /bin/ping -c 5 {HOST.CONN} , allowing all groups / users to execute it with READ access. However, when I click on the script to execute it, the results window pops up, with an error at the bottom, "Cannot connect to ZABBIX server [127.0.0.1:10051] [Success]", and no results returned.

Any suggestions as to what I am missing?

Thanks,

Ross

[rxm8028]

Has no one else run into this problem?

[rrr]

I have a very similar problem. http://www.zabbix.com/forum/showthread.php?t=10951

[rxm8028]

Fixed

The issue I posted above has been eliminated with the release of version 1.6.1.

Many thanks to the developers for correcting this problem.

[rrr]

Scripts still aren't working. 1.6.1 didn't change that!

[Raph]

I am having the same problem, and I am also running 1.6.1. Does anyone have any information on this issue?

the errors:

    * socket_connect() [<a href='function.socket-connect'>function.socket-connect</a>]: unable to connect [111]: Connection refused[/var/www/html/mon/include/scripts.inc.php:76]
    * Cannot connect to ZABBIX server [localhost:8788] [Connection refused]

[nibb]

I also have exactly the same problem with the same output.

Does someone can finally comment on this?

Is this a permission problem from the web interface since when i run

/bin/ping -c 3 iphere

From the command line it works. But the webinterface displays the same error as you posted before. Connection refused.

[Tenzer]

'Cannot connect to ZABBIX server [localhost:8788] [Connection refused]' doesn't at all sound like a permission issue, but rather it trying to connect to a wrong port number or address, since there is no service replying.

[nibb]

'Cannot connect to ZABBIX server [localhost:8788] [Connection refused]' doesn't at all sound like a permission issue, but rather it trying to connect to a wrong port number or address, since there is no service replying.

I fixed it. The localhost config was wrong. Since I was testing the local Zabbix server it failed to resolve its own hostname. Its fixed now.