mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 11:46:35 +00:00
kevinveenbirkenbachandClaude Opus 5.5
fa91d1763b
The nfs-ganesha drop-in sets Environment="OPTIONS=-L SYSLOG ...", but the Debian and Ubuntu unit (upstream nfs-ganesha.service.debian8) also reads EnvironmentFile=-/etc/default/nfs-ganesha, whose OPTIONS name -L /var/log/ganesha/ganesha.log, and systemd lets EnvironmentFile= override Environment=. So on those distros ganesha logged to a file with no bound, while CentOS, Fedora and Arch already logged to the journal (SystemMaxUse=256M on the lab node). Under MODE_DEBUG ganesha.conf raised NFS_V4 to DEBUG sincea085427236, which writes a dozen lines per NFS compound. In odoo#1 of run 40625679270 (debian) the nfs-server node grew 12.6 GB above the control node and the step aborted at "DISK EXHAUSTION IMMINENT (<6144M free on /)". In the same run, nodes logging to the journal grew 0.8 to 1.6 GB in four hours, nodes logging to the file 4.4 to 12.6 GB. - The drop-in resets EnvironmentFile= before setting OPTIONS. The Debian unit's ExecStart reads nothing else from that file (its journal reports EPOCH, GNODEID, NUMACTL and NUMAOPTS as referenced but unset). - NFS_V4 goes back to the default level: it was raised to chase the probe-write bug that9b7f25f2fefixed. DISPATCH stays at DEBUG, since nfs_Init_svc(), which binds 2049, logs under it (1aea8a472e). - The swarm diagnostics read the last 600 journal lines of nfs-ganesha instead of the file tail. test_ganesha_log_levels and test_ganesha_unit_options pin the debug components and the drop-in's OPTIONS source; against the previous template and drop-in both fail. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>