Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Following snapshot 20200914 error "Failed to start Apply Kernel Variables"

  1. #1
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,554

    Default Following snapshot 20200914 error "Failed to start Apply Kernel Variables"

    Both my TW machines now throw "Failed to start Apply Kernel Variables" error upon boot following snapshot 20200914

    From the journal, this appears to be due to:

    Code:
    Sep 16 11:23:54 Orion-15 systemd-sysctl[409]: Couldn't write '"0 2147483647" to' to 'net/ipv4/ping_group_range': Invalid argument
    Sep 16 11:23:54 Orion-15 systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
    Sep 16 11:23:54 Orion-15 systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.
    Sep 16 11:23:54 Orion-15 systemd[1]: Failed to start Apply Kernel Variables.
    Raised a bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1176592
    Regards, Paul

    2x Tumbleweed (Snapshot: 20201019) KDE Plasma 5
    2x Leap 15.2 KDE Plasma 5

  2. #2
    Join Date
    Oct 2014
    Location
    Switzerland
    Posts
    745

    Default Re: Following snapshot 20200914 error "Failed to start Apply Kernel Variables"

    Quote Originally Posted by tannington View Post
    Both my TW machines now throw "Failed to start Apply Kernel Variables" error upon boot following snapshot 20200914

    From the journal, this appears to be due to:

    Code:
    Sep 16 11:23:54 Orion-15 systemd-sysctl[409]: Couldn't write '"0 2147483647" to' to 'net/ipv4/ping_group_range': Invalid argument
    Sep 16 11:23:54 Orion-15 systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
    Sep 16 11:23:54 Orion-15 systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.
    Sep 16 11:23:54 Orion-15 systemd[1]: Failed to start Apply Kernel Variables.
    Raised a bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1176592
    I was getting the same thing. I removed the quotation marks in
    Code:
     /usr/lib/sysctl.d/50-default.conf
    from the line that contains
    Code:
    net.ipv4.ping_group_range = "0 2147483647"
    to
    Code:
    net.ipv4.ping_group_range = 0 2147483647
    and everything seems to be working fine.

  3. #3
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,554

    Default Re: Following snapshot 20200914 error "Failed to start Apply Kernel Variables"

    Yes, it seems this was already known about: https://bugzilla.opensuse.org/show_bug.cgi?id=1174504

    However I didn't find that report when I searched earlier ....
    Regards, Paul

    2x Tumbleweed (Snapshot: 20201019) KDE Plasma 5
    2x Leap 15.2 KDE Plasma 5

  4. #4
    Join Date
    Oct 2014
    Location
    Switzerland
    Posts
    745

    Default Re: Following snapshot 20200914 error "Failed to start Apply Kernel Variables"

    Quote Originally Posted by tannington View Post
    Yes, it seems this was already known about: https://bugzilla.opensuse.org/show_bug.cgi?id=1174504

    However I didn't find that report when I searched earlier ....
    I did not see that bug report before I came to a same conclusion but well, everyone can miss something.

  5. #5

    Default Re: Following snapshot 20200914 error "Failed to start Apply Kernel Variables"

    I'm having this issue, as well. But I used nano to remove the quotes from the specified line in /usr/lib/sysctl.d/50-default.conf, and it doesn't seem to have fixed the issue.

    My error message in the log (via journalctl):

    Code:
    Sep 16 16:01:05 linux-vsbp systemd[1]: Starting Apply Kernel Variables...
    Sep 16 16:01:05 linux-vsbp systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
    Sep 16 16:01:05 linux-vsbp systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.
    Sep 16 16:01:05 linux-vsbp systemd[1]: Failed to start Apply Kernel Variables.
    Sep 16 16:01:05 linux-vsbp systemd-journald[182]: Journal started
    Sep 16 16:01:05 linux-vsbp systemd-journald[182]: Runtime Journal (/run/log/journal/5e233e6dd4e445bcb6c29f64293ec9dc) is 8.0M, max 395.5M, 387.5M free.
    Sep 16 16:01:05 linux-vsbp systemd-modules-load[183]: Inserted module 'scsi_dh_alua'
    Sep 16 16:01:05 linux-vsbp haveged[180]: haveged: command socket is listening at fd 3
    Sep 16 16:01:05 linux-vsbp systemd-modules-load[183]: Inserted module 'scsi_dh_emc'
    Sep 16 16:01:05 linux-vsbp systemd-modules-load[183]: Inserted module 'scsi_dh_rdac'
    Sep 16 16:01:05 linux-vsbp systemd-modules-load[183]: Inserted module 'dm_multipath'
    Sep 16 16:01:05 linux-vsbp systemd-modules-load[183]: Inserted module 'sg'
    Sep 16 16:01:05 linux-vsbp systemd-sysctl[194]: Couldn't write '"0 2147483647"' to 'net/ipv4/ping_group_range': Invalid argument
    My file via sudo nano /usr/lib/sysctl.d/50-default.conf

    Code:
    net.ipv4.ping_group_range = 0 2147483647
    How am I still having the error?

    And what effect can it have on my system?

  6. #6

    Default Re: Following snapshot 20200914 error "Failed to start Apply Kernel Variables"

    I had/have the same issue. In addition to removing quotation marks in 50-default.conf I updated initramfs image and errors disappeared from logs.
    In a nutshell, in addition to solution posted by SJLPHI I ran:
    Code:
    sudo mkinitrd

  7. #7
    Join Date
    Oct 2014
    Location
    Switzerland
    Posts
    745

    Default Re: Following snapshot 20200914 error "Failed to start Apply Kernel Variables"

    Quote Originally Posted by siim80 View Post
    I had/have the same issue. In addition to removing quotation marks in 50-default.conf I updated initramfs image and errors disappeared from logs.
    In a nutshell, in addition to solution posted by SJLPHI I ran:
    Code:
    sudo mkinitrd
    Yes, recompiling is necessary, sorry, I neglected to mention that.

  8. #8
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    1,903
    Blog Entries
    1

    Default Re: Following snapshot 20200914 error "Failed to start Apply Kernel Variables"

    Users may choose to copy file /usr/lib/sysctl.d/50-default.conf to /etc/sysctl.d/50-default.conf and edit the latter. As a bonus systemd-delta lists the changes made:

    Code:
    erlangen:~ # systemd-delta --type overridden 
    [OVERRIDDEN] /etc/sysctl.d/50-default.conf → /usr/lib/sysctl.d/50-default.conf
    
    --- /usr/lib/sysctl.d/50-default.conf   2020-09-09 08:49:33.000000000 +0200
    +++ /etc/sysctl.d/50-default.conf       2020-09-17 09:49:55.651527076 +0200
    @@ -29,7 +29,7 @@
     # bits (bsc#1174504).
     # this only allows users to handle ICMP ECHO REQUESTs and REPLYs, nothing
     # else.
    -net.ipv4.ping_group_range = "0 2147483647"
    +net.ipv4.ping_group_range = 0 2147483647
     
     # increase the number of possible inotify(7) watches
     fs.inotify.max_user_watches = 65536
    ...
    3 overridden configuration files found.
    erlangen:~ #
    Running 'dracut -f' completes the fix.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  9. #9

    Default Re: Following snapshot 20200914 error "Failed to start Apply Kernel Variables"

    Has this been fixed already upstream or better to wait some days before next zypper dup? Not interested in reviving all TWs right now... ;-)
    Kind regards

    raspu

  10. #10
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,554

    Default Re: Following snapshot 20200914 error "Failed to start Apply Kernel Variables"

    Quote Originally Posted by suse_rasputin View Post
    Has this been fixed already upstream or better to wait some days before next zypper dup? Not interested in reviving all TWs right now... ;-)
    In progress... https://bugzilla.opensuse.org/show_bug.cgi?id=1174504
    Regards, Paul

    2x Tumbleweed (Snapshot: 20201019) KDE Plasma 5
    2x Leap 15.2 KDE Plasma 5

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •