Redis, almost no commands work properly, get Error Unknown command for KNOWN COMMANDS - redis

Trying to make a SIMPLE backup of our Redis Database that is on Heroku for a Ruby on Rails command, I connect using redis-cli just fine, I can type help save and it says it is a command, but when I try to run save it gives me a lame error that says:
ec2-34-231-26-8.compute-1.amazonaws.com:19099> save
(error) ERR unknown command `save`, with args beginning with:
ec2-34-231-26-8.compute-1.amazonaws.com:19099> bgsave
(error) ERR unknown command `bgsave`, with args beginning with:
ec2-34-231-26-8.compute-1.amazonaws.com:19099>
Yet if I ask for help on these commands they do in fact exist:
ec2-34-231-26-8.compute-1.amazonaws.com:19099> help save
SAVE -
summary: Synchronously save the dataset to disk
since: 1.0.0
group: server
ec2-34-231-26-8.compute-1.amazonaws.com:19099> help bgsave
BGSAVE -
summary: Asynchronously save the dataset to disk
since: 1.0.0
group: server
ec2-34-231-26-8.compute-1.amazonaws.com:19099>
Does anyone know why Redis doesn't work properly?
It is the Heroku Hobby Dev version and I am connecting to it via Windows which is not giving me ANY trouble at all other than the Redis Server not working properly. On another instance I get an even stranger error that says Save is not allowed?
I have searched for hours and there appears to be NOTHING on this subject at all which is very confusing to me. A lot of the commands listed on redis.io return that same stupid error that the command doesn't exist when the help clearly states that it DOES exist.
Any help would be appreciated..

I hope this may help someone, In my case was that there was a rename in the configuration
check your redis.config file
I had
rename-command SAVE "SV"
now, type your rename command and that's it
127.0.0.1:6380> SV
OK

Related

redis.exceptions.ResponseError: MISCONF Redis is configured to save RDB snapshots

I'm with this problem when I try to save to redis. Introducing the message below.
MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Red
The redis log file displays this:
Background saving started by pid 73
Write error saving DB on disk: Function not implemented
Has anyone ever experienced this?
I found the answer. You need to wsl 2 To find out the version run below command in PowerShell
wsl -l -v
If it is version 1, run the command below and open ubuntu again
wsl --set-version 2
More information: https://learn.microsoft.com/en-us/windows/wsl/install

Can't connect VS Code to Linux machine for remote development

I am getting this error on VS Code and have no clue why it fails
[15:14:59.543] Log Level: 2
[15:14:59.555] remote-ssh#0.51.0
[15:14:59.555] win32 x64
[15:14:59.560] SSH Resolver called for "ssh-remote+xx.xx.xx.xx", attempt 1
[15:14:59.561] SSH Resolver called for host: xx.xx.xx.xx
[15:14:59.561] Setting up SSH remote "xx.xx.xx.xx"
[15:14:59.621] Using commit id "0ba0ca52957102ca3527cf479571617f0de6ed50" and quality "stable" for server
[15:14:59.624] Install and start server if needed
[15:15:01.964] getPlatformForHost was canceled
[15:15:01.965] Resolver error: Connecting was canceled
[15:15:01.973] ------
Add one key in your settings.json as below. Please remember to replace the $remote_server_name to yours.
"remote.SSH.remotePlatform": {
"$remote_server_name": "linux"
}
Menu: File->Preference->Settings
Or click the icon to open settings.json:
In dialog box where you have typed user#host type/select Linux/Windows/etc. depends what you are using, then type/select Continue, then type password for remote session.
For those getting this error on Windows: Check if you have multiple ssh clients installed.
How I solved it was by adding my ssh-configuration to ALL ssh-config files.
In my case I had one in
C:\Users\USER_NAME.ssh\config (this is the one that the remote extension used to give me connection options)
and another in C:\Program Data\ssh\ssh-config
After adding my ssh-config setting to both I got the prompt to select virtual hosts' OS. Tried editing the settings.json file directly, but I think it gets confused because of the multiple ssh-configurations.
P.S.
Tested it for both private key and password enabled connections and it work with either.
I got a similar problem, but the error logs were bigger. Before that, I deleted the python and reinstalled it. Perhaps this led to the problem. Just reinstalled "Remote -SSH" extension in vscode and it worked for me.
In my case there were two files that look like
vscode-remote-lock.<user>.<xxx>
vscode-remote-lock.<user>.<xxx>.target
where was my remote user name and xxx the VS Code Remote Server build hash.
These two files on the remote server in the folder.
/run/user/1000/
I deleted both files and then VS Code came up right away. I have encountered this a few times now. VS Code Remote Server install is not very robust. I use it on about 7 remote machines and every once in a while something goes awry and it cannot recover from simple errors and gets stuck in installation loops.
This trick only works if there is a valid ~/.vscode-server on the remote machine with a hash that matches your local VS Code installation.
If you got here because you were trying to install VS Code in the first place and for whatever reason VS Code had issues with the remote installation, I highly recommend installing it manually by downloading and extracting the tar file to the remote machine directly.
I have tried playing with the setting "Use remote.SSH: Use Flock" and other tricks posted on StackOverflow but none of these work for me whenever I have remote installation issues. I cannot figure out why on some machines, a smooth remote installation is not possible. Even when all of my ssh keys and remote ids have been copied and tested from both the Windows command line and inside a WSL Ubuntu instance.
If VS Code Remote Server installation had slightly better error logic and better error messages none of us would be wasting hours doing this simple task.
I was getting the exact same error as the original poster received and yet none of the other answers were my issue.

ERROR: invalid token 'verify' after the command "rladmin help verify "

I have installed the redis on my VM. And then I run the commands
[root#vm001jeguan ~]# rladmin help verify
it shows the following error:
[root#dltasvm001jeguan ~]# rladmin help verify
ERROR: invalid token 'verify'
Run the following command it works well
[root#vm001jeguan ~]# rladmin status
Does anyone have met such issue? Thank you very much.
You are probably trying to run a new rladmin command on an older version of RLEC.
For further support please contact us at support#redislabs.com
Verify that you are using correct commands.
You can use rladmin then press "enter" and get an easier view.
Also use 'tab' for command guessing will help you.
[Example from 4.2.1-30 RLEC]
[root#ip-10-0-0-65 ~]# rladmin
RedisLabs Admin CLI
Version 4.2.1-30.rhel6
Use <?> for help at any time, <TAB> for command completion.
rladmin>
rladmin>
cluster Cluster management commands
exit Exit admin shell
failover Fail-over master to slave
help Show available commands, or use help <command> for a specific command
info Show information about tunable parameters
migrate Migrate elements between nodes
node Node management commands
status Show status information
tune Tune system parameters
upgrade Upgrade database version
rladmin>

Redis Server doesn't start or do anything - Redis-64 on Windows

I'm following these steps outlines on this link, however when I try to start the server nothing happens nor can I connect to anything from the client. Does anyone know how to run this?
when I try from a command prompt instead of double clicking the redis-server.exe I get this message
[11868] 23 Jul 11:58:26.325 # QForkMasterInit: system error caught. error code=0
x000005af, message=VirtualAllocEx failed.: unknown error
http://bartwullems.blogspot.ca/2013/07/unofficial-redis-for-windows.html
The easiest way to install Redis is through NuGet:
Open Visual Studio
Create an empty solution so that NuGet knows where to put the packages
Go the Package Manager Console: Tools –> Library Package Manager –>Package Manager Console
Type Install-Package Redis-64
image
Go to the Packages folder and browse to the Tools folder. Here you’ll find the Redis-server.exe. Double click on it to start it.
Redis is ready to use and start’s listening on a specific port(6379 in
my case)
image
Let’s open up a client and try to put a value into Redis. Start Redis-cli.exe. It already connects to the same port by default.
image
Add a value by executing following command:
image
Read the value again:
image
Try to run with redis-server --maxheap 4000000
Miguel is correct, but it is not that simple. To start redis-server either as a service or from the command prompt, the amount of available RAM and disk space must be sufficient for Redis to run as configured.
Now, if no configuration file is specified when running Redis, it will use the default configuration values. All of this is documented in the redis.windows.conf file as well as in the document "Redis on Windows.docx" (both deployed with the redis installation).
In my experience, errors when starting Redis usually come from lack of available resources (RAM or disk space) or some incorrect configuration of maxhead or maxmemory parameters.
To troubleshoot this kind of behavior, check your system's available resources and try running redis-server from the command line varying the parameters maxmemory, maxheap, and/or heapdir. The loglevel parameter set to verbose might also help diagnosing the issue.
Regards

Cannot get rid of following error "pg_dump: aborting because of server version mismatch" on Lion OSX

I am trying to download the dump of a database on Heroku in the following way:
pg_dump dc6psqngs8h580 -h url_address -U user_name> db.sql
but I am getting this error all the time:
pg_dump: server version: 9.2.4; pg_dump version: 9.1.5
pg_dump: aborting because of server version mismatch
I found topics with this error here on SO, but none of them helped me out with this issue.
I added:
PATH="/Applications/Postgres.app/Contents/MacOS/bin:$PATH"
into ~/.profile, also I added
export PATH=/Applications/Postgres.app/Contents/MacOS/bin:$PATH
into ~/.bash_profile, but none of these helped me to successfully download the dump.
Where can be yet the problem and how to fix it?
Thank you very much
Install PostgreSQL 9.2.x whether by homebrew, from source, or some other means.
Basically you can dump an older server with a newer version of the dump file, but not the other way around. This exists to ensure that newer features of the db are not ignored in the dump and there are no command line switches to get around the error.