** Description changed:

  This issue was spotted on one of our server, during the upgrade process
- this message came up.
+ this message came up, I didn't know if there is anything that's not
+ working due to this error, so far it looks good.
  
  $ sudo systemctl status systemd-sysctl.service
  ● systemd-sysctl.service - Apply Kernel Variables
-    Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static; vendor 
preset: enabled)
-    Active: failed (Result: exit-code) since Fri 2018-01-26 06:33:11 UTC; 
46min ago
-      Docs: man:systemd-sysctl.service(8)
-            man:sysctl.d(5)
-   Process: 1088 ExecStart=/lib/systemd/systemd-sysctl (code=exited, 
status=1/FAILURE)
-  Main PID: 1088 (code=exited, status=1/FAILURE)
+    Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static; vendor 
preset: enabled)
+    Active: failed (Result: exit-code) since Fri 2018-01-26 06:33:11 UTC; 
46min ago
+      Docs: man:systemd-sysctl.service(8)
+            man:sysctl.d(5)
+   Process: 1088 ExecStart=/lib/systemd/systemd-sysctl (code=exited, 
status=1/FAILURE)
+  Main PID: 1088 (code=exited, status=1/FAILURE)
  
  Jan 26 06:33:11 jenkins2 systemd[1]: Starting Apply Kernel Variables...
  Jan 26 06:33:11 jenkins2 systemd[1]: systemd-sysctl.service: Main process 
exited, code=exited, status=1/FAILURE
  Jan 26 06:33:11 jenkins2 systemd[1]: Failed to start Apply Kernel Variables.
  Jan 26 06:33:11 jenkins2 systemd[1]: systemd-sysctl.service: Unit entered 
failed state.
  Jan 26 06:33:11 jenkins2 systemd[1]: systemd-sysctl.service: Failed with 
result 'exit-code'.
  
  Please find the attachment for the /etc/sysctl.conf file (identical to
  /etc/sysctl.d/99-sysctl.conf).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-83-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: N/A
  Date: Fri Jan 26 06:30:21 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  JournalErrors:
-  Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
-        Users in the 'systemd-journal' group can see all messages. Pass -q to
-        turn off this notice.
-  No journal files were opened due to insufficient permissions.
+  Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
+        Users in the 'systemd-journal' group can see all messages. Pass -q to
+        turn off this notice.
+  No journal files were opened due to insufficient permissions.
  MachineType: Intel Corporation S2600WTT
  PciMultimedia:
-  
+ 
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=<set>
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=<set>
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB:
-  
+ 
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=9a5914ff-0d81-4f66-962f-e747a85cad59 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-83-generic N/A
-  linux-backports-modules-4.4.0-83-generic  N/A
-  linux-firmware                            N/A
+  linux-restricted-modules-4.4.0-83-generic N/A
+  linux-backports-modules-4.4.0-83-generic  N/A
+  linux-firmware                            N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
-  
+ 
  dmi.bios.date: 03/19/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SE5C610.86B.01.01.1008.031920151331
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S2600WTT
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G92187-350
  dmi.chassis.asset.tag: ....................
  dmi.chassis.type: 23
  dmi.chassis.vendor: ...............................
  dmi.chassis.version: ..................
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.1008.031920151331:bd03/19/2015:svnIntelCorporation:pnS2600WTT:pvr....................:rvnIntelCorporation:rnS2600WTT:rvrG92187-350:cvn...............................:ct23:cvr..................:
  dmi.product.name: S2600WTT
  dmi.product.version: ....................
  dmi.sys.vendor: Intel Corporation

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745560

Title:
  systemd-sysctl.service complains "Failed to start Apply Kernel
  Variables"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745560/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to