Error connecting to pika with redis protocol
Closed this issue · 19 comments
Hello,
I have p3x installed in docker container and one Pika in other docker container (Pika uses redis protocol).
I have configured the connection, and If I test it from the p3x UI, I get "Redis connection succesfully"
But If I click in Connect, I get this error:
Cannot read properties of undefined (reading 'trim')
I'm checking the logs and I can see this:
I have tried also installing redis-cli in the p3x container and I can connect to the pika (redis) instance and get the keys.
i have not time to fix with Pika, in Redis it works.
try sending your configuration without sending your password
Thanks, now I have just this:
But I have tried creating it directly from the UI but I get the same error. This is the config directly from the UI
The connection is sucessfully
But I get the error I said in the first post
that is not the eror, the code is here:
try {
//commands = await redis.call('command2')
commands = await redis.command()
console.info(options.payload.connection.name, 'instance command listing is available') // , JSON.stringify(commands))
} catch(e) {
console.warn(options,payload.connection.name, 'instance command listing is not available, not all redis instances are not available command listing', e)
}try the error get on the browser log where the trim error is.
but it is prossible this error is on the error side, you have to check both where this trim error is.
baseides, try to generate the configuration in the gui, then apply in your docker environment.
In the browser I only see this:
I don't see errors, and the response of this traces are:
ok
1
2
ok
something like that:
try the console error and the server as well.
baseides, try to generate the configuration in the gui, then apply in your docker environment.
I have already done, I have two configs, one done by from the browser and I get the same error
but there must be handled in the server side or the browser so there should be a stack trace. either side.
see the log of the p3x-redis-ui log on the docker and the browser not the net tab, but the console tab.
This is the console view:
In the docker log I can see now the Connection is closed:
But before, when I see the command trace I sent you, I dont see any error
it connects, but it disconnects right away... sorry.
i suppose the protocol is same as pika, but the way it works is different.
Ok thank yo uso much
it is working, but i suppose there will be errors because of this, i will let you know when it is released, it is building right now.
Thank you! I'm goint to try it