If you are sure the binary/program exists, it could be that your PATH variable is broken or not set. Just do this to set most of the common paths: export PATH=$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin There's no risk to the above, because it just takes your current PATH variable and adds more to what is already existing. To make this permanent you can add this to your ~/.bashrc file........

If you are using a hypervisor to test Proxmox (eg. Vbox) then changing the video card/display adapter can fix it. For example VboxSVGA causes the issue but switching to VMSVGA fixes it. For example VboxSVGA causes the issue but switching to VMSVGA fixes it. ........

If you have swarm services and dockerd is creating a high load even with the containers just being idle, the easiest solution is to upgrade to a newer docker version. For example an identical config of 3 nodes, with Redis 5 with 30 replicas produces a load of about 1.45 in Debian 10 with Docker18.09.1 If I create the same setup on Debian 11, with Docker 20.10.5+dfsg1 then the CPU usage is low. One other difference I wondered is the kernel. In my test setup........

If you get this error in your logs: add bridge failed: Package not installed This error normally means one of two things. 1.) Is your brctl (bridge-utils) installed? On Mint/Debian check for "brctl". If it's not there do sudo apt install bridge-utils uml-utilities 2.) Is your bridge.ko (bridge kernel module loaded?). On some installs I have seen that you cannot modpro........

If you plugin your phone to your computer and enable USB File Transfer/Allow on the phone side but the contents of your phone on the computer side are empty in the file manager, you probably don't have mtp-tools.MTP or media transfer protocol is the standard protocol that most phones use to communicate over USB to the computer. Just do this to fix it and get access to your files: apt install mtp-tools After that you should be a........

If you get an error that you aren't in the sudoers file, this typically means that your user is not designated as an admin with sudo privileges. In plain English, when it comes to some OS's like Debian including 10,11 etc.., by default the user is created without special privileges which is contrary to how Ubuntu/Mint handle the secondary user. Let's check the sudoers file to see the problem.........

If you get error messages like this it is usually because /var/run/sshd does not exist. root@userbox:/# service sshd status ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enab Active: failed (Result: start-limit-hit) since Wed 2019-04-10 02:24:44 EDT; 1 Process: 511 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255)........

If you visit a site that exploits the WebRTC vulnerability including whatismyipaddress.com it may show "Local IP Address" which would be the real IP of your machine. The vulnerability works on Windows and Linux machines (contrary to false information on the web which claims it only affects Windows). The above works and happens even if you are using a proxy or VPNaccount like ProVPNAccounts.com It is easy........

If Linux Mint 17 or other has no window buttons/controls you can do the following from terminal: marco --replace& Sometimes it can be fixed if you go to your themes/appearance and choose a new one but in the case like mine where Compiz is installed but not running/working then that fix will not work and will require the marco command above. What if you can't type in a terminal Window? If you close........

If the below is happening on KVM (a very weird and scary looking error) it's probably because of Windows. This has happened countless times to me where the bootsector on Windows 7/2008 becomes corrupted easily (even by a crash or shutdown). KVM: unknown exit, hardware reason 0x80000021 kvm_run returned -22 rax 0000000000000010 rbx 0000000000000080 rcx 0000000000000000 rdx 0000000000000080 rsi 000000000025db2a rdi 000000000007db2a rsp 0000000000000200 rbp........

If you have the "(auto-read-only)" beside an arrayI have no idea why that happens but it is easy to fix. Just run "mdadm --readwrite /dev/md1" (rename md0 to the device with the problem and it will begin to resync. md1 : active (auto-read-only) raid1 sdb2[0] sda2[1] 19534976 blocks [2/2] [UU] resync=PENDING ........