Pi 3 98-rpi.conf bug in new update

[DNPNWO]

Did 'apt-get upgrade', noticed a boot fail error for "apply kernel variables", troubleshot it, and determined that there was what appears to be some poor coding work done in /etc/sysctl.d/98-rpi.conf (regarding "echo 16384 > /proc/sys/vm/min_free_kbytes", and/or Adjusting vm.swappiness and vm.min_free_kbytes ) which was replaced in the update.

Restoring original file contents, resolved failure.

Code: Select all

Linux version 4.4.13-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #894 SMP Mon Jun 13 13:13:27  2016

Updated:

Code: Select all

 libmysqlclient18 mysql-common python-gpiozero python3-gpiozero
  raspberrypi-sys-mods sonic-pi

Code: Select all

(Reading database ... 157590 files and directories currently installed.)
Preparing to unpack .../mysql-common_5.5.52-0+deb8u1_all.deb ...
Unpacking mysql-common (5.5.52-0+deb8u1) over (5.5.50-0+deb8u1) ...
Preparing to unpack .../libmysqlclient18_5.5.52-0+deb8u1_armhf.deb ...
Unpacking libmysqlclient18:armhf (5.5.52-0+deb8u1) over (5.5.50-0+deb8u1) ...
Preparing to unpack .../raspberrypi-sys-mods_20160915_armhf.deb ...
Removing old /etc/sysctl.d/98-rpi.conf...
Adjusting vm.swappiness and vm.min_free_kbytes...
Unpacking raspberrypi-sys-mods (20160915) over (20160426) ...
Preparing to unpack .../python-gpiozero_1.3.1_all.deb ...
Unpacking python-gpiozero (1.3.1) over (1.2.0) ...
Preparing to unpack .../python3-gpiozero_1.3.1_all.deb ...
Unpacking python3-gpiozero (1.3.1) over (1.2.0) ...
Preparing to unpack .../sonic-pi_1%3a2.10.0-2_armhf.deb ...
Unpacking sonic-pi (1:2.10.0-2) over (1:2.10.0-1) ...
Processing triggers for gnome-menus (3.13.3-6) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for mime-support (3.58) ...
Setting up mysql-common (5.5.52-0+deb8u1) ...
Setting up libmysqlclient18:armhf (5.5.52-0+deb8u1) ...
Setting up raspberrypi-sys-mods (20160915) ...
Setting up python-gpiozero (1.3.1) ...
Setting up python3-gpiozero (1.3.1) ...
Setting up sonic-pi (1:2.10.0-2) ...
Enabling /etc/security/limits.d/audio.conf for jackd2
Processing triggers for libc-bin (2.19-18+deb8u4) ...

Error (persistent following reboot):
[Failed] failed to start apply kernel variables

Code: Select all

systemctl status systemd-sysctl.service

Code: Select all

● systemd-sysctl.service - Apply Kernel Variables
   Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static)
   Active: failed (Result: exit-code) since Thu 2016-09-15 16:24:02 GMT; 20min ago
     Docs: man:systemd-sysctl.service(8)
           man:sysctl.d(5)
  Process: 131 ExecStart=/lib/systemd/systemd-sysctl (code=exited, status=1/FAILURE)
 Main PID: 131 (code=exited, status=1/FAILURE)

Issue:

Code: Select all

raspberrypi-sys-mods

Code: Select all

/etc/sysctl.d/98-rpi.conf

From:

Code: Select all

kernel.printk = 3 4 1 3
vm.swappiness=1
vm.min_free_kbytes = 8192

To:

Code: Select all

kernel.printk = 3 4 1 3
echo 16384 > /proc/sys/vm/min_free_kbytes

Restoring original file content, resolves kernel boot fail error.

Code: Select all

systemctl status systemd-sysctl.service

Code: Select all

● systemd-sysctl.service - Apply Kernel Variables
   Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static)
   Active: active (exited) since Fri 2016-09-16 10:03:19 GMT; 8min ago
     Docs: man:systemd-sysctl.service(8)
           man:sysctl.d(5)
  Process: 132 ExecStart=/lib/systemd/systemd-sysctl (code=exited, status=0/SUCCESS)
 Main PID: 132 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/systemd-sysctl.service

[DNPNWO]

Looks like this issue is being discussed here: https://github.com/RPi-Distro/raspberry ... s/issues/1

[schwarzr]

I can confirm the issue, looks quite seriously. Did you noticed any significant impacts or consequences ?

[DNPNWO]

I can confirm the issue, looks quite seriously. Did you noticed any significant impacts or consequences ?

I restored my backup almost immediately. S I am fine.

[ShiftPlusOne]

I can confirm the issue, looks quite seriously. Did you noticed any significant impacts or consequences ?

No real negative consequences. A fixed version should hit the repo soon, so an apt-get update && apt-get upgrade should fix it in about half an hour. Just waiting for the load balancers to pick up the update.

[schwarzr]

@ShiftPlusOne
Ok, thanks