David Osei

David Osei

Runs the servers Pegel lives on, the release job and the Raspberry Pi in his hallway in Ostheim. Writes the incident reports, including the ones about his own changes.

Post

Release day

A signed tag starts everything else: two builds, the checksum file and the release page. Eight seconds of it, looped.

1 min

PostMembers only

Sixty days of Pegel watching itself

Our site, the status page and the mail relay from 2026-09-14 to 2026-11-12: three red days, uptime between 99.72 % and 99.81 %. The numbers per target are for members.

1 min

Sixty days of uptime bars for pegel.example.org, the status page and the mail relay. Day 12 is red for the first two, day 13 for the status page, day 41 for the mail relay.

Incident

arm64 downloads of v0.9.0 failed their checksum

For 13 hours after the release, pegel upgrade on arm64 stopped with a checksum error. The binary was fine, the checksum file was not. Two community packages still carry the old one.

Monitoring Major

Post

Why an alert needs two probes

From May to October, one probe on a home line sent us 121 false alarms. Two probes that had to agree sent one.

2 min

A diagram: probe home and probe vps each report down to a box labelled agree?, which points to example.org. An alert fires only when both probes see the outage.

Incident

Alert mails were held for four hours

On 2026-10-24 our mail relay accepted every mail and delivered none from 09:20 to 13:20 CEST. Webhook alerts reached us the whole time.

Resolved Minor

Post

Running Pegel on a Raspberry Pi

Pegel uses 23 MB of memory on a Raspberry Pi 4 checking 40 sites a minute. The compose file, and the two settings that spare the SD card.

1 min

A single-board computer with the label pegel-pi.
Buy Logbuch