Linux

I will post anything I've learnt on Linux distributions.

  • Linux

    Unable to install all modules. See log /temp/vmware-

    I fired up VMWare Player 17 on my Pop_OS! machine today and was prompted to update it. Problem is, the update failed with the below error:     With some google fu I found this github repo which helped me run the below commands and I was able to open VMWare player again: wget https://github.com/mkubecek/vmware-host-modules/archive/workstation-17.0.2.tar.gz (replace 17.0.0 with your current version of VMWare Player tar -xzf workstation-17.0.2.tar.gz  (again replace 17.0.2 with your version) cd vmware-host-modules-workstation-17.0.2/ make sudo make install I did have to reboot my PC after the above steps to start using VMWare Player again.

  • Linux,  VMWare Workstation

    enable promiscuous mode on adapter error in VMWare Workstation

    Hi am testing out VMWare Workstation and have come across the below error when trying to run a Palo Alto OVA. “The virtual machine’s operating system has attempted to enable promiscuous mode on adapter ‘adapter_name’. This is not allowed for security reasons.” The below video shows the error and how to resolve it. If you don’t want to watch the video then please find the steps below the video. Some googling brought me to the below article: https://kb.vmware.com/s/article/287 In short, on your host system and if you are the only user on it, and if you are using Linux, as I have not tested this on Windows: Open a terminal…

  • Linux

    Frigate won’t start [Errno 111] Connection refused

    I updated my Debian server and noticed that Frigate won’t start up. My Frigate NVR is running on a Docker container and checking the logs I found that predominantly the error [Errno 111] Connection refused popped up. I also received an error about unable to connect to MQTT and then realised that I need to check MQTT. I am using Home Assistant as my MQTT broker and found that after updating Home Assistant the MQTT service did not start and was set to not start at boot. I managed to run and connect to Frigate after the MQTT service on Home Assistant was started and set to start at boot.…

  • Linux,  Virtual Box

    Installing Virtualbox Guest Additions on Debian 11

    I have been working with Debian 11 and running docker on it to host a few applications at home. As per best practice, I setup a virtual machine to test configs and updates first before deploying it to my production infrastructure. In this article I will show you how to install the Virtual Box Guest Additions on a Debian 11 virtual machine. The Virtual Box Guest Additions makes features such as copying and pasting between the host OS and virtual machine as well as running the virtual machine in full screen. This article has a good write up on what the Guest Additions provide you. I used this article as…

  • Linux

    You must specify packages by their own names error in dpkg when trying to remove an installed deb package

    I tried to remove an installed deb package using dpkg -P the_deb_name but received the error “you must specify packages by their own names, not by quoting the names of the files they come in“ Follow the below steps to correctly uninstall an application (deb package) that you installed using dpkg or eddy: get the correct name of the package: dpkg –get-selections | grep part_of_the_name Remove the application: sudo dpkg -P application_name_as_per_above_output (-P removes the package and config files) Below is a video showing the steps:  

  • Linux

    anydesk error while loading shared libraries libpangox-1.0.so.0

    You receive the error “error while loading shared libraries libpangox-1.0.so.0” when trying to run anydesk on an Ubuntu 22.04 based distro. To resolve the issue run the below few steps as found on this forum post: Open your terminal. Paste: wget http://ftp.us.debian.org/debian/pool/main/p/pangox-compat/libpangox-1.0-0_0.0.2-5.1_amd64.deb (you might need to add sudo to the start of the line if you get access denied) Install the package: sudo apt install ./libpangox-1.0-0_0.0.2-5.1_amd64.deb Now open anydesk by just typing anydesk in your terminal or launching it from your applications menu. The below video shows you the steps:

  • Linux,  Virtual Box

    Kernel driver not installed (rc=-1908) and modprobe vboxdrv

    I created a new VM in Virtualbox on my Pop_OS! machine to install Rocky Linux but received the below error when trying to start the virtual machine:             A quick search on the internet took me to the solution in this post. Thanks to Ali Razmdideh for the answer. I’m posting the steps here in case I need to find it again quickly. From terminal: sudo apt update sudo apt install –reinstall linux-headers-$(uname -r) virtualbox-dkms dkms sudo modprobe vboxdrv I did not reboot and managed to start the virtual server.

  • Linux,  Ubuntu

    ESET NOD32 for Linux needs the following packages to install: libc6-i386, /lib/ld-linux.so.2

    I tried to install ESET Antivirus on one of my machines and received an error stating: “ESET NOD32 for Linux needs the following packages to install: libc6-i386, /lib/ld-linux.so.2“ I had to install libc6 but just running an apt install libc6 showed that I already had libc6 installed. After some head scratching I noticed the -i376 (doh!) and installed the missing dependency using: sudo apt install libc6-i386 which resolved the issue and I was able to install ESET Antivirus.

  • Linux

    end Kernel panic – not syncing: VFS: Unable to mount root fs on unknown block

    Yesterday I booted up Kali Linux on my laptop only to find the error “end Kernel panic – not syncing: VFS: Unable to mount root fs on unknown block” after selecting the latest kernel. I rebooted, chose “Advanced Options for Kali GNU/Linux” as per below, then chose an older kernel and managed to boot in to Kali Linux.                             To resolve the issue I had to run the below steps to list and delete the oldest kernel installed. In the end, the cause of the error was that boot did not have enough disk space left thus…

  • CentOS,  Linux

    Unable to browse samba shares when internet connection is down

    We’ve been having a lot of outages on our internet connection and I noticed that we are unable to browse the samba shares on our CentOS 7 server. After some searching on the internet I saw a few comments around adding the server’s host name and IP in it’s own hosts file. I proceeded to open /hosts/etc and added the IP and server name to the hosts file. Sure enough I could now browse my samba shares on the server with our internet being down.