touch-packages team mailing list archive

[dino99 <1437574@xxxxxxxxxxxxxxxxxx>]

old issue

** Changed in: systemd (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1437574

Title:
  systemd-journald[221]: Failed to create new system journal: No such
  file or directory

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Get this logged into syslog:

  systemd-journald[221]: /var/log/journal/efe9c2428e64e7a70a91277254016fe6/system.journal: Journal file has been deleted, rotating.
   kernel: [ 4647.247581] systemd-journald[221]: Failed to create new system journal: No such file or directory

  from freedesktop doc:
  By default, the journal stores log data in /run/log/journal/. Since /run/ is volatile, log data is lost at reboot. To make the data persistent, it is sufficient to create /var/log/journal/ where systemd-journald will then store the data.

  so i've created /var/log/journal/ subdir, and the data is well stored (owner:root, group:systemd-journal). But i've seen that data continue to be added every cold boot after every cold boot. That gives mixed session data, which seems not the best way to get easy readable session's data log. So now i delete /var/log/journal/* before shutdown to get a clean new journal on next cold boot session.
  But then the error above is logged, even if the journal is created in fact. So it's like a false positive error.

  What systemd should do:
  - rotate itself each journal's session instead of concataning all the data inside /var/log/journal/ like other logs

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sat Mar 28 08:01:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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