Your message dated Mon, 13 May 2019 09:15:53 +0200
with message-id <[email protected]>
and subject line Re: Bug#928915: Full log unavailable with -e or -x
has caused the Debian Bug report #928915,
regarding systemd: Full log unavailable with -e or -x
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
928915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928915
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 242-1
Severity: normal

Dear Maintainer,

Different invocations of journalctl seem to display different amounts of the 
log.

$ sudo journalctl -xe
-- Logs begin at Sun 2019-05-12 20:37:51 EDT, end at Sun 2019-05-12 21:16:32 
EDT. --
ಮೇ 12 20:44:29 chiraag env[8395]: 
{"name":"log","hostname":"chiraag","pid":203,"level":30,"msg":"GET 
https://textsecure-service.whispersystems.org/

$ sudo journalctl -x
-- Logs begin at Sun 2019-05-12 20:37:51 EDT, end at Sun 2019-05-12 21:16:32 
EDT. --
ಮೇ 12 20:44:29 chiraag env[8395]: 
{"name":"log","hostname":"chiraag","pid":203,"level":30,"msg":"GET 
https://textsecure-service.whispersystems.org/

$ sudo journalctl -e
-- Logs begin at Sun 2019-05-12 20:37:51 EDT, end at Sun 2019-05-12 21:16:32 
EDT. --
ಮೇ 12 20:44:29 chiraag env[8395]: 
{"name":"log","hostname":"chiraag","pid":203,"level":30,"msg":"GET 
https://textsecure-service.whispersystems.org/

$ sudo journalctl
-- Logs begin at Sun 2019-05-12 20:37:51 EDT, end at Sun 2019-05-12 21:17:17 
EDT. --
ಮೇ 12 20:37:51 chiraag kernel: microcode: microcode updated early to revision 
0x9a, date = 2018-07-16

I included the first line only, but it should get the point across. I scrolled 
back up to the top with the invocations which include -e, so that's not the 
issue. Additionally, this seems to not be an issue if I use --unit to filter by 
regexp.

Sincerely,

Chiraag

-- Package-specific info:

-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.0.2-chiraag (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=kn_IN.UTF-8, LC_CTYPE=kn_IN.UTF-8 (charmap=UTF-8), 
LANGUAGE=kn_IN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd depends on:
ii  adduser          3.118
ii  libacl1          2.2.53-4
ii  libapparmor1     2.13.2-10
ii  libaudit1        1:2.8.4-3
ii  libblkid1        2.33.1-0.1
ii  libc6            2.28-10
ii  libcap2          1:2.25-2
ii  libcryptsetup12  2:2.2.0~rc0-1
ii  libgcrypt20      1.8.4-5
ii  libgnutls30      3.6.7-2
ii  libgpg-error0    1.36-1
ii  libidn2-0        2.0.5-1
ii  libip4tc0        1.8.2-4
ii  libkmod2         26-1
ii  liblz4-1         1.8.3-1
ii  liblzma5         5.2.4-1
ii  libmount1        2.33.1-0.1
ii  libpam0g         1.3.1-5
ii  libpcre2-8-0     10.32-5
ii  libseccomp2      2.3.3-4
ii  libselinux1      2.9-1
ii  libsystemd0      242-1
ii  mount            2.33.1-0.1
ii  util-linux       2.33.1-0.1

Versions of packages systemd recommends:
ii  dbus            1.13.8-1
ii  libpam-systemd  242-1

Versions of packages systemd suggests:
ii  policykit-1        0.116-1
pn  systemd-container  <none>

Versions of packages systemd is related to:
pn  dracut           <none>
ii  initramfs-tools  0.133
ii  udev             242-1

-- Configuration Files:
/etc/systemd/resolved.conf changed [not included]

-- no debconf information

--- End Message ---
--- Begin Message ---
Am 13.05.19 um 03:33 schrieb ಚಿರಾಗ್ ನಟರಾಜ್:
> Hmm, it seems there's been a change in behavior? Before I upgraded, I could 
> access the full log with -xe, but it seems that now -e implies -n1000?
> 

This is even documentend. See "man journalctl"

>       -e, --pager-end
>            Immediately jump to the end of the journal inside the implied pager
>            tool. This implies -n1000 to guarantee that the pager will not
>            buffer logs of unbounded size. 



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to