I newly installed Ubuntu 19.10, and installed redis with sudo apt install redis-server(5.0.5).
And started sudo systemctl start redis.
Executed redis-cli, then I got Could not connect to Redis at 127.0.0.1:6379: Y
The last 1 charactor (Y in this case) is different each time.
I just installed with using apt and didn't change any configs.
Is there any bugs or something I missed? please help me.
I tried to install from source code (5.0.7).
It works.
Related
Having a terrible time with the raspi related problems. One of them concerning the libcamera. I have Ubuntu 22.04 64bit on my raspi and I have installed the libcamera package with the command sudo apt install libcamera_*. The problem is that whenever I run a command with libcamera it tells me command not found!!! Any solutions?!! The camera is detected and supported. Thanks in advance for your help.
I want to know if the linux VM is running on Hyper-V environment. Is there any way I can identify? Thank you !
It can be determined by installing virt-what
here is documentation
https://linux.die.net/man/1/virt-what
as an example, install on ubuntu:
sudo apt install virt-what
usage:
sudo virt-what
I am trying to install MSSQL-Server on my Ubuntu 22.04. I know that it does not currently support Ubuntu 22.04. I need to find a workaround to install the software as I don't want to downgrade.
I tried installing but it keeps giving me dependency errors. How do I solve it? Any help would be appreciated.
Unfortunately, at this time, SQL Server 2019 only works on Ubuntu 20/21. 22.04 is not supported at this time.
So either you will have to use Ubuntu 20 or, as others have stated, use Docker Containers.
You can install Docker into Ubuntu 22.04. It's a multi-step process, but it isn't that difficult.
Install Docker Engine on Ubuntu (follow the Install using the repository section)
https://docs.docker.com/engine/install/ubuntu/#set-up-the-repository
Install SQL Server Container
https://learn.microsoft.com/en-us/sql/linux/quickstart-install-connect-docker?view=sql-server-ver15&pivots=cs1-bash
That should do it.
Also, in link #2, read further below on how to connect to your docker image to run SQLCMD from within the container.
Like SQL Server 2019, you cannot install the SQLCMD tools directly into your Ubuntu 22.04 installation. But the Docker container image contains the sqlcmd tool for you to be able to connect to the database.
Or, you can use Visual Studio Code with the SQL Server (mssql) extension and it can connect to your SQL Server instance in your running Docker container.
The connection string would be:
"Server=localhost;Database=your database name;User Id=user id;Password=password"
You can leave out the Database setting if you just want to connect to the default database.
If you create any databases, you can then connect to them directly by specifying the name.
I also have same problem like this. I also tried downgrading Openssl to 1.1.1k and 1.1.1s but still not works. And finally I found this explanation
https://github.com/microsoft/msphpsql/issues/1419#issuecomment-1303626500
So, keep use OpenSSL 3.0.2 and you just need to change the SECLEVEL to 0 instead of 1 in /etc/ssl/openssl.conf
[system_default_sect]
CipherString = DEFAULT:#SECLEVEL=0
And it works, now I can connect to SQL Server using Ubuntu 22.04.
Looked at this
and it has worked for me!
So worth giving it a shot
cd /opt/mssql/lib
ls -la
sudo rm libcrypto.so libssl.so
sudo ln -s /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 libcrypto.so
sudo ln -s /usr/lib/x86_64-linux-gnu/libssl.so.1.1 libssl.1.1
If libssl is not installed, try:
sudo apt install libssl1.1
Update: I had issues connecting using libssl1.1, so I switched to 1.0 after performing the previous steps, so I also did the following:
sudo systemctl stop mssql-server
sudo systemctl edit mssql-server
Added:
[Service]
Environment="LD_LIBRARY_PATH=/opt/mssql/lib"
Then:
sudo ln -s /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 /opt/mssql/lib/libssl.so
sudo ln -s /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 /opt/mssql/lib/libcrypto.so
Then started mysql-server and things just worked fine!
I am trying to run rabbitmq server on my mac and i keep getting this error:
Starting broker...Logger - error: {removed_failing_handler,rabbit_log}
BOOT FAILED
I have tried reinstalling it several times and even logged into local host but see the same error.
Managed to fix it. Ran these commands to fully uninstall RabbitMQ (vhosts, users too).
sudo apt-get remove --auto-remove rabbitmq-server
sudo apt-get purge --auto-remove rabbitmq-server
Then after I reinstalled everything worked.
Another possibility is that you are running it on Big Sur- it keeps on giving errors to me that I didn't get previously.
Try pip3 uninstall rabbitmq-server then pip3 install rabbitmq server- that worked for me.
I followed below steps to install Redis on CentOS. But Redis 3.2.x version got downloaded, I want more recent version (i.e 4.0.11 or 5.0.x) to be downloaded.
I need steps how to upgrade the Redis current installation? I used below steps while installation
We can use yum to install EPEL:
sudo yum install epel-release
As soon as we finish installing EPEL, we can use yum once again to install Redis:
sudo yum install redis
After a few minutes this installation will be completed and then you can start the Redis service:
sudo systemctl start redis.service
There is always the chance for Redis to start on boot, all you have to do is enable it through the enable command:
sudo systemctl enable redis
If you want to check Redis`s status you should run the following:
sudo systemctl status redis.service
I have found the Remi repository keeps up with the latest binaries. While you can add them to your repos (see https://rpms.remirepo.net), you can just point yum directly at the rpm file there as well (e.g. yum install -y http://rpms.remirepo.net/enterprise/7/remi/x86_64/redis-5.0.0-1.el7.remi.x86_64.rpm).
Edit: Regarding an upgrade, I assumed you don't have any data at this point, so I would suggest a quick yum uninstall redis before installing the latest. If you really need to upgrade with data and all, you need to just be sure to preserve your persistent data files and replace them before starting the new version.