I no longer recommend the below method. For my updated recommendation, see this gist
The linux watchdog service can be configured to run certain 'liveness' tests periodically, and then take some action (such as reboot) if a test fails (and doesn't recover) for some period of time.
There is a built-in test for pinging an IP address (i.e. 'ping' directive), but you may instead need to test access to a hostname
| If you have a failure mode that can be diagnosed by a high rate of messages flooding the system log, | |
| you can use the script below in conjunction with the watchdog service to detect the condition | |
| and reboot if it persists. This is a pretty big hammer, but potentially better than just rebooting on | |
| loss of network or some other arbitrary liveness test. | |
| add a 'test-binary' line to /etc/watchdog.conf pointing to this script (will be treated as V0 test script | |
| with no corresponding repair script). Also, set 'interval' to something like 20 seconds (at least greater than | |
| the sample period in the script). | |
| You can convince yourself it's working (once the watchdog service has been restarted with the above config) |
| We want to run a long-running process during certain hours, days-of-the-week, etc. | |
| We want the service to start on a schedule, and be stopped on a corresponding schedule. | |
| Example: Residential electric rates are based on Time of Use (TOU) such that Weekdays | |
| from 1p to 7p are considered 'Peak Hours' when rates are much higher than all other times. | |
| Our long running process uses significant electricity, so we want to stop running it | |
| once we reach the Peak Hours period, and resume running once the Peak period is over. | |
| 1.) We create a systemd service file for the long running process (foo.service) | |
| 2.) We create a systemd timer unit associated with the service (foo.timer). This timer handles |
| Task: add vector type option parsing to chia_plot for the -t and -2 options | |
| so the user can specify a comma-separated list of paths instead of just a single path | |
| e.g. | |
| ./chia-plot -n 4 -t /mnt/ssd1/,/mnt/ssd2 -2 /mnt/ssd3/,/mnt/ssd4/,/mnt/ssd5 <other options> | |
| in the above example the actual paths used will be as follows: | |
| plot -t_path -2_path |
| The version of ModemManager that ships with Raspberry Pi OS (1.10) doesn't appear to work with the Telit LE910 V2 | |
| in MBIM mode (AT#USBCFG=3) and so we must upgrade to a newer version (1.14). Thankfully, that is available via | |
| the debian backports repository. | |
| 0.) Add this line to /etc/apt/sources.list | |
| deb http://deb.debian.org/debian buster-backports main | |
| 1.) Download and install the Debian repo key package | |
| wget http://deb.debian.org/debian/pool/main/d/debian-archive-keyring/debian-archive-keyring_2021.1.1_all.deb | |
| sudo dpkg -i debian-archive-keyring_2021.1.1_all.deb |
| How to setup the Raspberry Pi to use the Connected IO EM1000T-VZ-CAT1 modem in MBIM mode | |
| (Tested on Pi 4 model B (2GB), Raspberry Pi OS Buster 2021-01-11 release, Modem firmwre 20.00.015) | |
| First put the modem into MBIM mode by issuing the following AT command (using minicom -D /dev/ttyACM0) | |
| at#usbcfg=5 | |
| Power off /on modem, reboot Pi | |
| Confirm the following device exists | |
| /dev/cdc-wdm0 |
| Make sure the host has up-to-date nvidia drivers (460 as of this writing) | |
| sudo apt install nvidia-headless-460 | |
| Download ethminer to current directory: | |
| wget https://github.com/ethereum-mining/ethminer/releases/download/v0.19.0-alpha.0/ethminer-0.19.0-alpha.0-cuda-9-linux-x86_64.tar.gz | |
| Create Dockerfile as follows: | |
| FROM nvidia/cuda:11.2.0-base-ubuntu18.04 | |
| LABEL description="ethminer container for NVIDIA GPU systems" |
| if (msg.payload == 0) { | |
| msg.payload = "No trip factor " | |
| } else if (msg.payload == 1) { | |
| msg.payload = "Over-current event while at constant speed" | |
| } else if (msg.payload == 2) { | |
| msg.payload = "Over-current event during deceleration" | |
| } else if (msg.payload == 3) { | |
| msg.payload = "Over-current event during acceleration " | |
| } else if (msg.payload == 4) { | |
| msg.payload = "Over-current event during other conditions" |
| FROM ubuntu:18.04 | |
| LABEL description="ethminer AMD ROCm Container" | |
| ENV API_PORT=3333 | |
| COPY ethminer.tar.gz ./ethminer.tar.gz | |
| ARG ROCM_VER=4.0.0 | |
| RUN apt-get update \ |
| cd ethminer | |
| mkdir build | |
| cd build | |
| cmake .. -DETHASHCUDA=OFF -DETHASHCL=ON -DUSE_SYS_OPENCL=ON -DAPICORE=ON | |
| CPATH=/opt/rocm/opencl/include cmake --build . |