Workaround for tracker-miner-f high CPU utilization

High CPU utilization
Workaround for tracker causing high CPU utilization

One fine day I heard a laptop of mine making a sustained noise. I thought immediately of high CPU utilization. My intuition was right.

The issue was happening in Debian 11, running the Linux kernel 5.10.0-17-686-pae. Yeah, you’re right, it’s an i686 still functional machine. The issue began suddenly, but once it started remained happening for hours with no signs to stop.

I checked the processes using “top” and soon found the culprits. They were:

  • tracker-miner-f
  • tracker-extract
  • tracker-store

I have never seen these guys before, so, I started browsing the web for advisory… I found a good match in the thread tracker-miner-f taking over 100% of cpu. First, I learned that tracker-miner-f is Gnome’s file indexer. I had no idea about it. Anyway, I searched for any systemctl command to disable it, and found none. OK… so, I continued reading and figured out to uninstall these packages:

  • tracker-miner-fs
  • tracker-extract
  • tracker

but I noticed a removal of any of them (or all of them) would impact nautilus; so, I dismissed the idea of uninstalling them.

Then, I emptied the cache of tracker:

rm -f .cache/tracker/*

but the issue came back later.

Read more

VNC server installation on Linux Mint running the Mate desktop environment

VNC server on Linux Mint Mate desktop


The installation of a VNC server on Linux Mint -running the Mate desktop environment- can be accomplished by following this step-by-step guide. The procedure below is scoped to run the vnc server on demand, it is, only when required.


First thing anyone should do is to trigger an update of the packages from the corresponding repositories. To accomplish this, simply run:

sudo apt-get update

I would say it should be good to upgrade the versionof the installed packages by running:

Read more

NFS 4.1 support on Azure File Shares


The NFS 4.1 support on Azure File Shares -in public preview- is a fully POSIX-compliant offer ideal for workloads that require POSIX-compliant file shares, case sensitivity, or UNIX style permissions (UID/GID).

The NFS 4.1 support -in preview– on Azure File Shares is available in a number of Azure regions. You may find additional information about NFS 4.1 support on Azure File Shares in these articles “How to create an NFS share” and “Azure file share protocols“.

Installation of kubernetes on Azure virtual machines

kubernetes installation guide

This is a demo guide of how to install kubernetes master and worker nodes on Microsoft Azure standalone virtual machines.

This guide is not intended as a solution for production purposes.


This guide assumes that you have a Microsoft Azure account and that you installed the Azure CLI and you are logged in to the respective subscription in Azure.

First steps

To create a resource group:

az group create -n rg_k8sdemo --location eastus2 --tags Purpose=Education

To create a VNET:

az network vnet create \
--resource-group rg_k8sdemo \
--name vnet-k8s-101519 \
--address-prefix \
--subnet-name subnet-k8s-101519 \

To create a virtual machine (as master):

az vm create \
--location eastus2 \
--size Standard_B1ms \
--resource-group rg_k8sdemo \
--image UbuntuLTS \
--computer-name my-k8s-master-00 \
--name k8s-101519-master-00 \
--vnet-name vnet-k8s-101519 \
--subnet subnet-k8s-101519 \
--storage-sku Standard_LRS \
--ssh-key-values .ssh/ \
--tags role=master

Read more

Basic kubernetes commands to investigate an issue

There are many usage cases of kubernetes and, hence, very distinct support scenarios when it deals to supporting a kubernetes issue. In my experience, I would call the following basic kubernetes commands to investigate an issue, as the most useful -and necessary- to accompany any kubernetes issue report.

Basic kubernetes commands to investigate an issue
kubectl version
kubectl cluster-info
kubectl get nodes -o wide
kubectl get pods --all-namespaces -o wide
kubectl get deployments --all-namespaces
kubectl get svc --all-namespaces -o wide

On the same time, I would include these couple of Docker commands:

docker -v
docker ps

To speed up any kubernetes troubleshooting, I’d recommend to provide the output of those commands in TXT format, rather than taking a screenshot.

Do you have any other experienced-based basic kubernetes command you would add to this list? Please share in the comments section.