[ZBX-19138] The default configuration line "Plugins.Redis.Uri=tcp://localhost:6379" deemed incorrect Created: 2021 Mar 19  Updated: 2024 Apr 10  Resolved: 2023 Jan 23

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent2 plugin (G)
Affects Version/s: 5.0.9
Fix Version/s: 5.0.31rc1, 6.0.13rc1, 6.2.7rc1, 6.4.0beta6, 6.4 (plan)

Type: Problem report Priority: Trivial
Reporter: Victor Sudakov Assignee: Eriks Sneiders
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian 10, zabbix-agent2 installed from the " http://repo.zabbix.com/zabbix/5.0/debian buster/main amd64" repo


Team: Team INT
Sprint: Sprint 95 (Dec 2022), Sprint 96 (Jan 2023)
Story Points: 0.5

 Description   

On zabbix-agent2, when I only uncomment the provided line from the default config:

Plugins.Redis.Uri=tcp://localhost:6379

zabbix-agent2 does not start with the message:

zabbix_agent2 [6152]: ERROR: cannot create scheduling manager: invalid plugin Redis configuration: Cannot assign configuration: invalid parameter Plugins.Redis.Uri at line 32: unknown parameter

Of course I tried other hostnames instead of "localhost" with the same result.

*Expected result: *

zabbix-agent2 should start and begin monitoring a Redis server at localhost:6379 or some other host:port



 Comments   
Comment by Victor Sudakov [ 2021 Mar 19 ]

Overriding the connect URL from the {$REDIS.CONN.URI} macro seems to work fine, but overriding from the agent2 config does not.

Comment by Eriks Sneiders [ 2023 Jan 12 ]

Fixed in:

Comment by Eriks Sneiders [ 2023 Jan 12 ]

For anyone who wishes to provide the URI in the Zabbix agent 2 configuration file, it needs to be provided as a session parameters, e.g:

Plugins.Redis.Sessions.<SessionName>.Uri=tcp://localhost:6379

For more information please check out our documentation for Redis plugin at https://www.zabbix.com/documentation/current/en/manual/appendix/config/zabbix_agent2_plugins/redis_plugin

Generated at Thu May 29 10:31:34 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.