MariaDB issue fixed, but now we've some networking inforamation to do update too:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 8 2026
Access to Vault works fine, fetching secrets from there too, including after Terraform rotation.
Feb 7 2026
viperserv.nasqueron.org. 86400 IN AAAA 2001:470:1f13:9e1:0:c0ff:ee:7
Data imported from Ysul.
Roles is provisioned excepted the youtube-dl package, see T2214.
Vault credentials provisioned, eggdrop installed
Unit account done, next step: Vault credentials
Feb 5 2026
Feb 4 2026
Feb 3 2026
Jan 29 2026
Jan 25 2026
Was actually correctly configured in rOPS, but not deployed, so old version was still there.
Dec 15 2025
Dec 1 2025
Nov 28 2025
Alias photo.nasqueron.org → photos.nasqueron.org : Configuré et fonctionnel
Mounting the ZFS datasets mysql-innodb-data and mysql-innodb-logs outside of /var/db/mysql, then deploying them to db-B-001: operation completed and functional.
Nov 27 2025
Deployed on all FreeBSD servers with salt -G 'os:FreeBSD' state.apply roles/core/ntp
Nov 26 2025
Action plan
Activer ntpd : nécessaire si le serveur doit aussi servir de source horaire à d'autres machines.
Let's go for that road, even if it's only for the local machine.
Next: reconfigure DNS zone in HE control panel, as it only has our IPv4.
DNS server listens correctly to IPv6:
Nov 25 2025
Dans le cadre de mes activités du jour, j'ai travaillé avec mon maître de stage sur un problème de synchronisation horaire détecté sur le serveur db-B-001, qui présentait un décalage de deux heures.
Ce problème a été documenté dans le rapport d'incident suivant :
https://agora.nasqueron.org/Operations_grimoire/Incidents/2025-11-25-MariaDB
Nous avons analysé la configuration actuelle : la synchronisation NTP est gérée par les scripts périodiques situés dans :
ntpq log shows it only works to print statistics when ntpd is launched.
ntpq log: https://termbin.com/1vu4
Deployed on WindRiver.
Nov 24 2025
Avancement sur T2074
Nov 21 2025
Configuration is ready.
Nov 19 2025
Next step: deploy to docker-002, and ensure D3622 is already deployed there too.
@sandrined Could you publish the commit for this change for review?
Current status: deployed to Dwellers
Nov 18 2025
Nov 17 2025
Deployment on Dwellers