Time.lan.nurd.space: Difference between revisions

From NURDspace
Jump to navigation Jump to search
 
(7 intermediate revisions by the same user not shown)
Line 23: Line 23:
== where? ==
== where? ==


Currently (2026/03/30) it is on a shelf next to the serverrack in the old printer-corner.
Currently (2026/04/29) it is on the RF shelf CV-closet.
 
[[File:Time.lan.nurd.space.png|640px]]


== who? ==
== who? ==


This thing is managed by [[folkert]] & [[melan]].
This thing is managed by [[folkert]] & [[User:Melan]].


== specs ==
== specs ==
Line 49: Line 47:
*** realtime kernel
*** realtime kernel
*** preemptible kernel
*** preemptible kernel
* it (the pi) is also the "emergency"-gateway for when the regular internet connection is not available


* CPU clock frequency scaling has been disabled as scaling negatively affects time keeping
* CPU clock frequency scaling has been disabled as scaling negatively affects time keeping
Line 60: Line 56:
* ntpviz has been installed (part of ntpsec), see http://10.208.0.10/ntpviz/
* ntpviz has been installed (part of ntpsec), see http://10.208.0.10/ntpviz/
* every minute the script /root/bin/monitor-ntp-traffic.sh is invoked by cron. The script reads the iptables-rule statistics (an ACCEPT rule added by a @reboot-rule in the root-crontab) and sends those values to influx.vm.nurd.space:2012 (a graphite receiver for the influx NTP database). This data is graphed at metrics.nurd.space (grafana): https://metrics.nurd.space/d/bfhlkmlss8d1ca/time-lan-nurd-space?orgId=1&from=now-24h&to=now&timezone=browser&refresh=5s Also the temperature is monitored by monitor-sys-temp.sh
* every minute the script /root/bin/monitor-ntp-traffic.sh is invoked by cron. The script reads the iptables-rule statistics (an ACCEPT rule added by a @reboot-rule in the root-crontab) and sends those values to influx.vm.nurd.space:2012 (a graphite receiver for the influx NTP database). This data is graphed at metrics.nurd.space (grafana): https://metrics.nurd.space/d/bfhlkmlss8d1ca/time-lan-nurd-space?orgId=1&from=now-24h&to=now&timezone=browser&refresh=5s Also the temperature is monitored by monitor-sys-temp.sh
* lastly it runs ntp-evaluator: http://10.208.0.10:5000/
== other task ==
It also functions as an internet-gateway via UMTS to (currently only) Folkert's VPS (172.31.0.1 via vps001.komputilo.nl). That allows us to reach the space when regular internet is unavailable. Soon the time-pi will be on an UPS fo extended power when main power is gone.
It also runs a local [[uptime kuma]] instance which only monitors the physical servers ([[erratic]], [[melody]], [[sporadic]] and [[spacenanny]]). Notifications of these go through the vpn to Folkert's XMPP server.
=== TODO ===
* connect an ESP to it (via USB) which monitors the regular main power. then we can check from remote if the power went down.
* setup vpn to Melan
* setup xmpp for [[r3boot]]
* setup some other messenger for Melan

Latest revision as of 23:26, 29 April 2026

time - THE time-source for NURDSpace
Time.lan.nurd.space pica.png
Participants
Skills ntp, gps, ptp
Status In progress
Niche Time
Purpose Use for infra
Tool Yes
Location bij de bar
Cost
Tool category General

time - THE time-source for NURDSpace

Time.lan.nurd.space pica.png {{#if:Yes | [[Tool Owner::{{{ProjectParticipants}}} | }} {{#if:Yes | [[Tool Cost::{{{Cost}}} | }}


what it is

This is the main time server for NURDSpace. "Connect" using NTP (or SNTP) - most (if not all) operating systems support NTP in some form.

And as we have UNLIMITED (well almost) internet bandwidth, it is also part of https://www.ntppool.org/ (configured at half a megabit).

pro tip

On ESP32, do not use some vague NTP library: the IDF/Arduino SDK on that platform contains a very capable NTP implementation by itself (google for configTime).

where?

Currently (2026/04/29) it is on the RF shelf CV-closet.

who?

This thing is managed by folkert & User:Melan.

specs

  • gpsd - GPS: GY-GPSV3-NEO-M8N GNSS-GPS Module
  • ntpsec

networking

  • hostname: time.lan.nurd.space
  • ip-adress: 10.208.0.10

notes

  • the system runs a special 'realtime kernel', please be careful not to replace it when updating raspberryos!
    • special settings:
      • 100 Hz interrupt
      • nohz=off
      • realtime kernel
      • preemptible kernel
  • CPU clock frequency scaling has been disabled as scaling negatively affects time keeping

monitoring

other task

It also functions as an internet-gateway via UMTS to (currently only) Folkert's VPS (172.31.0.1 via vps001.komputilo.nl). That allows us to reach the space when regular internet is unavailable. Soon the time-pi will be on an UPS fo extended power when main power is gone. It also runs a local uptime kuma instance which only monitors the physical servers (erratic, melody, sporadic and spacenanny). Notifications of these go through the vpn to Folkert's XMPP server.

TODO

  • connect an ESP to it (via USB) which monitors the regular main power. then we can check from remote if the power went down.
  • setup vpn to Melan
  • setup xmpp for r3boot
  • setup some other messenger for Melan