On Sun, Jul 21, 2019 at 11:48 PM Ulrich Windl
wrote:
>
> >>> Chris Murphy schrieb am 18.07.2019 um 17:55 in
> Nachricht
> :
> > On Thu, Jul 18, 2019 at 4:50 AM Uoti Urpala wrote:
> >>
> >> On Mon, 2019-07-15 at 14:32 -0600, Chris Murphy wrote:
> >> > So far nothing I've tried gets me access to i
On Fri, Jul 19, 2019 at 8:45 AM Uoti Urpala wrote:
>
> On Thu, 2019-07-18 at 21:52 -0600, Chris Murphy wrote:
> > # df -h
> > ...
> > /dev/mapper/live-rw 6.4G 5.7G 648M 91% /
> >
> > And in the log:
> > 47,19636,16754831,-;systemd-journald[905]: Fixed min_use=1.0M
> > max_use=648.7M max_size=8
On Thu, 2019-07-18 at 21:52 -0600, Chris Murphy wrote:
> # df -h
> ...
> /dev/mapper/live-rw 6.4G 5.7G 648M 91% /
>
> And in the log:
> 47,19636,16754831,-;systemd-journald[905]: Fixed min_use=1.0M
> max_use=648.7M max_size=81.0M min_size=512.0K keep_free=973.1M
> n_max_files=100
>
> Why is k
This is suspicious:
# df -h
...
/dev/mapper/live-rw 6.4G 5.7G 648M 91% /
And in the log:
47,19636,16754831,-;systemd-journald[905]: Fixed min_use=1.0M
max_use=648.7M max_size=81.0M min_size=512.0K keep_free=973.1M
n_max_files=100
Why is keep_free bigger than available free space? Is that the
On Thu, Jul 18, 2019 at 4:36 PM Greg Oliver wrote:
> I am assuming you have ripped apart the initramfs to see exactly how RedHat
> is invoking systemd in the live images?
I have not. No idea what I'd be looking for.
# ps aux | grep systemd
Installed system (Fedora 30):
root 1 0.0 0.
On Thu, Jul 18, 2019 at 4:02 PM Chris Murphy wrote:
>
> On Thu, Jul 18, 2019 at 10:18 AM Dave Howorth wrote:
> >
> > On Thu, 18 Jul 2019 09:55:51 -0600
> > Chris Murphy wrote:
> > > On Thu, Jul 18, 2019 at 4:50 AM Uoti Urpala
> > > wrote:
> > > >
> > > > On Mon, 2019-07-15 at 14:32 -0600, Chris
On Thu, Jul 18, 2019 at 5:02 PM Chris Murphy
wrote:
> On Thu, Jul 18, 2019 at 10:18 AM Dave Howorth
> wrote:
> >
> > On Thu, 18 Jul 2019 09:55:51 -0600
> > Chris Murphy wrote:
> > > On Thu, Jul 18, 2019 at 4:50 AM Uoti Urpala
> > > wrote:
> > > >
> > > > On Mon, 2019-07-15 at 14:32 -0600, Chri
On Thu, Jul 18, 2019 at 10:18 AM Dave Howorth wrote:
>
> On Thu, 18 Jul 2019 09:55:51 -0600
> Chris Murphy wrote:
> > On Thu, Jul 18, 2019 at 4:50 AM Uoti Urpala
> > wrote:
> > >
> > > On Mon, 2019-07-15 at 14:32 -0600, Chris Murphy wrote:
> > > > So far nothing I've tried gets me access to info
On Thu, 18 Jul 2019 09:55:51 -0600
Chris Murphy wrote:
> On Thu, Jul 18, 2019 at 4:50 AM Uoti Urpala
> wrote:
> >
> > On Mon, 2019-07-15 at 14:32 -0600, Chris Murphy wrote:
> > > So far nothing I've tried gets me access to information that would
> > > give a hint why systemd-journald thinks the
On Thu, Jul 18, 2019 at 4:50 AM Uoti Urpala wrote:
>
> On Mon, 2019-07-15 at 14:32 -0600, Chris Murphy wrote:
> > So far nothing I've tried gets me access to information that would
> > give a hint why systemd-journald thinks there's no free space and yet
> > it still decides to create a single 8MB
On Mon, 2019-07-15 at 14:32 -0600, Chris Murphy wrote:
> So far nothing I've tried gets me access to information that would
> give a hint why systemd-journald thinks there's no free space and yet
> it still decides to create a single 8MB system journal, which then
> almost immediately gets deleted,
This problem of missing early boot messages is now happening on a
default boot of Fedora Live images. I don't have to change any boot
parameters to trigger it.
This image:
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20190715.n.1/compose/Workstation/x86_64/iso/Fedora-Workstati
On Mon, Jul 15, 2019 at 2:32 PM Chris Murphy wrote:
>
> This is still a problem with systemd-242-5.git7a6d834.fc31.x86_64
>
> If I boot using 'systemd.journald.forward_to_console=1
> console=ttyS0,38400 console=tty1 systemd.log_level=debug rd.debug
> rd.udev.debug'
>
> There is no debug output for
On Mon, Jul 15, 2019 at 2:32 PM Chris Murphy wrote:
>
> If I boot using 'systemd.log_level=debug rd.debug rd.udev.debug
> systemd.log_target=kmsg log_buf_len=64M printk.devkmsg=on'
Another data point. Is kmsg dumped into a file is 5MiB, after the
point in time when journald had done vacuuming on
This is still a problem with systemd-242-5.git7a6d834.fc31.x86_64
If I boot using 'systemd.journald.forward_to_console=1
console=ttyS0,38400 console=tty1 systemd.log_level=debug rd.debug
rd.udev.debug'
There is no debug output forwarded to console, only kernel messages
and normal systemd logging
On Wed, Jun 19, 2019 at 6:15 AM Lennart Poettering
wrote:
>
> On Di, 18.06.19 20:34, Chris Murphy (li...@colorremedies.com) wrote:
>
> > When I boot Fedora 30/Rawhide Workstation (LiveOS install media) in a
> > VM with ~2GiB memory, using any combination of systemd, dracut, or
> > udev debugging,
On Di, 18.06.19 20:34, Chris Murphy (li...@colorremedies.com) wrote:
> When I boot Fedora 30/Rawhide Workstation (LiveOS install media) in a
> VM with ~2GiB memory, using any combination of systemd, dracut, or
> udev debugging, events are missing from the journal.
>
> systemd-241-7.gita2eaa1c.fc30
When I boot Fedora 30/Rawhide Workstation (LiveOS install media) in a
VM with ~2GiB memory, using any combination of systemd, dracut, or
udev debugging, events are missing from the journal.
systemd-241-7.gita2eaa1c.fc30.x86_64
systemd-242-3.git7a6d834.fc31.x86_64
'journalctl -b -o short-monotonic
18 matches
Mail list logo
