sysctl items not persisting after reboot on Ubuntu 20.04

Aaron Jones retro64xyz at gmail.com
Fri Aug 19 12:18:50 MST 2022


https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093

Does this bug seem applicable?

> On Aug 19, 2022, at 10:05 AM, Shawn Badger via PLUG-discuss <plug-discuss at lists.phxlinux.org> wrote:
> 
> 
> It is called 99-bridge.conf and is applied correctly on the restart of the procps.
> 
> 
>> On Fri, Aug 19, 2022 at 10:03 AM Aaron Jones via PLUG-discuss <plug-discuss at lists.phxlinux.org> wrote:
>> What is the name of the sysctl files? You may want to try renaming them something like zzz-mysysctlstuff.conf to make sure they aren’t being over written to start? Or are they already named high enough in the order so it’s a moot point?
>> 
>> > On Aug 19, 2022, at 9:52 AM, Shawn Badger via PLUG-discuss <plug-discuss at lists.phxlinux.org> wrote:
>> > 
>> > 
>> > I am running into an odd issue where config files placed in /etc/sysctl.d/ are not being read on reboot, but after restarting procps they load as expected.
>> > 
>> > root at dd:/home/user# sysctl -a |grep net.bridge
>> > net.bridge.bridge-nf-call-arptables = 1
>> > net.bridge.bridge-nf-call-ip6tables = 1
>> > net.bridge.bridge-nf-call-iptables = 1
>> > net.bridge.bridge-nf-filter-pppoe-tagged = 0
>> > net.bridge.bridge-nf-filter-vlan-tagged = 0
>> > net.bridge.bridge-nf-pass-vlan-input-dev = 0
>> > root at dd:/home/user# systemctl restart procps
>> > root at dd:/home/user# sysctl -a |grep net.bridge
>> > net.bridge.bridge-nf-call-arptables = 0
>> > net.bridge.bridge-nf-call-ip6tables = 0
>> > net.bridge.bridge-nf-call-iptables = 0
>> > net.bridge.bridge-nf-filter-pppoe-tagged = 0
>> > net.bridge.bridge-nf-filter-vlan-tagged = 0
>> > net.bridge.bridge-nf-pass-vlan-input-dev = 0
>> > 
>> > I have done 
>> > # systemctl restart procps
>> > # sysctl -p
>> > 
>> > a few times and rebooted without success. I have even done systemctl daemon-reload in hopes of having systemd reread the files.
>> > My Google Fu is failing on finding a solution that works. Does anyone have an idea why the restart of procps applies the changes but doesn't apply them on startup?
>> > Yes, the procps service is enabled and is running before I do the restart.
>> > 
>> > Thanks
>> > 
>> > ---------------------------------------------------
>> > PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>> > To subscribe, unsubscribe, or to change your mail settings:
>> > https://lists.phxlinux.org/mailman/listinfo/plug-discuss
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>> To subscribe, unsubscribe, or to change your mail settings:
>> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20220819/63964acf/attachment.html>


More information about the PLUG-discuss mailing list