To fix this, you have to change the partition size of the recovery partition. ATTENTION: I am not responsible if you do something wrong here and lose all your data. Be careful what you do and always create a backup before any modifications on partition layouts. Continue only if you know what you do!
This Post describes, how to install the UniFi Network Server as Docker image on a QNAP NAS.
The first step is to make sure you’ve installed Container Station from the QNAP App Center. After this, open Container Station, go to “Applications” and click “Create”. Give your application a name, for example “unifi-and-mongodb”. Upload this yaml-code for docker-compose, replace “UNIFIPASSWORD” with a secure password, you will use this later to configure the database:
Did you know that it’s possible to discover your Snapmaker 2.0 in your LAN? Just send an UDP discover Broadcast to Port 20054 and your Snapmaker will reply with his IP-Address, Model-Name and Status.
Update 19.01.2024: This project got some reactions, see here: HomeAssistant-Forum and here: Snapmaker-Forum Meanwhile I created a new Script V2 which gets more Information from the Web-API, this makes the information below obsolete. -> See new code on github Maybe I will try to write a HomeAssistant Integration someday….
With this function, I inform my Home Assistant about the state of my Snapmaker. Home Assistant sends me a push-message if the 3D-Print, Laser-Cut or CNC is finished. Because I only need this information, it’s not necessary to login, get info and logout to the Snapmaker. Maybe I will write another script in future to read other values like process, temperatures, enclosure state etc.
Here is an example of my webhook-sensors in templates.yaml: (For more details see this Link)
Recently we changed the backup Server for our vCenter. The backup job over SCP worked for years on the old Server, but on the new one I was not able to configure the backup-schedule. I got always a timeout on the vCenter Server Appliance Management Web-GUI and I had to restart it with:
service-control --restart applmgmt
To get it working again without rebooting the whole vCenter Appliance.
After a few hours of debugging, I saw a process named sshpass which was hanging. sshpass tries to find “Password:” in the prompt and sends then the password.
Now the problem was, the old Server had a prompt like:
And the new one had:
Password for username@servername:
So sshpass was not able to find “Password:” and timed out.
As both our servers are BSD, I had to fix the sshd config on the new Server for PAM in /etc/pam.d/sshd with adding of “authtok_prompt=Password:” and then restart sshd.
Beim Neovac den blauen Deckel abmontieren und dann den weissen Einsatz entfernen. Der untere Zylinder wird dann neu anstelle des weissen Einsatzes eingeklemmt. Der Deckel als Halterung für den ESP32 wird dann einfach über den Zylinder gestülpt und seitlich mit einer Schraube fixiert. Auf dem ESP32-CAM muss der Fokus angepasst werden.