DGNum/infrastructure
10
5
Fork 3
Code Issues 31 Pull requests 30 Projects 1 Releases Packages Wiki Activity Actions

feat(ulogd): enabling ulogd #121

Merged
rlahfa merged 1 commit from :ulogd into main 2024-09-08 12:21:08 +02:00
Conversation 6 Commits 1 Files changed 2 +57
lbailly commented 2024-08-28 19:02:37 +02:00
Member
Copy link

ulogd indique qu'il n'arrive pas à parse le fichier de config, mais je ne trouve pas le problème

ulogd indique qu'il n'arrive pas à parse le fichier de config, mais je ne trouve pas le problème
rlahfa reviewed 2024-08-28 19:13:20 +02:00
machines/vault01/ulogd.nix Outdated
@ -0,0 +28,4 @@
postgresql = {
enable = true;
ensureUsers = [
{
rlahfa commented 2024-08-28 19:13:20 +02:00
Owner
Copy link

The root user is unnecessary

The `root` user is unnecessary
lbailly commented 2024-08-28 20:42:28 +02:00
Author
Member
Copy link

I removed the root user in the database.

I removed the root user in the database.
lbailly marked this conversation as resolved
rlahfa reviewed 2024-08-28 19:13:37 +02:00
machines/vault01/ulogd.nix Outdated
@ -0,0 +32,4 @@
name = "root";
ensureClauses.superuser = true;
}
{
rlahfa commented 2024-08-28 19:13:37 +02:00
Owner
Copy link

ulogd user is unnecessary as ulogd may require root privileges for now

`ulogd` user is unnecessary as ulogd may require `root` privileges for now
lbailly commented 2024-08-28 20:37:28 +02:00
Author
Member
Copy link

we need a user to access the database, and I'm not willing to use the 'postgres' user for such operations

we need a user to access the database, and I'm not willing to use the 'postgres' user for such operations
rlahfa marked this conversation as resolved
rlahfa reviewed 2024-08-28 19:14:24 +02:00
machines/vault01/ulogd.nix Outdated
@ -0,0 +21,4 @@
user = "\"root\"";
table = "\"ulog2_ct\"";
procedure = "\"INSERT_CT\"";
pass = "\"changeme\"";
rlahfa commented 2024-08-28 19:14:24 +02:00
Owner
Copy link

connstring = "postgresql:///ulogd?host=/run/postgresql"; should work in principle

`connstring = "postgresql:///ulogd?host=/run/postgresql";` should work in principle
lbailly commented 2024-08-28 20:40:41 +02:00
Author
Member
Copy link

it doesn't want a connection URI, but really a connection string, as in section 31.1.1.1. of the postgres doc. In the end, I just don't give network connection information and it behave as expected.

it doesn't want a connection URI, but really a connection string, as in section 31.1.1.1. of the [postgres doc](https://www.postgresql.org/docs/9.2/libpq-connect.html#LIBPQ-CONNSTRING). In the end, I just don't give network connection information and it behave as expected.
rlahfa marked this conversation as resolved
lbailly commented 2024-08-28 20:41:45 +02:00
Author
Member
Copy link

Normalement tout est bon dans la config now, il reste éventuellement à ajouter des stacks si les logs sont insufisant.

Normalement tout est bon dans la config now, il reste éventuellement à ajouter des stacks si les logs sont insufisant.
lbailly changed title from WIP: feat(ulogd): enabling ulogd to feat(ulogd): enabling ulogd 2024-08-28 20:41:47 +02:00
thubrecht reviewed 2024-08-28 20:46:13 +02:00
machines/vault01/ulogd.nix Outdated
@ -0,0 +44,4 @@
};
systemd.services.postgresql = {
preStart = lib.mkAfter ''
if test -e "${config.services.postgresql.dataDir}/.first_startup"; then
thubrecht commented 2024-08-28 20:46:13 +02:00
Owner
Copy link

Je ne pense pas que ça fasse ce que tu veux

Je ne pense pas que ça fasse ce que tu veux
lbailly commented 2024-08-28 21:20:21 +02:00
Author
Member
Copy link

Le but c'est que le script ne soit exec que quand le serveur s'initialise, il suppr toute les données.
Je peux pas utiliser .first_statup car il est suppr au tout début de postStart, ducoup je recréer le flag.

Le but c'est que le script ne soit exec que quand le serveur s'initialise, il suppr toute les données. Je peux pas utiliser .first_statup car il est suppr au tout début de postStart, ducoup je recréer le flag.
thubrecht commented 2024-08-29 00:57:25 +02:00
Owner
Copy link

Mais en pratique ça ne tourne jamais donc je vois pas trop l'intérêt de le mettre

Mais en pratique ça ne tourne jamais donc je vois pas trop l'intérêt de le mettre
lbailly commented 2024-08-29 01:00:30 +02:00
Author
Member
Copy link

si on doit redéployer un routeur avec log, on aura le nécessaire dans le module sans avoir à recheck comment deploy ulogd, sinon le ensureUsers et ensureDatabases ne servent pas non plus...

si on doit redéployer un routeur avec log, on aura le nécessaire dans le module sans avoir à recheck comment deploy ulogd, sinon le `ensureUsers` et `ensureDatabases` ne servent pas non plus...
lbailly commented 2024-08-29 01:29:29 +02:00
Author
Member
Copy link

En vérité, il faudrait plutôt check l'existence des tables pour le cas où le module est déployé sur une machine qui a déjà un pgsql, mais bon...

En vérité, il faudrait plutôt check l'existence des tables pour le cas où le module est déployé sur une machine qui a déjà un pgsql, mais bon...
thubrecht commented 2024-08-29 13:26:14 +02:00
Owner
Copy link

Oui, ou alors faire un preStart dans l'unit de ulogd en sauvegardant le state dans var/lib/ulogd, dans ce cas on pourra charger les tables lors de la première activation du module

Oui, ou alors faire un preStart dans l'unit de ulogd en sauvegardant le state dans `var/lib/ulogd`, dans ce cas on pourra charger les tables lors de la première activation du module
thubrecht reviewed 2024-08-29 13:26:59 +02:00
machines/vault01/ulogd.nix Outdated
@ -0,0 +8,4 @@
services = {
ulogd = {
enable = true;
logLevel = 5;
thubrecht commented 2024-08-29 13:26:59 +02:00
Owner
Copy link

Si ça fonctionne désormais ce n'est pas la peine d'activer les logs de debug, à part spammer journald

Si ça fonctionne désormais ce n'est pas la peine d'activer les logs de debug, à part spammer journald
lbailly commented 2024-09-07 12:22:06 +02:00
Author
Member
Copy link

D'après la doc, 5 correspond au niveau notice de log, 1 serai debug. Si tu veux on peut monter à 7 pour avoir que les erreurs.

D'après [la doc](https://search.nixos.org/options?channel=unstable&show=services.ulogd.logLevel), 5 correspond au niveau notice de log, 1 serai debug. Si tu veux on peut monter à 7 pour avoir que les erreurs.
rlahfa merged commit 3b766e6a2b into main 2024-09-08 12:21:08 +02:00
dgnum-chores referenced this pull request from a commit 2025-06-12 15:01:17 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-13 14:57:26 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-14 14:59:08 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-15 14:59:12 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-16 14:58:59 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-17 14:59:10 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-18 14:58:20 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-19 14:58:07 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-20 15:00:09 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-21 14:58:58 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-22 14:57:31 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-23 14:58:40 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-24 14:58:15 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-25 14:58:10 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-26 14:58:20 +02:00
lon: update proxmox-nixos
mdebray referenced this pull request from a commit 2025-06-26 15:13:29 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-27 14:57:55 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-28 14:59:06 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-29 14:59:08 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-06-30 14:59:20 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-07-01 14:59:02 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-07-02 14:58:53 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-07-03 14:59:04 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-07-04 14:58:29 +02:00
lon: update proxmox-nixos
dgnum-chores referenced this pull request from a commit 2025-07-05 14:58:44 +02:00
lon: update proxmox-nixos
thubrecht referenced this pull request from a commit 2025-07-06 11:47:22 +02:00
lon: update proxmox-nixos
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
awaiting
awaiting-author
Awaiting for the author interaction (e.g. QA/confirmation/final merge)

  
awaiting
awaiting-reviewer
Awaiting for a privileged reviewer to approve this PR

  
bot

Pull Request opened by a bot

  
deployed

This PR is currently deployed on the infra

  
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No labels
awaiting
awaiting-author
awaiting
awaiting-reviewer
bot
deployed
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: DGNum/infrastructure#121
No description provided.
Delete branch ":ulogd"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?