-
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.
-
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…
-
ONVIF integration failing with “Couldn’t connect to camera x, please verify that the credentials are correct. Error: Invalid data”
A few weeks ago I noticed that I was unable to view one of my CCTV cameras from within Home Assistant. After some investigation on the ONVIF integration I noticed the below error: ONVIF integration failing with "Couldn't connect to camera x, please verify that the credentials are correct. Error: Invalid data" I checked the credentials set for the camera and confirmed that the credentials were not the issue. After some research I found this github issue which pointed me to NTP. I then logged into the camera itself and enabled NTP as per the picture below. I then refreshed the integration in Home Assistant and the integration managed to…
-
The Active Directory schema isn’t up-to-date, and this user account isn’t a member of the ‘Schema Admins’ and/or ‘Enterprise Admins’ groups.
I am busy installing Exchange 2016 in a test environment and received the below error when running Setup.exe /IAcceptExchangeServerLicenseTerms_DiagnosticDataON /PrepareSchema when trying to extend the domain schema. “The Active Directory schema isn’t up-to-date, and this user account isn’t a member of the ‘Schema Admins’ and/or ‘Enterprise Admins’ groups.” Thing is, my account is part of the Schema Admins and Enterprise Admins group. I then found the solution from this post (thanks Andy!) In short, open the group membership tab on your account in Active Directory Users and Computers and then check which group is set to default, then click on Schema Admins and click on Set Primary Group to make…
-
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.…
-
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…
-
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:
-
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:
-
How to change a pool name in TrueNas
Today I installed and started setting up TrueNas as a backup for my home server. As per usual, being eager to get things done and to start playing I found that I’d like to change the pool names of my pools after I have set them up. Thanks to danb35 on the TrueNas forums for providing the short and sweet answer on how to change the pool name in this post on the forums. I successfully change the pool names and below are a step by step on how I did it using the above posts instructions: Login to your TrueNas Click on Storage Click on Pools Click on the…
-
This board requires newer software error when installing MotionEyeOS on Raspberry Pi 4
I am currently testing MotionEyeOS on my test Raspberry Pi 4. I received an error “This board requires newer software” and the board goes into a reboot loop as per the below screenshot after I flashed the SD card with MotionEyeOS version motioneyeos-raspberrypi4-20200606 After some digging I found this post where user starbasessd pointed to the solution of installing the dev version (dev20201026). I downloaded and flashed the Dev version and successfully booted into MotionEyeOS
