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
Sun, Feb 8
Access to Vault works fine, fetching secrets from there too, including after Terraform rotation.
Sat, Feb 7
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
Fri, Feb 6
Sun, Jan 25
Was actually correctly configured in rOPS, but not deployed, so old version was still there.
Dec 15 2025
Dec 1 2025
Nov 28 2025
Mail bien reçu : `
ARC-Authentication-Results: i=1; mx.google.com;
spf=pass (google.com: domain of mediawiki-saas-no-reply@nasqueron.org designates 2001:41d0:303:d971::517e:c0de as permitted sender) smtp.mailfrom=mediawiki-saas-no-reply@nasqueron.org
Return-Path: <mediawiki-saas-no-reply@nasqueron.org>
Received: from web-001.nasqueron.drake (www-alkane.nasqueron.org. [2001:41d0:303:d971::517e:c0de])
by mx.google.com with ESMTP id ffacd0b85a97d-42e1ca54633si1934360f8f.947.2025.11.28.03.09.59 for <doba.guimartinien@gmail.com>; Fri, 28 Nov 2025 03:10:00 -0800 (PST)
Received-SPF: pass (google.com: domain of mediawiki-saas-no-reply@nasqueron.org designates 2001:41d0:303:d971::517e:c0de as permitted sender) client-ip=2001:41d0:303:d971::517e:c0de;
Authentication-Results: mx.google.com;
spf=pass (google.com: domain of mediawiki-saas-no-reply@nasqueron.org designates 2001:41d0:303:d971::517e:c0de as permitted sender) smtp.mailfrom=mediawiki-saas-no-reply@nasqueron.org
Received: from mediawiki (uid 3004) (envelope-from mediawiki-saas-no-reply@nasqueron.org) id 1fd73 by web-001.nasqueron.drake (DragonFly Mail Agent v0.13+ on web-001.nasqueron.drake); Fri, 28 Nov 2025 11:09:58 +0000
SPF updated for nasqueron.org domain to allow web-001:
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.
DNS record for SPF, TXT version, didn't include the IPs of web-001, now it's the case with D3892 (propagation still pending to nsX.he.net)
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
Nov 23 2025
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 15 2025
Nov 13 2025
Nov 12 2025
Wiki account created. Password should have been sent by e-mail.
Nov 11 2025
Deployed for WindRiver, server now runs on 17.6.