touch-packages team mailing list archive

[kenjo <ken@xxxxxxxxx>]

Public bug reported:

so the manual say this..
---
       If called without parameters, it will show the full contents of the journal, starting with the oldest entry collected.
---

This is not happening for me. if I do the following command

journalctl | grep [program name]

I get less output than if I do

journalctl _COMM=[program name]


My guess is that this is happening for the same reason that my previous bug where --list-boots did not work. 

Namely there seems to be a major problem when the log is corrupted and
things behave inconsistently.

journalctl --verify

shows several corruptions but that should not make this type of
inconsistent behavior. The systemd people have said repeatedly that
there is no need for a repair tool and that systemd can handle
corruptions just fine. Not my experience.

Now the reason I get corruptions is probably due to unreliable
suspend/resume where resume is not working an a power cycle is needed.
This is not a uncommon thing suspend/resume just is not gong to be 100%
and people are going to end up with journal that is corrupted.

Note that the copy I get in syslog contain all the output I get when I
run journalctl with the _COMM option.

systemd journal handling needs to improve substantial so it can handle
corruption better and at least be consistent with itself.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-7ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
Uname: Linux 3.19.0-14-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Apr 17 15:59:13 2015
InstallationDate: Installed on 2015-04-09 (7 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
MachineType: Apple Inc. MacBookPro11,2
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-14-generic.efi.signed root=UUID=f84ca03e-c0d4-45ad-80f3-c45d4ad106dd ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7
SourcePackage: systemd
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/07/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP112.88Z.0138.B14.1501071031
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-3CBD00234E554E41
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-3CBD00234E554E41
dmi.modalias: dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B14.1501071031:bd01/07/2015:svnAppleInc.:pnMacBookPro11,2:pvr1.0:rvnAppleInc.:rnMac-3CBD00234E554E41:rvrMacBookPro11,2:cvnAppleInc.:ct10:cvrMac-3CBD00234E554E41:
dmi.product.name: MacBookPro11,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug vivid

-- 
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/1445512

Title:
  journalctl not showing all content in the log.

Status in systemd package in Ubuntu:
  New

Bug description:
  so the manual say this..
  ---
         If called without parameters, it will show the full contents of the journal, starting with the oldest entry collected.
  ---

  This is not happening for me. if I do the following command

  journalctl | grep [program name]

  I get less output than if I do

  journalctl _COMM=[program name]

  
  My guess is that this is happening for the same reason that my previous bug where --list-boots did not work. 

  Namely there seems to be a major problem when the log is corrupted and
  things behave inconsistently.

  journalctl --verify

  shows several corruptions but that should not make this type of
  inconsistent behavior. The systemd people have said repeatedly that
  there is no need for a repair tool and that systemd can handle
  corruptions just fine. Not my experience.

  Now the reason I get corruptions is probably due to unreliable
  suspend/resume where resume is not working an a power cycle is needed.
  This is not a uncommon thing suspend/resume just is not gong to be
  100% and people are going to end up with journal that is corrupted.

  Note that the copy I get in syslog contain all the output I get when I
  run journalctl with the _COMM option.

  systemd journal handling needs to improve substantial so it can handle
  corruption better and at least be consistent with itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 17 15:59:13 2015
  InstallationDate: Installed on 2015-04-09 (7 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  MachineType: Apple Inc. MacBookPro11,2
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-14-generic.efi.signed root=UUID=f84ca03e-c0d4-45ad-80f3-c45d4ad106dd ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B14.1501071031
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-3CBD00234E554E41
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-3CBD00234E554E41
  dmi.modalias: dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B14.1501071031:bd01/07/2015:svnAppleInc.:pnMacBookPro11,2:pvr1.0:rvnAppleInc.:rnMac-3CBD00234E554E41:rvrMacBookPro11,2:cvnAppleInc.:ct10:cvrMac-3CBD00234E554E41:
  dmi.product.name: MacBookPro11,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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