Cricalix.Net - User contributions [en-gb]

Computing/NUT

2026-04-02T17:17:05Z

Cricalix:

== Network UPS ==

=== Installation ===
<syntaxhighlight lang="bash">
dnf install nut
</syntaxhighlight>

=== Configuration ===
For the Eaton Pro UPS, '''/etc/ups/ups.conf'''<syntaxhighlight lang="ini">
[eaton650]
driver = "usbhid-ups"
port = "auto"

</syntaxhighlight>'''/etc/ups/upsd.conf'''<syntaxhighlight lang="bash">
LISTEN * 3493

</syntaxhighlight>All other files were left at defaults from the RPM installs, bar this detritus from a polkit adventure - it may or may not still apply<syntaxhighlight>
polkit.addRule(function(action, subject) {
if (action.id == "org.freedesktop.systemd1.manage-units" &&
subject.user == "nut") {
return polkit.Result.YES;
}
});

</syntaxhighlight>

=== udev ===
<syntaxhighlight>
ATTR{idVendor}=="0463", ATTR{idProduct}=="ffff", MODE="664", GROUP="nut"

</syntaxhighlight>

== Runtime ==
<syntaxhighlight>
systemctl start nut-server
</syntaxhighlight>The script behind nut-server will spin up new systemctl services to handle the UPS.

== Troubleshooting ==
Previous attempts got stuck on custom UPS definitions in systemd, with permissions not setting up correctly etc. Ended up blowing everything away and restarting from scratch with the NUT enumerator approach.

Computing/NUT

2026-04-02T17:16:48Z

Cricalix:

== Network UPS ==

=== Installation ===
<syntaxhighlight lang="bash">
apt install nut nut-monitor
</syntaxhighlight>

=== Configuration ===
For the Eaton Pro UPS, '''/etc/ups/ups.conf'''<syntaxhighlight lang="ini">
[eaton650]
driver = "usbhid-ups"
port = "auto"

</syntaxhighlight>'''/etc/ups/upsd.conf'''<syntaxhighlight lang="bash">
LISTEN * 3493

</syntaxhighlight>All other files were left at defaults from the RPM installs, bar this detritus from a polkit adventure - it may or may not still apply<syntaxhighlight>
polkit.addRule(function(action, subject) {
if (action.id == "org.freedesktop.systemd1.manage-units" &&
subject.user == "nut") {
return polkit.Result.YES;
}
});

</syntaxhighlight>

=== udev ===
<syntaxhighlight>
ATTR{idVendor}=="0463", ATTR{idProduct}=="ffff", MODE="664", GROUP="nut"

</syntaxhighlight>

== Runtime ==
<syntaxhighlight>
systemctl start nut-server
</syntaxhighlight>The script behind nut-server will spin up new systemctl services to handle the UPS.

== Troubleshooting ==
Previous attempts got stuck on custom UPS definitions in systemd, with permissions not setting up correctly etc. Ended up blowing everything away and restarting from scratch with the NUT enumerator approach.

Computing/NAS/Software

2026-04-02T17:12:23Z

Cricalix: Remove proxmox, use Incus

== Hardware ==
Core is a https://nascompares.com/review/cwwk-q670-8-bay-gen5-nas-vpro-mobo-review/ ([https://web.archive.org/web/20250624104920/https://nascompares.com/review/cwwk-q670-8-bay-gen5-nas-vpro-mobo-review/ archive] link); twin 2.5G network ports, a lot of SATA ports, and lots of compromises.

== Network ==
Used https://mkdocs-4960c2.gitlab.io/lab/incus/incus_network_issues_walkthrough/ ([https://web.archive.org/web/20260402165455/https://mkdocs-4960c2.gitlab.io/lab/incus/incus_network_issues_walkthrough/ archive] link; apparently AI generated, but functional enough) as a guide to reconfiguring the Fedora OS that's running the NAS so that br0 is the primary interface for Incus to use directly. This enables host-container communication - macvlan doesn't allow this, and the default Incus bridge uses NAT (and I don't want to deal with port forwards)

=== Host ===
The host uses enp7s0 for connectivity<syntaxhighlight lang="ini">
[connection]
id=enp7s0
uuid=4d354481-a088-3449-8d28-35b96ac1a3d4
type=ethernet
autoconnect-priority=-999
interface-name=enp7s0
timestamp=1775146834

[ethernet]

[ipv4]
address1=192.168.0.181/24
dns=192.168.0.1;
gateway=192.168.0.1
method=manual

[ipv6]
addr-gen-mode=default
method=auto

[proxy]
</syntaxhighlight>

=== Host Bridge ===
The bridge is configured with br0 having a static IP, and a slave interface is set up for enp8s0 so that the bridge sits on physical network port.<syntaxhighlight lang="ini">
[connection]
id=br0
type=bridge
interface-name=br0

[bridge]
forward-delay=0
stp=false

[ipv4]
address1=192.168.0.2/24
dns=192.168.0.1;
gateway=192.168.0.1
method=manual

[ipv6]
addr-gen-mode=default
method=auto
</syntaxhighlight><syntaxhighlight lang="ini">
[connection]
id=br0-slave
type=ethernet
controller=br0
interface-name=enp8s0
port-type=bridge

[ethernet]

[bridge-port]

</syntaxhighlight>

=== Incus Bridge ===
Incus's default bridge was removed when setting up the new configuration (older install where the default bridge had been accepted. A custom physical interface was added, based on the <code>br0</code> bridge. Profiles were then changed to use the new <code>ibr0</code>.
incus network create ibr0 --type=physical parent=br0

== VMs and Containers ==

=== Unraid VM ===
Unraid needs a USB stick to boot from, as it uses the serial number of the stick as a license key. Ended up with plopkexec in the boot path for the qemu-backed VM (pc-q35)<syntaxhighlight lang="yaml">
devices:
iso-volume:
boot.priority: '10'
pool: machines
source: plopkexec64.iso
type: disk
bootdrive:
required: 'true'
serial: 20CF302E2382F150663CA637
type: usb
sata:
address: '00:17.0'
type: pci
</syntaxhighlight>Whole SATA controller is passed through, removing the devices from the view of the host OS.

=== HomeAssistant ===
Default HAOS setup, but with two USB devices passed through from the host for Zigbee and Matter support.<syntaxhighlight lang="yaml">
devices:
matter-antenna:
productid: 831a
type: usb
vendorid: 303a
zigbee:
productid: 55d4
type: usb
vendorid: 1a86
</syntaxhighlight>The Incus web UI can do very silly things when adding USB devices; doing it via the YAML editor is safer. Silly being defined as not allowing settings for the passed-through device, and 'usb' seemed to grab everything including the pass through for the Unraid VM (making Unraid unhappy).

Blue Opal/Engine

2025-06-07T12:31:00Z

Cricalix: /* Inventory */

Notes for the engine, a Yanmar 3GM30F.

== Tools ==

{| class="wikitable"
|+
!Area
!Item
!Fixing
!Driver
|-
|Engine
|Alternator
|Top bolt
|14mm
|-
|
|
|Bottom bolt
|12mm
|-
|
|
|Swing nut
|12mm
|-
|
|Water Pump
|Top bolt
|12mm
|-
|
|
|Bottom bolt
|12mm
|}

== Starter Solenoid ==

To solve a starting issue, an automotive relay was installed. The correct relay will have four terminals numbered 85, 86, 30 and 87.
<blockquote>
Make up a length of cable from the large screw on the solenoid (battery cable terminal) and connect this to #30. Remove white cable from small solenoid terminal and connect to #85.

Make up cable from #86 connect to engine block. Connect #87 to small terminal on the solenoid.

Terminals #85 & #86 actuate the relay and #30 & #87 power the solenoid.
</blockquote>
-- https://www.cricalix.net/2023/05/13/relaying-a-solenoid/

== Parts Cross-reference ==

{| class="wikitable"
|+
!Item
!Page
!Original
!Alternative 1
!Notes
|-
|Primary fuel filter
|
|Racor R12P
|Fleetguard FS19627
|Blue Opal's original filter housing was replaced with a Racor
|-
|Secondary fuel filter / fuel strainer
|55
|Yanmar 104500-55710
|Orbitrade 8-55710
|
|-
|Oil filter
|38
|Yanmar 124450-35100
Yanmar 119660-35150

Yanmar 119305-35170

Yanmar 119305-35151
|Blue Print ADS72101
|The ADS72101 has a larger outer diameter, but fits. Filter is shared across 1/2/3GMs.
35100 appears to be unavailable.
35151 supersedes 35150, slightly smaller.
35170 found in spares on board.
https://marineparts.ie/filter-assy-lub-oil/ (35170)
https://marineparts.ie/oil-filter-rec119305-35151-yanmar/ (35151)
|}

Page numbers reference the [[:File:Yanmar-3GM30-parts-catalog.pdf|Yanmar Parts Catalog]].

For fuel filters, https://www.fuelfilter-crossreference.com/convert/FLEETGUARD/FS19627 is a decent reference.

For oil filters, https://www.oilfilter-crossreference.com/convert/YANMAR/124450-35100 is a decent reference.
Filter type: Full-Flow Lube Spin-on
Thread measurement: 20x1.5mm
Outer diameter: 77 mm (Approx. 3.03")
Height: 86 mm (Approx. 3.39")
Mounts - https://www.parts4engines.com/yanmar-3gm30-and-3gm30f-engine-mount/ - claim to be better than original ones.

== Inventory ==
{| class="wikitable"
|+
!Purpose
!Part number
!Count
!Notes
|-
|Impeller kit
|Johnson 09-810B / JIKJMP005
|3
|Yanmar water pump is a rebadge
|-
|Impeller
|Yanmar 128296-42070
|1
|Not a full kit
|-
|Primary fuel filter
|Fleetguard FS19627
|3
|
|-
|Oil filter
|Yanmar 119305-35170
|1
|
|-
|Oil filter
|BluePrint ADS72101
|4
|
|-
|Thermostat gasket
|Yanmar 129350-49451
|1
|https://marineparts.ie/rec129350-49541/
|-
|Fresh water thermostat
|Yanmar 121750-49800
|1
|
|-
|Fuel filter
|Orbitrade 8-55710 / 10450055710
|3
|
|-
|Alternator belt
|Yanmar 25132-003700
|1
|https://www.svb24.com/en/v-belt-for-yanmar-2gm20f-3gm30f.html
|-
|Raw water belt
|Yanmar 104511-78780
|0
|https://www.svb24.com/en/yanmar-v-belt-for-seawater-pump-2-3-gm.html
|-
|Collar anode
|AV004 / 957000001805
|5
|25mm shaft,https://miscosrl.com/en/prodotto/anodo-a-collare-av004-asse-o-25mm/
|-
|Heads smell filter
|Vetus NSF16FES
|1
|4 in pack, https://webshop.vetus.com/en/product/nsf16fes-filter-element-for
|-
|Manual bilge kit
|Gusher Titan AK4400
|1
|Service kit, https://www.chmarine.com/whale-gusher-titan-service-kit/
|-
|Boiler anode
|FVSLANMG 1820A00
|2
|200mm boiler anode, <nowiki>https://www.svb24.com/en/quick-magnesium-anode-for-b3-bx-and-bxs-series-boilers.html</nowiki>
|}
Main anode 10mm stud 17mm nut 0.4 alu

shaft anode 4 mm Allen captive nuts 25mm

sra supply to head -15-27 jubilee

waste from head 35 to 50 jubilee
[[Category:Blue Opal]]

Blue Opal/Engine

2025-06-07T10:52:55Z

Cricalix: /* Tools */

Blue Opal/Electrics

2025-03-17T08:44:43Z

Cricalix:

=== Battery banks ===
House bank - 2x 105 Ah SLA. Effective 100 Ah.
Starter - 1x 80 Ah SLA. Effective 40 Ah.

=== Alternator ===
BV PSH 80A, Hitachi saddle mount. Sourced from Myles Balfe. V-belt sheave.
[[File:Img 2122-768x1024.jpg|none|thumb|Part number is 985.001.080.200.]]
[[File:Alternator specifications for Blue Opal.jpg|none|thumb]]

=== Terminal and driver sizes ===
{| class="wikitable"
|+
!Area
!Item
!Fixing
!Driver
!Stud
|-
|Battery
|Shunt
|Terminal
|10mm
|8mm
|-
|
|House
|Terminal
|14mm
|10mm
|-
|
|Starter
|Terminal
|13/14mm
|10mm
|-
|
|Blue Sea Fused Bus
|Terminal
|10mm
|5mm
|-
|
|MIDI fuses
|Terminal
|10mm
|8mm
|-
|
|Negative bus
|Terminal
|14mm
|8mm
|}
=== Core power distribution and charging===
This diagram is for the wiring in the starter and house battery bank compartments.

Charge and Distribution fuses are MIDI style with spare, Blue Sea 7720.

Solar charger fuse is inline automotive.

{{#mermaid:config.theme = neutral | graph TD;

subgraph "House Bank"
subgraph "House Battery 1 (2019)"
HOUSE_BAT1_NEG[-];
HOUSE_BAT1_POS[+];
end
subgraph "House Battery 2 (2019)"
HOUSE_BAT2_NEG[-];
HOUSE_BAT2_POS[+];
end
end
subgraph "Starter Battery (2023)"
STARTER_BAT_POS[+];
STARTER_BAT_NEG[-];
end

subgraph "House Battery Switch"
HOUSE_SW_POS[S];
HOUSE_SW_LOAD[L];
end
subgraph "Engine Battery Switch"
ENG_SW_SOURCE[S];
ENG_SW_LOAD[L];
end

subgraph "Alternator"
ALT_GEN_POS[+];
end

subgraph "BC1240 (Mains)"
MAINS_CHG_ENG[Starter];
MAINS_CHG_HOU["Unused(House)"];
MAINS_CHG_NEG[-];
end

subgraph "BB1240 (B2B 12V)"
BB1240_STARTER[Source];
BB1240_NEG[Neg];
BB1240_HOU[Target];
end

subgraph "Engine Panel"
IGNITION([Ignition Switch]);
end

subgraph "House Shunt"
HOUSE_SHUNT_POS[S]
HOUSE_SHUNT_NEG[L]
HOUSE_SHUNT_MON[Tap]
HOUSE_SHUNT_POS --- HOUSE_SHUNT_NEG;
HOUSE_SHUNT_POS --- HOUSE_SHUNT_MON --- HOUSE_SHUNT_NEG;
end

subgraph "Solar"
SOLAR_PANEL["200 Wp Renogy"]
subgraph "Votronic 250"
SOLAR_IN_POS[S]
SOLAR_IN_NEG[S]
SOLAR_OUT_POS[L]
SOLAR_OUT_NEG[L]
end
SOLAR_PANEL --- SOLAR_IN_POS;
SOLAR_PANEL --- SOLAR_IN_NEG;
end

subgraph "Charge Fuse"
STARTER_CHARGE_FUSE_SOURCE[S]
STARTER_CHARGE_FUSE(70A)
STARTER_CHARGE_FUSE_LOAD[L]
STARTER_CHARGE_FUSE_SOURCE --- STARTER_CHARGE_FUSE --- STARTER_CHARGE_FUSE_LOAD;
end

BAT_NEG_BUS[Battery Negative Busbar];
BSA_STUD[BlueSea Ancillary]
HOUSE_POS_BUS[House Positive Bus]
HOUSE_NEG_BUS[House Negative Bus];
HOUSE_DIST_FUSE(Distribution Fuse 150A)
HOUSE_CHARGE_FUSE(Charge Fuse 70A)
GROUND[Engine Block];
WLS_SW_POS([Windlass Switch]);
ALWAYS_ON_DIST[Always On Bus];
WINDLASS_NEG[Windlass];

HOUSE_BAT2_POS === HOUSE_BAT1_POS;
HOUSE_BAT2_NEG === HOUSE_BAT1_NEG;
HOUSE_BAT1_POS ==== HOUSE_DIST_FUSE;
HOUSE_BAT1_NEG === STARTER_BAT_NEG;

HOUSE_SW_POS --- ALWAYS_ON_DIST;
FRIDGE[Chillbox] --- BAT_NEG_BUS;
STARTER_CHARGE_FUSE_LOAD --- STARTER_BAT_POS;
HOUSE_CHARGE_FUSE --- HOUSE_BAT1_POS;
STARTER_BAT_POS == 25mm ==> ENG_SW_SOURCE;
STARTER_BAT_NEG === HOUSE_SHUNT_POS ;
ENG_SW_LOAD --- IGNITION;
ENG_SW_LOAD --- WLS_SW_POS;
ALT_GEN_POS == 16mm ==> STARTER_CHARGE_FUSE_SOURCE;
BB1240_NEG === STARTER_BAT_NEG;
STARTER_CHARGE_FUSE_SOURCE == 10mm === BB1240_STARTER;
BB1240_HOU == 10mm ==> HOUSE_CHARGE_FUSE;
BAT_NEG_BUS === HOUSE_NEG_BUS;
MAINS_CHG_NEG === BAT_NEG_BUS;
HOUSE_SW_LOAD === HOUSE_POS_BUS;
HOUSE_DIST_FUSE --- HOUSE_SW_POS;
HOUSE_SW_LOAD === BSA_STUD;
HOUSE_SHUNT_NEG === BAT_NEG_BUS;
STARTER_BAT_NEG ==== GROUND;
MAINS_CHG_ENG --- STARTER_CHARGE_FUSE_SOURCE;
SOLAR_OUT_POS --- STARTER_BAT_POS;
SOLAR_OUT_NEG --- STARTER_BAT_NEG;
WINDLASS_NEG --- STARTER_BAT_NEG;

classDef pos stroke:#f00
classDef fuse stroke:#00f,fill:#5c5;
class HOUSE_BAT1_POS,HOUSE_BAT2_POS,HOUSE_DIST_FUSE_POS,WLS_SW_POS,ENG_SW_SOURCE,ENG_SW_LOAD,HOUSE_SW_POS pos;
class STARTER_CHARGE_FUSE_SOURCE,SOLAR_IN_POS,SOLAR_OUT_POS pos;
class ENG_CHG_FUSE_POS,STERLING_STARTER,STERLING_HOUSE,IGNITION pos;
class MAINS_CHG_HOU,MAINS_CHG_ENG,STARTER_BAT_POS,ALT_GEN_POS pos;
class HOUSE_SW_LOAD pos;
class STARTER_CHARGE_FUSE_LOAD pos;
class BB1240_HOU,BB1240_STARTER pos;
class ALWAYS_ON_DIST,BSA_STUD,HOUSE_POS_BUS pos;
class HOUSE_DIST_FUSE,HOUSE_CHARGE_FUSE,STARTER_CHARGE_FUSE fuse;

}}To-do: Replace direct-to-terminal with distribution bus bars. Starter negative terminal has more than 4 cables attached.

=== Blue Sea Ancillary===
This distribution setup is used for power distribution in the saloon; it's in the same physical area as the batteries. Distributor is a Blue Sea Systems ST compact 8-circuit (5046) with 10-32 stud, and 8-32 screw terminals.

{{#mermaid:graph LR;

HOU_SWITCH["House Battery Switch (Load)"];
BAT_NEG_BUS[Battery Negative Busbar];

subgraph "BlueSea Ancillary"
BSA_STUD(Stud);
BSA_FRIDGE(Fridge 15);
BSA_AMPS(Ammeter 3A);
BSA_PP1(Powerpole 20A);
BSA_PP2(Powerpole 20A);
BSA_USB(USB 5A);
BSA_BILGE(Bilge 5A);
BSA_WPUMP(Water Pump 15A);
BSA_STUD --- BSA_FRIDGE & BSA_AMPS & BSA_PP1 & BSA_PP2 & BSA_USB & BSA_BILGE & BSA_WPUMP;
end

HOU_SWITCH === BSA_STUD;
BSA_FRIDGE === FRIDGE[Chillbox] === BAT_NEG_BUS;
BSA_AMPS --- AMMETER[Ammeter] --- BAT_NEG_BUS;
BSA_PP1 --- PP1[Powerpole] --- BAT_NEG_BUS;
BSA_PP2 --- PP2[Powerpole] --- BAT_NEG_BUS;
BSA_USB --- USB_SALOON[USB Sockets] --- BAT_NEG_BUS;
BSA_BILGE --- BILGE[Bilge Pump] --- BAT_NEG_BUS;
BSA_WPUMP --- WATER_PUMP[Fresh Water Pump] --- BAT_NEG_BUS;
classDef pos stroke:#f00
classDef fuse stroke:#00f,fill:#5c5;
class HOU_SWITCH pos;
class BSA_FRIDGE,BSA_AMPS,BSA_PP1,BSA_PP2,BSA_USB,BSA_BILGE,BSA_WPUMP fuse;
|
config.theme = neutral

}}

=== Always on distribution ===

This powers low draw devices that should be powered without the house switch being engaged. Basically, lights. Located in the wiring cabinet above and behind the chart table. Wired to supply side so it's always got power, bar the local fuse blowing.

{{#mermaid:graph LR;
HOU_SWITCH("House Battery Switch (Supply)");
BAT_NEG_BUS[Battery Negative Busbar];
CAB_NEG_BUS[Wiring Cabinet -ve Bus]

subgraph "BlueSea 4-fuse"
BSA_STUD(Stud);
BSA_SALOON(Saloon 3A);
BSA_CHART(Chart Table 3A);
BSA_CABINET(Cabinet 1A);
BSA_STUD --- BSA_SALOON & BSA_CHART & BSA_CABINET;
end

HOU_SWITCH === BSA_STUD;
BSA_SALOON --- SALOON_SW(Companionway Switch) --- SALOON[Saloon Light] --- CAB_NEG_BUS;
BSA_CHART --- CHART_SW(Chart Table Switch) --- CHART_LIGHT[Chart Table Light] --- CAB_NEG_BUS;
BSA_CABINET --- CABINET_SW(Wiring Cabinet Switch) --- CABINET_LIGHT[Cabinet Light] --- CAB_NEG_BUS;
CAB_NEG_BUS === BAT_NEG_BUS;
classDef pos stroke:#f00
classDef fuse stroke:#00f,fill:#5c5;
class HOU_SWITCH pos;
class BSA_SALOON,BSA_CHART,BSA_CABINET fuse;
|
config.theme = neutral

}}

=== Water pump ===

Wired via a relay so that the switch by the chart table just activates the relay, and the pump gets power from 6mm2 direct from the battery compartment.

{{#mermaid:graph LR;
subgraph "Relay"
SWITCHING_TERMINAL[Switching];
SWITCHED_TERMINAL[Switched];
end
subgraph "Pump"
PUMP_POS[+];
PUMP_NEG[-];
end
BAT_NEG_BUS[Battery Negative Busbar];
CAB_NEG_BUS[Wiring Cabinet -ve Bus]
PUMP_PANEL_SW(Panel Switch);
BSA_BAT_PUMP(Blue Sea Ancillary);
PUMP_PANEL_SW --> SWITCHING_TERMINAL --> CAB_NEG_BUS;
BSA_BAT_PUMP --> SWITCHED_TERMINAL --> PUMP_POS;
PUMP_NEG --> BAT_NEG_BUS;
classDef pos stroke:#f00
classDef fuse stroke:#00f,fill:#5c5;
class BSA_BAT_PUMP fuse;
class PUMP_PANEL_SW pos;
|
config.theme = neutral

}}

The relay is the same as the one for the engine starter, 12V 40A SPST with 30/85/86/87 terminals, normally open.
[[Category:Blue Opal]]

Computing/NAS/Software

2024-12-22T21:15:17Z

Cricalix:

=== Proxmox ===
Defaults to port 8006. Given I access it from multiple machines, defaulting to 443 would be nice.

<code>iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-ports 8006</code>

Then use iptables-persistent to make that apply every time.

=== Unraid VM ===
Unraid needs a USB stick to boot from. Legacy advice on the Internet is that Proxmox won't boot a VM from a USB stick, but that's wrong with at least Proxmox V8. Config for VM

* q35 machine
* UEFI/OVMF
* '''No''' EFI disk
* Some GB of RAM
* Host CPU cores, 2 of them (the VM is tied to the USB stick anyway, so may as well tie it to the host cores)
* PCI passthrough - SATA controller

SATA controller was assigned to a resource mapping at the Datacenter level in the Proxmox UI tree, then made available for the PCI passthrough. Two USB sticks were also configured in resource mappings; one for the boot stick, and the other for temporary use in the Unraid array. Integrated graphics also isolated for passthrough to the Media Host.

=== Media host VM ===
Tried q35 with PCI passthrough of the IGP

Hit https://bugzilla.proxmox.com/show_bug.cgi?id=2381

Revert to 440 with PCI passthrough. Had to reinstall for some reason, and switch to SeaBIOS.

==== Media host Sonarr ====
<code>podman run --name=sonarr --detach -e PUID=$(id -u media) -e PGUID=$(id -g media) -e TZ=Europe/Dublin -p 8989:8989 -v /services/sonarr:/config -v /vault/video/TV\ Shows:/media --restart always lscr.io/linuxserver/sonarr:latest</code>

Needs host NFS mounted. Avoids trying to do privileged LXCs on Proxmox and working out how to maintain a copy of the configs outside of the container.

Computing/NAS/Software

2024-12-22T12:20:25Z

Cricalix:

Proxmox

Defaults to port 8006. Given I access it from multiple machines, defaulting to 443 would be nice.

`iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-ports 8006`

Then use iptables-persistent to make that apply every time.

Unraid VM

Unraid needs a USB stick to boot from. Legacy advice on the Internet is that Proxmox won't boot a VM from a USB stick, but that's wrong with at least Proxmox V8. Config for VM

* q35 machine
* UEFI/OVMF
* '''No''' EFI disk
* Some GB of RAM
* Host CPU cores, 2 of them (the VM is tied to the USB stick anyway, so may as well tie it to the host cores)
* PCI passthrough - SATA controller

SATA controller was assigned to a resource mapping at the Datacenter level in the Proxmox UI tree, then made available for the PCI passthrough. Two USB sticks were also configured in resource mappings; one for the boot stick, and the other for temporary use in the Unraid array.

Media host VM

Tried q35 with PCI passthrough of the IGP

Hit https://bugzilla.proxmox.com/show_bug.cgi?id=2381

2024-07-28T16:40:21Z

Cricalix:

Manuals for Blue Opals electrical gubbins

* [[:File:Sterling Power BB1240.pdf|BB1240 Battery to Battery charger]]
* [[:File:Sterling Power BC1240 compressed.pdf|BC1240 Mains to Battery charger]]
* [[:File:Votronic_MPPT_250_Duo_manual.pdf|Votronic Solar Charger 250]]

2023-09-25T18:24:18Z

Cricalix:

Things I forget when doing new Rust installs, or other things I want to keep track of with Rust.

# Install rust-analyzer via rustup. <code>rustup component add rust-analyzer</code>

==== Reqwest GET URIs ====
<syntaxhighlight lang="rust">
let mut req = client.get("https://www.google.com").build().unwrap();

let query: String = form_urlencoded::Serializer::new(String::new())
.append_key_only("foo")
.finish();
req.url_mut().set_query(Some(&query));
</syntaxhighlight>https://docs.rs/form_urlencoded/latest/form_urlencoded/struct.Serializer.html#method.append_pair

<code>sudo apt install pkg-config libssl-dev</code>

==== Clap for CLI handling ====
<code>cargo add clap -F derive,env</code>

==== Serde and Axum ====

Refer to things correctly in the structs. Structs need to be <code>#[derive(Deserialize,Debug)]</code> for Azum JSON processing to work. Avoid the rawvalue stuff if possible, because lifetimes become a problem and the blocking error is <code>higher-ranked lifetime error</code> pointing at the <code>post()</code> handler in the Axum routing block of code.<syntaxhighlight lang="rust">
#[derive(Deserialize,Debug)]
struct AisCatcherMessage {
protocol: String,
encodetime: String,
stationid: String,
receiver: AisCatcherReceiver,
device: AisCatcherDevice,
msgs: Vec<serde_json::Value>,
}

async fn process_ais_message(Json(payload): Json<AisCatcherMessage>) -> impl IntoResponse {
println!("{:?}", payload);

for msg in payload.msgs {
println!("{}", msg["rxtime"]);
}
(StatusCode::CREATED, Json(json!({"message": "Processed" })))
}
</syntaxhighlight>

Computing/Rust

2023-09-25T18:22:42Z

Cricalix:

Things I forget when doing new Rust installs, or other things I want to keep track of with Rust.

# Install rust-analyzer via rustup. <code>rustup component add rust-analyzer</code>

==== Reqwest GET URIs ====
<syntaxhighlight lang="rust">
let mut req = client.get("https://www.google.com").build().unwrap();

let query: String = form_urlencoded::Serializer::new(String::new())
.append_key_only("foo")
.finish();
req.url_mut().set_query(Some(&query));
</syntaxhighlight>https://docs.rs/form_urlencoded/latest/form_urlencoded/struct.Serializer.html#method.append_pair

<code>sudo apt install pkg-config libssl-dev</code>

==== Clap for CLI handling ====
<code>cargo add clap -F derive,env</code>

Serde and Axum

Refer to things correctly in the structs. Structs need to be <code>#[derive(Deserialize,Debug)]</code> for Azum JSON processing to work.<syntaxhighlight lang="rust">
#[derive(Deserialize,Debug)]
struct AisCatcherMessage {
protocol: String,
encodetime: String,
stationid: String,
receiver: AisCatcherReceiver,
device: AisCatcherDevice,
msgs: Vec<serde_json::Value>,
}

async fn process_ais_message(Json(payload): Json<AisCatcherMessage>) -> impl IntoResponse {
println!("{:?}", payload);

for msg in payload.msgs {
println!("{}", msg["rxtime"]);
}
(StatusCode::CREATED, Json(json!({"message": "Processed" })))
}
</syntaxhighlight>

Computing/Rust

2023-09-25T17:02:56Z

Cricalix: Created page with "Things I forget when doing new Rust installs, or other things I want to keep track of with Rust. # Install rust-analyzer via rustup. <code>rustup component add rust-analyzer</code> ==== Reqwest GET URIs ==== <syntaxhighlight lang="rust"> let mut req = client.get("https://www.google.com").build().unwrap(); let query: String = form_urlencoded::Serializer::new(String::new()) .append_key_only("foo") .finish(); req.url_mut().set_query(Some(&query)); </syntaxhighl..."

Computing/AIS Catcher

2023-09-25T07:36:10Z

Cricalix: Created page with "Installation # https://github.com/jvde-github/AIS-catcher#container-images"

Installation

# https://github.com/jvde-github/AIS-catcher#container-images

Computing/Getting ERDDAP Running

2023-09-25T07:20:49Z

Cricalix:

ERDDAP is software for serving up scientific data. To run and configure it, the Docker approach works fairly well (even running on a Synology NAS).

=== Installation ===

# <code>docker pull axiom/docker-erddap:latest-jdk17-openjdk</code>

=== Configuration ===

# Read https://coastwatch.pfeg.noaa.gov/erddap/download/setupDatasetsXml.html very carefully.
## It's long. It's thorough.
# Read through https://github.com/unidata/tomcat-docker to see if any Tomcat bits apply (unlikely, will use Caddy2 to front this Tomcat)
# Read through https://registry.hub.docker.com/r/axiom/docker-erddap/ and (source) https://github.com/axiom-data-science/docker-erddap
# Run the container at least once and extract /usr/local/tomcat/content/erddap/setup.xml and datasets.xml
# Tune the XML files
## Even though Axiom's docker can do everything with environment variables, setup.xml must exist
# Re-run the docker instance with file pass-throughs
## Don't forget to pass through the bigParentDirectory, because the logs are there
## In fact, there's a ton of stuff there that is needed for persistent operation
# A sample JSON file is needed where the dataset indicates the files will exist
## The record should be deletable once the system is running and has real data flowing
# Use the DasDds.sh script in the WEB-INF directory to validate the dataset.xml file
## Given this is docker, either <code>docker exec -it <name> /bin/bash</code> or invoke it with sufficient pass-throughs to run the script directly from the host

=== Logs ===

# Catalina logs are uninteresting
# Application logs are not exported to docker's log system
# Application logs are in the bigParentDirectory passed-through volume

=== HTTPGet errors ===

# <code>sourceName</code> does not do case translations to <code>destinationName</code>. They must be '''identical'''.
# Configuration of the dataset attributes uses (effectively) the <code>destinationName</code> spelling
# <code>time, longitude, latitude</code> must be spelt that way
# <code>author</code> must be the last field on the request, and it points to the keys (username_$password)
# <code>command</code> must exist in the definition, but never set
# Yes, it's HTTP GET -> data write happens. It's terrible and goes against the RFC for web server implementation.

=== AIS Catcher integration ===
The whole goal of this setup is to grab AIS data from the meteorological sensors in Dublin Bay. A simple proof-of-concept parser follows.

<syntaxhighlight lang="python" line="">
#!/usr/bin/env python3

import json
import urllib.request
import urllib.parse
from datetime import datetime

URL="https://erddap.home.arpa/erddap/tabledap/datasetName.insert"
MAPPER = {
"signalpower": "Signal_Power",
"wspeed": "Wind_Speed",
"wgust": "Wind_Gust_Speed",
"wdir": "Wind_Direction",
"wgustdir": "Wind_Gust_Direction",
"lon": "longitude",
"lat": "latitude",
"waveheight": "Wave_Height",
"waveperiod": "Wave_Period",
"mmsi": "MMSI",
}

with open("ais.capture", "r") as f:
lines = f.readlines()

lines = [json.loads(x) for x in lines if "wspeed" in x and "01301" in x]

for line in lines:
kv = {}
rxtime = line["rxtime"]
dt_rxtime = datetime.strptime(rxtime, "%Y%m%d%H%M%S")
kv["time"]=dt_rxtime.strftime('%Y-%m-%dT%H:%M:%SZ')
kv["Station_ID"] ="Dublin_Bay_Buoy"
for field, value in MAPPER.items():
kv[value]=line[field]
kv["author"] ="testuser_somepassword"
params = urllib.parse.urlencode(kv)
url = f"{URL}?{params}"
with urllib.request.urlopen(url) as f:
print(f.read().decode('utf-8'))
</syntaxhighlight>