Costin Stefan

So it may happen that you have a Kubernetes or Openshift deployment and a pod does not want to start and remains in Pending state. First, let’s check the events that are causing this: [root@server ~]# k get events -n <namespace> LAST SEEN TYPE REASON OBJECT MESSAGE 31m Warning FailedScheduling <namespace>/<pod_name> 0/13 nodes are available: 10 Insufficient memory, 3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate, 4 Insufficient cpu. As we can see, the reason is FailedScheduling and the message complains about insufficient memory and insufficient cpu. ...

If you’re working on fixing an issue on a server and want to be notified as soon as this is reachable, you can run an audio alert. Below I have a list of variations of the Bell Character. Windows / PowerShell: while ($true) {if (Test-Connection -quiet 1.1.1.1) { [console]::beep() }} Windows / cmd: for /L %n in () do @ping -n 1 1.1.1.1 && echo ^G WSL2 / Bash: while true; do sudo ping -q 1.1.1.1 -w1 >/dev/null && tput bel; sleep 5; done on WSL ping needs eleventation so sudo is mandatory. ...

So I’ve tried to configure a self-hosted Roundcube container and set up an iCloud account with a custom domain address. Something like what this guy wanted to do a couple of years ago. Unfortunately, there was no tutorial available on the internet, so here I am creating one for you :) I’m using docker compose in my local selfhosted lab, so the first thing to do was to get the correct docker-compose.yml file. For this I went to the official one and I took the vars from the official docker image. However, playing with variables was a pain. The official documentation from Apple offered the correct IMAP and SMTP servers and ports. However, later I found out that for a 3rd party application you need to create a special password: https://support.apple.com/en-us/102654 ...

For today’s post I will walk you through the process of setting up a web-app testing environment automatically using ansible. I will split this into 2 parts. First part will focus on creating the automation needed to deploy the containers on proxmox. Second part is about creating the tester tool solution. Assumption: you already have a proxmox server in place. your ansible controller has passwordless ssh access enabled to the proxmox server. you know what ansible is and how to use it. ok, so the first step is to install ansible. I recommend doing this in a virtual environment: ...

This is a quick one, I had to get the SN of my external screens recently and I thought I should share the powershell command I used for this task. This works only on your local machine, for AD nodes there are other options out there on the internet. Get-WmiObject WmiMonitorID -Namespace root\wmi |Select-Object @{l="Manufacturer";e={[System.Text.Encoding]::ASCII.GetString($_.ManufacturerName)}},@{l="Model";e={[System.Text.Encoding]::ASCII.GetString($_.UserFriendlyName)}},@{l="SerialNumber";e={[System.Text.Encoding]::ASCII.GetString($_.SerialNumberID)}} This should return something like this: PS C:\Users\costin> Get-WmiObject WmiMonitorID -Namespace root\wmi |Select-Object @{l="Manufacturer";e={[System.Text.Encoding]::ASCII.GetString($_.ManufacturerName)}},@{l="Model";e={[System.Text.Encoding]::ASCII.GetString($_.UserFriendlyName)}},@{l="SerialNumber";e={[System.Text.Encoding]::ASCII.GetString($_.SerialNumberID)}} Manufacturer Model SerialNumber ------------ ----- ------------ HPN HP E243i 6CM90XXXX HPN HP E223 3CQXXXXX