[horde] Errors webinterface admin screens

[Nels Lindquist]

On 2026-05-21 3:55 PM, Nels Lindquist wrote:
> On 2026-05-20 12:29 AM, Ralf Lang wrote:
>> can you please update to https://github.com/horde/HashTable/releases/ 
>> tag/v2.0.0RC2 <https://github.com/horde/HashTable/releases/tag/ 
>> v2.0.0RC2> and use the new redis tester?
>> I'd like to understand more about why your setup fails.

<SNIP>

> I just keep getting the following:
> 
> # sudo -u apache ./vendor/bin/horde-redis-tester --help
> Error: Cannot find autoloader. Run 'composer install' first.
> 
> I did run "composer install" again and "composer horde-reconfigure", but 
> it made no difference.

Okay, I tweaked vendor/horde/hashtable/bin/horde-redis-tester as follows:

--- horde-redis-tester.orig     2026-05-21 16:53:11.059446974 -0600
+++ horde-redis-tester  2026-05-21 16:53:27.309737515 -0600
@@ -16,7 +16,7 @@
   * did not receive this file, see http://www.horde.org/licenses/lgpl21.
   */

-foreach ([__DIR__ . '/../vendor/autoload.php', __DIR__ . 
'/../../../vendor/autoload.php'] as $autoloader) {
+foreach ([__DIR__ . '/../vendor/autoload.php', __DIR__ . 
'/../../../autoload.php'] as $autoloader) {
      if (file_exists($autoloader)) {
          require_once $autoloader;
          break;

Now it runs:

# sudo -u apache ./vendor/bin/horde-redis-tester -c 
vendor/horde/horde/config/conf.php

Horde Redis Diagnostic
----------------------
Host:     edm-cmfe01:26379 (TLS: no)
Prefix:   hht_
Database: 0

[INFO]     Driver           Available: predis (composer) | Using: predis
[OK]       Connection       Connected to Redis 5.0.3 via predis
[SKIP]     AUTH             No credentials provided
[SKIP]     SELECT           Using default database 0
[WARNING]  COMMAND INFO     COMMAND INFO not available — cannot 
introspect commands
                             ERR unknown command `COMMAND`, with args 
beginning with: `INFO`, `GET`, `SET`, `MGET`, `DEL`, `SETEX`, `KEYS`,
[ERROR]    SET              Cannot write to Redis
                             ERR unknown command `SET`, with args 
beginning with: `hht___diag_test`, `horde_diag_923ccbf4`,

Summary: 1 OK, 1 WARNING, 1 ERROR
[ ERROR! ] Redis connection has critical errors. Horde HashTable will 
not function.

If I run without referencing the configuration file:

# sudo -u apache ./vendor/bin/horde-redis-tester

Horde Redis Diagnostic
----------------------
Host:     127.0.0.1:6379 (TLS: no)
Prefix:   hht_
Database: 0

[INFO]     Driver           Available: predis (composer) | Using: predis
[OK]       Connection       Connected to Redis 5.0.3 via predis
[SKIP]     AUTH             No credentials provided
[SKIP]     SELECT           Using default database 0
[OK]       COMMAND INFO     GET: available, SET: available, MGET: 
available, DEL: available, SETEX: available, KEYS: available
[OK]       SET              Wrote test key hht___diag_test
[OK]       GET              Read back matches written value
[OK]       MGET             MGET works — multi-key retrieval available
[OK]       DEL              Cleaned up test key
[INFO]     Key scan         Found 28018 keys with prefix hht_

Summary: 6 OK, 0 WARNING, 0 ERROR
[   OK   ] All tests passed. Redis is fully functional for Horde.

This seems consistent with my suspicion that the new library isn't 
handling the redis-sentinel setup properly.

Here are all the hashtable configuration parameters from conf.php:

$conf['hashtable']['params']['hostspec'] = array('edm-cmfe01', 
'edm-cmfe02', 'edm-webapps01', 'edm-webapps02');
$conf['hashtable']['params']['port'] = array('26379', '26379', '26379', 
'26379');
$conf['hashtable']['params']['service'] = 'mymaster';
$conf['hashtable']['params']['replication'] = 'sentinel';
$conf['hashtable']['params']['protocol'] = 'tcp';
$conf['hashtable']['params']['persistent'] = true;
$conf['hashtable']['driver'] = 'Predis';


-- 
Nels Lindquist
nlindq at maei.ca