banco: Allow inotify max user watches configuration
It prevented banco from properly working as a rancher agent once the postgresql backup started. This defaults to the future default value of the debian 12 suite.
The default value is 8192 on the nodes. Impacts the rancher production nodes (e.g. rancher-node-metal0*, banco, saam, ...) and the staging nodes too (storage1, rancher-node-staging-rke2-worker*, ...) with a similar plan [1].
[1] octo-diff banco
diff origin/production/banco.softwareheritage.org current/banco.softwareheritage.org
*******************************************
+ Exec[enforce-sysctl-value-fs.inotify.max_user_watches] =>
parameters =>
"command": "/sbin/sysctl -w fs.inotify.max_user_watches=1048576",
"unless": "/usr/bin/test \"$(/sbin/sysctl -n fs.inotify.max_user_watches)\" ...
*******************************************
+ Exec[sysctl-fs.inotify.max_user_watches] =>
parameters =>
"command": "sysctl -p /etc/sysctl.d/fs.inotify.max_user_watches.conf",
"path": [
"/usr/sbin",
"/sbin",
"/usr/bin",
"/bin"
],
"refreshonly": true
*******************************************
+ Exec[update-sysctl.conf-fs.inotify.max_user_watches] =>
parameters =>
"command": "sed -i -e 's#^fs.inotify.max_user_watches *=.*#fs.inotify.max_us...
"onlyif": "grep -E '^fs.inotify.max_user_watches *=' /etc/sysctl.conf",
"path": [
"/usr/sbin",
"/sbin",
"/usr/bin",
"/bin"
],
"refreshonly": true
*******************************************
+ File[/etc/sysctl.d/fs.inotify.max_user_watches.conf] =>
parameters =>
"content": "fs.inotify.max_user_watches = 1048576\n",
"group": "root",
"mode": "0644",
"notify": [
"Exec[sysctl-fs.inotify.max_user_watches]",
"Exec[update-sysctl.conf-fs.inotify.max_user_watches]"
],
"owner": "root"
*******************************************
+ Sysctl[fs.inotify.max_user_watches] =>
parameters =>
"enforce": true,
"suffix": ".conf",
"value": 1048576
*******************************************
*** End octocatalog-diff on banco.softwareheritage.org
+ set +x
/home/tony