System has not been booted with systemd as init system (PID 1) Can't operate | How to Fix 100% wsl

[Fixed] System has not been booted with systemd as init
System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down
Systemd support is now available in WSL!
devblogs.microsoft.com/comman...
Learn how to fix the error 'System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down' quickly and effectively. Follow step-by-step instructions to troubleshoot and resolve this issue on your Linux system. Perfect for beginners and advanced users alike! Watch now for a seamless solution to get your system running smoothly again.
1. What is systemd?
Systemd is a suite of basic building blocks for a Linux system. It provides a system and service manager that runs as PID 1 and starts the rest of the system.
2. How can you get systemd on your machine?
To get started, you will need to do these two things: - Ensure you are running the right version of WSL: Version 0.67.6 and above - Set the systemd flag set in your WSL distro settings.
3. Set the systemd flag set in your WSL distro settings
You will need to edit the wsl.conf file to ensure systemd starts up on boot.
Mastering Windows Subsystem for Linux: Run Linux on Windows without virtual machine. WSL2 tutorial :
• Mastering Windows Subs...
#wsl #linux #windows11 #windows10 #windows #redhat #ubuntu #centos #centos8 #wsl2 #windowstutorials #terminal

[@saitan_rider]

Hii

[@ismailchiba3513]

im using wsl to connect ubuntu 22.04 to vs code on my windows 10 even when a change the /etc/wsl.conf file i keep getting the same error could help me please and thank you for your effort

[@LinuxTechHub]

Hi, kindly check if you are running the right version of WSL: Version 0.67.6 and above required. 1. Check your version number by running: wsl --version on CMD or PowerShell 2. To check for any WSL updates available run: wsl --update on CMD or PowerShell Add these lines to the /etc/wsl.conf [boot] systemd=true Then exit your Ubuntu distro and run, wsl.exe --shutdown from PowerShell. Then run "wsl -d Ubuntu" to restart your ubuntu distro.

[@ibrahimmuhammad4030]

PLs help E492: Not an editor command: wql Press ENTER or type command to continue

[@LinuxTechHub]

Hi, To save the vi editor first press Esc button on keyboard. Then type :wq! All in small letters.

[@LinuxTechHub]

To properly save and exit Vi editor, ensure you are in command mode (press Esc on your keyboard), then type :wq! and press Enter. This will save your changes and exit Vim without errors. If you mistakenly typed :wql instead of :wq!, Vi doesn't recognize it as a valid command (E492 error) and prompts you to continue or enter a valid command.

[@ibrahimmuhammad4030]

Thanks man ❤

[@shahanawazkhan8745]

After writing [Boot] systemd=true, I can't write this term: wql, I can't write it smoothly even by pressing the Esc button on the keyboard.

[@LinuxTechHub]

Hi, If you are trying to edit the wsl.conf file as a normal user then you need sudo privilege. Type: sudo vi /etc/wsl.conf [boot] systemd = true then press Esc key on your keyboard, then type :wq! (all in lower case) and press Enter. This will save your changes and exit Vim without errors.

[@saitan_rider]

I am not able to do it.😢 Please 🙏 help me 🙏

[@LinuxTechHub]

Hi, could you please tell me the error you are getting. Also pls check if wsl.conf file has been properly edited as mentioned in the video.

[@ibrahimmuhammad4030]

pls help me again service apache2 start Starting Apache httpd web server: apache2AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using ::1. Set the 'ServerName' directive globally to suppress this message (13)Permission denied: AH00072: make_sock: could not bind to address [::]:80 (13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down AH00015: Unable to open lo

[@LinuxTechHub]

Hi, Ensure you are starting Apache with root privileges. Use sudo before the command: sudo service apache2 start Edit the Apache configuration file & check if it helps: sudo nano /etc/apache2/apache2.conf ServerName your_domain.com (replace your_domain.com with your actual domain)

[@ibrahimmuhammad4030]

Pls how can i contact u pls Include generic snippets of statements IncludeOptional conf-enabled/*.conf # Include the virtual host configurations: IncludeOptional sites-enabled/*.conf # vim: syntax=apache ts=4 sw=4 sts=4 sr noet ServerName 127.0.0.1 Look where i put it

[@ibrahimmuhammad4030]

about the domain what is that Is it same as my server name

[@ibrahimmuhammad4030]

Look what it showed me ┌──(kali㉿localhost)-[~] └─$ sudo service apache2 start Starting Apache httpd web server: apache2/usr/sbin/apache2ctl: 102: ulimit: error setting limit (Operation not permitted) Setting ulimit failed. See README.Debian for more information.