Remove LimitNOFile increases as it is a bug in virtiofsd
This commit is contained in:
parent
2331e0dad5
commit
d8c0110ebc
|
@ -221,15 +221,7 @@
|
||||||
# Do not break the boot
|
# Do not break the boot
|
||||||
enableEmergencyMode = false;
|
enableEmergencyMode = false;
|
||||||
|
|
||||||
services = {
|
services.nix-daemon.serviceConfig.KillMode = "control-group";
|
||||||
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;
|
|
||||||
};
|
|
||||||
};
|
|
||||||
|
|
||||||
# Reboot on hang
|
# Reboot on hang
|
||||||
watchdog = lib.mkIf (!config.boot.isContainer) {
|
watchdog = lib.mkIf (!config.boot.isContainer) {
|
||||||
|
|
|
@ -110,14 +110,8 @@ in
|
||||||
|
|
||||||
systemd = {
|
systemd = {
|
||||||
services = {
|
services = {
|
||||||
restic-backups-server8.serviceConfig = {
|
restic-backups-server8.serviceConfig.Environment = "RESTIC_PROGRESS_FPS=0.016666";
|
||||||
Environment = "RESTIC_PROGRESS_FPS=0.016666";
|
restic-backups-offsite.serviceConfig.Environment = "RESTIC_PROGRESS_FPS=0.016666";
|
||||||
LimitNOFile = 1024*32;
|
|
||||||
};
|
|
||||||
restic-backups-offsite.serviceConfig = {
|
|
||||||
Environment = "RESTIC_PROGRESS_FPS=0.016666";
|
|
||||||
LimitNOFile = 1024*32;
|
|
||||||
};
|
|
||||||
};
|
};
|
||||||
timers = lib.mkIf config.services.postgresqlBackup.enable {
|
timers = lib.mkIf config.services.postgresqlBackup.enable {
|
||||||
postgresqlBackup.timerConfig.RandomizedDelaySec = "5m";
|
postgresqlBackup.timerConfig.RandomizedDelaySec = "5m";
|
||||||
|
|
Loading…
Reference in New Issue