create a virtual machine 1G Ram - 40G HHD, install win 7 on a partition occupied 20G, and leave the remaining 20G in install Ubuntu.
So that when you boot the virtual machine it will run both windows and ubuntu
Related
In the Memgraph official documentation it says "Install MemgraphDB using the latest Memgraph Ubuntu package and by running the following command in the Ubuntu terminal.". On the download page there are three Ubuntu versions, 18.04, 20.04, and 22.04. I've downloaded the right .deb file. From Memgraph part, everything works ok.
I get stuck when trying to install Ubuntu 22.04 in WSL. I don't see it. I have Windows 11 professional. Does this mean that Ubuntu 22.04 is perhaps not available in my Region?
PS C:\Users\Gai> wsl --list --online
The following is a list of valid distributions that can be installed.
Install using 'wsl.exe --install <Distro>'.
NAME FRIENDLY NAME
Ubuntu Ubuntu
Debian Debian GNU/Linux
kali-linux Kali Linux Rolling
SLES-12 SUSE Linux Enterprise Server v12
SLES-15 SUSE Linux Enterprise Server v15
Ubuntu-18.04 Ubuntu 18.04 LTS
Ubuntu-20.04 Ubuntu 20.04 LTS
OracleLinux_8_5 Oracle Linux 8.5
OracleLinux_7_9 Oracle Linux 7.9
You can install Ubuntu 22.04 from the Microsoft Store.
Ubuntu 22.04.5 LTS on Microsoft Store
You can read more on the general availabilty of WSL in the Microsoft Store here.
I want to give a try to the create-cluster script given in the redis documentation.
I did as the documentation indicates:
./create-cluster start
./create-cluster create
After the ./create-cluster create command, my computer CPU is going indefinitely to 100% of usage.
./create-cluster stop
When stopping the cluster instances, the CPU usage is back to normal usage.
What is going on? What can I do in the configuration to solve this?
My operating system is a Windows 10 version 21H2.
I installed the WSL Ubuntu 20.04 and run redis on it.
I installed the apt-get redis-server package.
didi#CHOUCHOU:~$ redis-server --version
Redis server v=6.2.6 sha=00000000:0 malloc=jemalloc-5.1.0 bits=64 build=9c9e426e2f96cc51
didi#CHOUCHOU:~$ redis-cli --version
redis-cli 6.2.6
I downloaded from github the create-cluster script.
https://raw.githubusercontent.com/redis/redis/6.2/utils/create-cluster/create-cluster
I have spun a Redhat linux machine in aws,but struggling to install apt-get ,here is uname -a
Linux ip-172-31-69-100.ec2.internal 3.10.0-957.el7.x86_64 #1 SMP Thu Oct 4 20:48:51 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Could you provide help just to let me know how to get apt-get working in Redhat linux aws machine
actually my search was how to make sudo snap conjure-up --classic working in Amazon aws Linux machine,I was trying to run
sudo snap conjure-up --classic working in Amazon aws Linux machine,but i was getting message as snap not found sometimes apt-get not found,my quest was then how do i get snap in amazon linux machine?
Resolution:-one of my colleague explained"Unfortunately, conjure-up has been developed by Canonical, the creator of Ubuntu and is only tested on Ubuntu Linux machines. It most likely won't work on other OS'es. You'll need to spin up an Ubuntu machine to use conjure-up."
I am running RabbitMQ on Ubuntu 16.04 under the Windows 10 "windows on linux" installation.
I cannot connect using rabbitmqctl. I used su to run as root and also tried to run it under my username with sudo, but everytime I run the command I get:
Diagnostic log
attempted to contact: ['rabbit#SJDEV-JWRIGHT3']
rabbit#SJDEV-JWRIGHT3:
* connected to epmd (port 4369) on SJDEV-JWRIGHT3
* epmd reports node 'rabbit' running on port 25672
* TCP connection succeeded but Erlang distribution failed
* suggestion: hostname mismatch?
* suggestion: is the cookie set correctly?
* suggestion: is the Erlang distribution using TLS?
current node details:
- node name: 'rabbitmq-cli-133#SJDEV-JWRIGHT3'
- home dir: /var/lib/rabbitmq
- cookie hash: iLmkDqwKzDZPxk8ynhqsVw==
I have uninstall and re-installed both Erlang and RabbitMQ. I changed the host names as suggested by someone else, and I still cannot figure out this problem.
I have rebooted the system, and when I tried to run rabbitmq-server restart and got:
ERROR: node with name "rabbit" already running on "SJDEV-[NODE]"
I am new to linux and have been digging in to this for a week and hit my breaking point.
Okay I found out the problem in a round about way. I am running this version of Ubuntu on the Windows Subsystem for Linux application on my windows 10 machine. My windows machine is already running rabbitmq and it happens to be on the same node as the node that I was trying to access using the rabbitmqctl. So there must be a correlation between the Ubuntu and windows system that shows rabbitmq already running. I may try this on a VM and see if I can get a clean break and try again.
Thanks.
I had this issue today.
My config is below:
Have a rabbitmq-server on Windows 10 OS
Have a rabbitmq-server on Ubuntu which was installed on Windows 10 OS (Ubuntu 18.04 app from Windows store)
Now below error makes sense:
ERROR: node with name "rabbit" already running on "MyComputerNamehere"
Another hint was Windows OS firewall has allowed both of them, in other words, they are running on same computer with name (ex: MyComputerNamehere).
Though I know the issue, I didn't fix it by removing rabbitmq-server from Windows 10, as I wanted Windows 10 rabbitmq-server, so gave up on Ubuntu on Windows 10.
Hope this explanation helps someone.
I am using VMWare Workstation Desktop to test new zendserver.
Install CentOS 7 minimum install.
CENTOS Linux release 7.2.1511 (core)
I have disabled SEinux. reboot.
Install ZendServer-8.5.2-update1
Everything works ok. I can reach http://192.168.1.37:10081/ZendServer/Dashboard/
but after reboot zend server don't responded.
If I manually start zend server - everything goes well.
What's wrong?
I have received answer from zend server support:
The problem is caused by a bug in RHEL/CentOS 7.2 systemd (bug was already fixed but have not been shipped yet).
Meanwhile, you can use the following workaround (as root):
rm -f /etc/init.d/zend-server
cp -p /usr/local/zend/bin/zendctl.sh /etc/init.d/zend-server