Cannot get it to work

[dubcanada]

Hello,

I have a Amazon Linux 2 server that I installed and setup and it appears correct. I am using the latest 0.6.5 centos 7. I am just trying to ping a local server and I keep getting false. I can do the exact same in PhpRedis and it works fine.

My test php file

<?php

$relay = new \Relay\Relay('127.0.0.1',6379);
//$relay = new Redis(['host'=>'127.0.0.1','port'=>6379]);

var_dump($relay->ping('hello'));

PhpRedis version works, Relay says false

My logging is turned on and I get

[1687182716.150184 DBG 29630] shmalloc.c:202 Allocated 33554432 byte pool (head: 7fd4ed217000, curr: 7fd4ed218020, alignment: 16)
[1687182716.150218 DBG 29630] cache.c:43 EPOCH[malloc]: 7fd4ed21efa0 (5303 bytes)
[1687182716.150236 NOT 29630] relay.c:2256 STARTUP - Relay has started...
[1687182716.154573 DBG 29630] relay.c:2911 RINIT - Requests (1 total, 1 active, 1 max)
[1687182716.154674 DBG 29630] relay.c:2878 HTTP_HOST - Failed to find HTTP_HOST or it's not a string.
[1687182716.154679 DBG 29630] relay.c:2854 PLINK - Uninstalling handlers for 0 links
[1687182716.154777 DBG 29630] cache.c:1116 PLINK - No free link to 'tcp://[default@127.0.0.1:6379?cache=1](http://default@127.0.0.1:6379/?cache=1)'
[1687182716.155156 NOT 29630] relay.c:3422 CRON TASKS - GC(keys): 1; GC(msg): 0, EVICTED: 0 keys
[1687182716.155162 NOT 29630] relay.c:3429 CRON  PROC - hits/miss: 0/0 (0.00%), oom: 0, errors: 0
[1687182716.155165 NOT 29630] relay.c:3380 CRON STATS - Memory 54400/33554432 bytes (0.16%)
[1687182716.155170 DBG 29630] relay.c:2785 PLINK - installing handlers for 0 links
[1687182716.155173 DBG 29630] relay.c:3003 RSHUTDOWN - Finished request
[1687182716.155232 NOT 29630] relay.c:2279 Relay is shutting down, bye bye

My so LLD result is

ldd /usr/lib64/php/modules/relay.so
ldd: warning: you do not have execution permission for `/usr/lib64/php/modules/relay.so'
        linux-vdso.so.1 (0x00007ffeabbf8000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f4045e28000)
        libssl.so.1.1 => /lib64/libssl.so.1.1 (0x00007f4045b9c000)
        libcrypto.so.1.1 => /lib64/libcrypto.so.1.1 (0x00007f40456c5000)
        libzstd.so.1 => /lib64/libzstd.so.1 (0x00007f4045414000)
        liblz4.so.1 => /lib64/liblz4.so.1 (0x00007f4045200000)
        libanl.so.1 => /lib64/libanl.so.1 (0x00007f4044ffc000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f4044c4f000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f40462fc000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f4044a3a000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f4044836000)

Not sure what is going up, PHP says it's enabled and correct. I have

sed -i "s/00000000-0000-0000-0000-000000000000/$(cat /proc/sys/kernel/random/uuid)/" /tmp/relay/relay-pkg.so

Injected

Any ideas what is wrong or what I am missing?

[tillkruss]

I'm guessing because Redis Server isn't reachable?

Try setting this:

$relay->setOption(Relay::OPT_THROW_ON_ERROR, true);

[tillkruss]

The connection in our AL2 workflow is working: https://github.com/cachewerk/relay/actions/runs/5320570219/jobs/9634522593

[dubcanada]

That gave me the following error

PHP Fatal error:  Uncaught Relay\Exception: ERR unknown command 'HELLO' (RELAY_ERR_REDIS; commands.c:7344) in test.php:7
Stack trace:
#0 test.php(7): Relay\Relay->ping('hello')
#1 {main}
  thrown in test.php on line

[dubcanada]

I think my problem is I am using Redis 5.4 I will try 6.

[dubcanada]

yup that was the issue, it doesn't work under 6. We can close this.

I will say it does silently fail though.

[tillkruss]

@michael-grunder: Can we throw an exception when Relay is connected to a <6.0 instance?

[michael-grunder]

Sure. I can add this to the "always throw an exception" list.

[michael-grunder]

Update: I double-checked this and it already appears to throw this exception. I don't to call setoption.

@dubcanada How do you mean it fails silently?

[dubcanada]

Oh why yes I was I thought it was 5. My bad.

…

On Mon, Jun 26, 2023 at 4:48 PM Michael Grunder ***@***.***> wrote: @dubcanada <https://github.com/dubcanada> Were you possibly using Redis 4.x.x? I think I see how this could happen with a version of Redis that old. Basically, Relay intercepts the specific HELLO error message to present a more helpful exception message. Redis switched from single-quoting the command name to using back-ticks in 5.x.x ERR unknown command 'HELLO' vs ERR unknown command `HELLO` — Reply to this email directly, view it on GitHub <#81 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA5MBMPPYM53PXXHICDBG3XNHRRTANCNFSM6AAAAAAZL7TJDQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[michael-grunder]

Fix is merged. Thanks again for the report!