Remove LimitNOFile increases as it is a bug in virtiofsd

This commit is contained in:
Sandro - 2023-05-18 22:11:12 +02:00
parent 2331e0dad5
commit d8c0110ebc
Signed by: sandro
GPG Key ID: 3AF5A43A3EECC2E5
2 changed files with 3 additions and 17 deletions

View File

@ -221,15 +221,7 @@
# Do not break the boot
enableEmergencyMode = false;
services = {
nix-daemon.serviceConfig.KillMode = "control-group";
postgresql = lib.mkIf config.services.postgresql.enable {
# default is 1024 which was not enough for mastodon and leading to errors like the following which crash postgresql:
# could not close file "./global/176529": Too many open files
serviceConfig.LimitNOFile = 1024*32;
};
};
services.nix-daemon.serviceConfig.KillMode = "control-group";
# Reboot on hang
watchdog = lib.mkIf (!config.boot.isContainer) {

View File

@ -110,14 +110,8 @@ in
systemd = {
services = {
restic-backups-server8.serviceConfig = {
Environment = "RESTIC_PROGRESS_FPS=0.016666";
LimitNOFile = 1024*32;
};
restic-backups-offsite.serviceConfig = {
Environment = "RESTIC_PROGRESS_FPS=0.016666";
LimitNOFile = 1024*32;
};
restic-backups-server8.serviceConfig.Environment = "RESTIC_PROGRESS_FPS=0.016666";
restic-backups-offsite.serviceConfig.Environment = "RESTIC_PROGRESS_FPS=0.016666";
};
timers = lib.mkIf config.services.postgresqlBackup.enable {
postgresqlBackup.timerConfig.RandomizedDelaySec = "5m";