search

withfig / fig

Public issue tracker for Fig.
https://fig.io
MIT License
2.06k stars 63 forks source link

bug: journalctl log with millions of lines from within a fraction of a day! #2265

Open schrmh opened 1 year ago

schrmh commented 1 year ago

Checks

Operating system

Arch Linux x86_64

Expected behaviour

Normal log behaviour NOT filling up the whole journalctl (at best non of these specific log entries cause I don't want them in my journalctl at all due to lack of importance for me)

Actual behaviour

Similar to #1666, it got to my log file limits within a short time (and those are low, so it might have been worse if they were higher!)

journalctl contains 6807120 times lines like Jan 27 09:31:20 myhost fig[7429]: 2023-01-27T08:31:20.905547Z ERROR fig_cli::daemon: 162: Error while connecting to websocket: Serde error: EOF while parsing a value at line 1 column 0 (took almost two minutes to wc -l that) And everything is from today! If I grep -v that, I'm left with 1515 other entries.

/var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e:$ ls -latrSh

drwxr-sr-x+ 4 root systemd-journal 4,0K  6. Sep 2017  ..
drwxr-sr-x+ 2 root systemd-journal  24K 27. Jan 13:33 .
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 11:17 system@02eca81960364bfc9e02668c29b162cf-0000000002bf3cf3-0005f33c156e501f.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 09:36 system@02eca81960364bfc9e02668c29b162cf-0000000002949191-0005f33aaf324eba.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 10:58 system@02eca81960364bfc9e02668c29b162cf-0000000002b73cd2-0005f33bd2d03a04.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 10:27 system@02eca81960364bfc9e02668c29b162cf-0000000002a9e741-0005f33b640971d3.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 12:16 system@02eca81960364bfc9e02668c29b162cf-0000000002d73d4a-0005f33ce67e6f5e.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 12:35 system@02eca81960364bfc9e02668c29b162cf-0000000002df3d63-0005f33d2c01d47f.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 09:43 system@02eca81960364bfc9e02668c29b162cf-0000000002973c45-0005f33ac4d8a8e9.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 10:08 system@02eca81960364bfc9e02668c29b162cf-0000000002a1e717-0005f33b1ff935d6.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 11:56 system@02eca81960364bfc9e02668c29b162cf-0000000002cf3d31-0005f33ca0d01262.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 10:15 system@02eca81960364bfc9e02668c29b162cf-0000000002a491cd-0005f33b35ea8cb0.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 13:26 system@02eca81960364bfc9e02668c29b162cf-0000000002f49313-0005f33de43082c0.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 11:37 system@02eca81960364bfc9e02668c29b162cf-0000000002c73d18-0005f33c5b20e706.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 09:55 system@02eca81960364bfc9e02668c29b162cf-00000000029c91b6-0005f33af1b02c2e.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 12:41 system@02eca81960364bfc9e02668c29b162cf-0000000002e1e80a-0005f33d433b75f3.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 11:11 system@02eca81960364bfc9e02668c29b162cf-0000000002bc923e-0005f33bff7c6fbc.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 10:46 system@02eca81960364bfc9e02668c29b162cf-0000000002b1e772-0005f33ba5fbc77a.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 13:01 system@02eca81960364bfc9e02668c29b162cf-0000000002e9e832-0005f33d87a0658c.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 11:50 system@02eca81960364bfc9e02668c29b162cf-0000000002cc927b-0005f33c8995aedd.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 10:52 system@02eca81960364bfc9e02668c29b162cf-0000000002b4921c-0005f33bbc14e866.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 12:22 system@02eca81960364bfc9e02668c29b162cf-0000000002d9e7f1-0005f33cfdb856ba.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 10:02 system@02eca81960364bfc9e02668c29b162cf-00000000029f3c5f-0005f33b08bef743.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 11:24 system@02eca81960364bfc9e02668c29b162cf-0000000002c1e7a6-0005f33c2caca3c0.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 13:20 system@02eca81960364bfc9e02668c29b162cf-0000000002f1e85b-0005f33dccf63c6e.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 13:14 system@02eca81960364bfc9e02668c29b162cf-0000000002ef3da3-0005f33db5bbe5b0.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 12:54 system@02eca81960364bfc9e02668c29b162cf-0000000002e73d7a-0005f33d7062e941.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 12:09 system@02eca81960364bfc9e02668c29b162cf-0000000002d49292-0005f33ccf43ccf4.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 12:03 system@02eca81960364bfc9e02668c29b162cf-0000000002d1e7da-0005f33cb80ae83c.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 11:04 system@02eca81960364bfc9e02668c29b162cf-0000000002b9e786-0005f33be86be665.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 13:33 system@02eca81960364bfc9e02668c29b162cf-0000000002f73dbb-0005f33dfb3fe5c1.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 12:48 system@02eca81960364bfc9e02668c29b162cf-0000000002e492bf-0005f33d592e3332.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 13:07 system@02eca81960364bfc9e02668c29b162cf-0000000002ec92e8-0005f33d9eac39e6.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 11:30 system@02eca81960364bfc9e02668c29b162cf-0000000002c4925e-0005f33c43e4ba4c.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 12:29 system@02eca81960364bfc9e02668c29b162cf-0000000002dc92a9-0005f33d14c6948f.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 11:43 system@02eca81960364bfc9e02668c29b162cf-0000000002c9e7c1-0005f33c725b0cc4.journal
-rw-r-----+ 1 root systemd-journal 3,6M 27. Jan 10:39 system@02eca81960364bfc9e02668c29b162cf-0000000002af3cb6-0005f33b8f409d55.journal
-rw-r-----+ 1 root systemd-journal 3,7M 27. Jan 09:49 system@02eca81960364bfc9e02668c29b162cf-000000000299e6f8-0005f33ada747a4a.journal
-rw-r-----+ 1 root systemd-journal 3,7M 27. Jan 10:33 system@02eca81960364bfc9e02668c29b162cf-0000000002ac91f5-0005f33b79a5bca6.journal
-rw-r-----+ 1 root systemd-journal 3,7M 27. Jan 10:21 system@02eca81960364bfc9e02668c29b162cf-0000000002a73c81-0005f33b4cf9b8ed.journal
-rw-r-----+ 1 root systemd-journal 8,0M 27. Jan 13:33 system.journal
-rw-r-----+ 1 root systemd-journal  40M 27. Jan 13:34 user-1000.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 13:26 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002f49312-0005f33de42aa26b.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 12:35 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002df3d62-0005f33d2bfbdca5.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 12:16 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002d73d49-0005f33ce678cd93.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 11:56 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002cf3d30-0005f33ca0c8fd69.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 11:37 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002c73d17-0005f33c5b1a4a51.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 10:46 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002b1e771-0005f33ba5f5bfba.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 09:55 user-1000@2bddd6884dd2473caf45e372c206b268-00000000029c91b5-0005f33af1aa4d49.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 13:33 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002f73dba-0005f33dfb39de44.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 13:20 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002f1e85a-0005f33dccf091c2.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 13:14 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002ef3da2-0005f33db5b56587.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 13:07 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002ec92e7-0005f33d9ea6e656.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 13:01 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002e9e831-0005f33d8796c47f.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 12:54 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002e73d79-0005f33d705c894f.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 12:48 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002e492be-0005f33d59285c36.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 12:41 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002e1e809-0005f33d4335fe4a.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 12:29 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002dc92a8-0005f33d14c1200f.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 12:22 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002d9e7f0-0005f33cfdb24947.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 12:09 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002d49291-0005f33ccf3d7a31.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 12:03 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002d1e7d9-0005f33cb8049510.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 11:50 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002cc927a-0005f33c898fa4a3.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 11:43 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002c9e7c0-0005f33c72546ea7.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 11:30 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002c4925d-0005f33c43df355a.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 11:24 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002c1e7a5-0005f33c2ca60972.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 11:17 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002bf3cf2-0005f33c156836cf.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 11:11 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002bc923d-0005f33bff773b28.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 11:04 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002b9e785-0005f33be866b714.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 10:58 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002b73cd1-0005f33bd2cb625a.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 10:52 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002b4921b-0005f33bbc100a7f.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 10:39 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002af3cb5-0005f33b8f3bb9b0.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 10:33 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002ac91f4-0005f33b79a03958.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 10:27 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002a9e740-0005f33b640442a2.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 10:21 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002a73c80-0005f33b4cf467f0.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 10:15 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002a491cc-0005f33b35e504f4.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 10:08 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002a1e716-0005f33b1ff3c523.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 10:02 user-1000@2bddd6884dd2473caf45e372c206b268-00000000029f3c5e-0005f33b08b9370f.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 09:49 user-1000@2bddd6884dd2473caf45e372c206b268-000000000299e6f7-0005f33ada6edf2b.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 09:43 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002973c44-0005f33ac4d3484a.journal
-rw-r-----+ 1 root systemd-journal 103M 27. Jan 09:36 user-1000@2bddd6884dd2473caf45e372c206b268-0000000002949190-0005f33aaf2d68c7.journal

Also looks like I got logged out from fig within just a few days of installing it: fig doctor

✘ Logged into Fig: Not logged in. Run `fig login` to login.

error: Not logged in. Run `fig login` to login.

After fig restart the log file filling continued for a few minutes until it started printing less of the lines (every few minutes one). Also I noticed those two lines that got written to my journalctl log after I cleared it and looked at the new log

Jan 27 14:05:52 myhost fig_desktop[49118]: 2023-01-27T13:05:52.245717Z ERROR fig_desktop: 104: failed to init global state err=EOF while parsing a value at line 1 column 0
Jan 27 14:05:52 myhost fig_desktop[49118]: 2023-01-27T13:05:52.243924Z ERROR fig_settings: 264:  Failed to load json file into global backend err=EOF while parsing a value at line 1 column 0 file_content=Ok("")

Steps to reproduce

judging by dmesg output, it started pretty soon after wakeup by suspend2hibernation.service which failed to hibernate my system (before I cleared dmesg log, which was a few minutes before I ran systemctl suspend, I had nothing regarding reaching log file limits in it). /etc/systemd/system/suspend2hibernation.service

[Unit]
Description=Suspend to hibernation / delayed hibernation
Documentation=https://bbs.archlinux.org/viewtopic.php?pid=1420279#p1420279
Documentation=https://wiki.archlinux.org/index.php/Power_management
Before=suspend.target
Conflicts=hibernate.target hybrid-sleep.target
StopWhenUnneeded=true

[Service]
Type=oneshot
RemainAfterExit=yes
Environment="WAKEALARM=/sys/class/rtc/rtc0/wakealarm"
Environment="SLEEPLENGTH=+20minute"
ExecStart=-/usr/bin/sh -c 'echo -n "alarm set for "; date +%%s -d$SLEEPLENGTH | tee $WAKEALARM'
ExecStop=-/usr/bin/sh -c '\
  alarm=$(cat $WAKEALARM); \
  now=$(date +%%s); \
  if [ -z "$alarm" ] || [ "$now" -ge "$alarm" ]; then \
     echo "hibernate triggered"; \
     systemctl hibernate; \
  else \
     echo "normal wakeup"; \
  fi; \
  echo 0 > $WAKEALARM; \
'

[Install]
WantedBy=sleep.target

dmesg -T

[Fr, 27. Jan 2023, 09:29:17] audit: type=1130 audit(1674806958.135:4466): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fr, 27. Jan 2023, 09:29:17] wlan0: deauthenticating from 38:10:d5:71:22:56 by local choice (Reason: 3=DEAUTH_LEAVING)
[Fr, 27. Jan 2023, 09:29:18] audit: type=1131 audit(1674806958.705:4467): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ntpd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fr, 27. Jan 2023, 09:29:18] audit: type=1130 audit(1674806958.901:4468): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=suspend2hibernation comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fr, 27. Jan 2023, 09:29:18] PM: suspend entry (deep)
[Fr, 27. Jan 2023, 09:29:18] Filesystems sync: 0.057 seconds
[Fr, 27. Jan 2023, 09:29:18] Freezing user space processes ... (elapsed 0.012 seconds) done.
[Fr, 27. Jan 2023, 09:29:18] OOM killer disabled.
[Fr, 27. Jan 2023, 09:29:18] Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
[Fr, 27. Jan 2023, 09:29:18] printk: Suspending console(s) (use no_console_suspend to debug)
[Fr, 27. Jan 2023, 09:29:18] sd 4:0:0:0: [sdd] Synchronizing SCSI cache
[Fr, 27. Jan 2023, 09:29:18] sd 5:0:0:0: [sde] Synchronizing SCSI cache
[Fr, 27. Jan 2023, 09:29:18] sd 11:0:0:0: [sdf] Synchronizing SCSI cache
[Fr, 27. Jan 2023, 09:29:18] sd 11:0:0:0: [sdf] Stopping disk
[Fr, 27. Jan 2023, 09:29:18] sd 4:0:0:0: [sdd] Stopping disk
[Fr, 27. Jan 2023, 09:29:18] sd 5:0:0:0: [sde] Stopping disk
[Fr, 27. Jan 2023, 09:29:18] sd 3:0:0:0: [sdc] Synchronizing SCSI cache
[Fr, 27. Jan 2023, 09:29:18] sd 2:0:0:0: [sdb] Synchronizing SCSI cache
[Fr, 27. Jan 2023, 09:29:18] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[Fr, 27. Jan 2023, 09:29:18] sd 2:0:0:0: [sdb] Stopping disk
[Fr, 27. Jan 2023, 09:29:18] sd 0:0:0:0: [sda] Stopping disk
[Fr, 27. Jan 2023, 09:29:18] sd 3:0:0:0: [sdc] Stopping disk
[Fr, 27. Jan 2023, 09:29:19] amdgpu 0000:2b:00.0: amdgpu: PCI CONFIG reset
[Fr, 27. Jan 2023, 09:29:19] ACPI: PM: Preparing to enter system sleep state S3
[Fr, 27. Jan 2023, 09:29:19] ACPI: PM: Saving platform NVS memory
[Fr, 27. Jan 2023, 09:29:19] Disabling non-boot CPUs ...
[Fr, 27. Jan 2023, 09:29:19] smpboot: CPU 1 is now offline
[Fr, 27. Jan 2023, 09:29:19] smpboot: CPU 2 is now offline
[Fr, 27. Jan 2023, 09:29:19] smpboot: CPU 3 is now offline
[Fr, 27. Jan 2023, 09:29:20] smpboot: CPU 4 is now offline
[Fr, 27. Jan 2023, 09:29:20] smpboot: CPU 5 is now offline
[Fr, 27. Jan 2023, 09:29:20] smpboot: CPU 6 is now offline
[Fr, 27. Jan 2023, 09:29:20] smpboot: CPU 7 is now offline
[Fr, 27. Jan 2023, 09:29:20] smpboot: CPU 8 is now offline
[Fr, 27. Jan 2023, 09:29:20] smpboot: CPU 9 is now offline
[Fr, 27. Jan 2023, 09:29:20] smpboot: CPU 10 is now offline
[Fr, 27. Jan 2023, 09:29:20] smpboot: CPU 11 is now offline
[Fr, 27. Jan 2023, 09:29:20] smpboot: CPU 12 is now offline
[Fr, 27. Jan 2023, 09:29:20] smpboot: CPU 13 is now offline
[Fr, 27. Jan 2023, 09:29:20] smpboot: CPU 14 is now offline
[Fr, 27. Jan 2023, 09:29:20] smpboot: CPU 15 is now offline
[Fr, 27. Jan 2023, 09:29:20] ACPI: PM: Low-level resume complete
[Fr, 27. Jan 2023, 09:29:20] ACPI: PM: Restoring platform NVS memory
[Fr, 27. Jan 2023, 09:29:20] LVT offset 0 assigned for vector 0x400
[Fr, 27. Jan 2023, 09:29:20] Enabling non-boot CPUs ...
[Fr, 27. Jan 2023, 09:29:20] x86: Booting SMP configuration:
[Fr, 27. Jan 2023, 09:29:20] smpboot: Booting Node 0 Processor 1 APIC 0x2
[Fr, 27. Jan 2023, 09:29:20] microcode: CPU1: patch_level=0x08701021
[Fr, 27. Jan 2023, 09:29:20] ACPI: \_SB_.PLTF.C002: Found 2 idle states
[Fr, 27. Jan 2023, 09:29:20] CPU1 is up
[Fr, 27. Jan 2023, 09:29:20] smpboot: Booting Node 0 Processor 2 APIC 0x4
[Fr, 27. Jan 2023, 09:29:20] microcode: CPU2: patch_level=0x08701021
[Fr, 27. Jan 2023, 09:29:20] ACPI: \_SB_.PLTF.C004: Found 2 idle states
[Fr, 27. Jan 2023, 09:29:20] CPU2 is up
[Fr, 27. Jan 2023, 09:29:20] smpboot: Booting Node 0 Processor 3 APIC 0x6
[Fr, 27. Jan 2023, 09:29:20] microcode: CPU3: patch_level=0x08701021
[Fr, 27. Jan 2023, 09:29:20] ACPI: \_SB_.PLTF.C006: Found 2 idle states
[Fr, 27. Jan 2023, 09:29:20] CPU3 is up
[Fr, 27. Jan 2023, 09:29:20] smpboot: Booting Node 0 Processor 4 APIC 0x8
[Fr, 27. Jan 2023, 09:29:20] microcode: CPU4: patch_level=0x08701021
[Fr, 27. Jan 2023, 09:29:20] ACPI: \_SB_.PLTF.C008: Found 2 idle states
[Fr, 27. Jan 2023, 09:29:20] CPU4 is up
[Fr, 27. Jan 2023, 09:29:20] smpboot: Booting Node 0 Processor 5 APIC 0xa
[Fr, 27. Jan 2023, 09:29:20] microcode: CPU5: patch_level=0x08701021
[Fr, 27. Jan 2023, 09:29:20] ACPI: \_SB_.PLTF.C00A: Found 2 idle states
[Fr, 27. Jan 2023, 09:29:20] CPU5 is up
[Fr, 27. Jan 2023, 09:29:20] smpboot: Booting Node 0 Processor 6 APIC 0xc
[Fr, 27. Jan 2023, 09:29:20] microcode: CPU6: patch_level=0x08701021
[Fr, 27. Jan 2023, 09:29:20] ACPI: \_SB_.PLTF.C00C: Found 2 idle states
[Fr, 27. Jan 2023, 09:29:20] CPU6 is up
[Fr, 27. Jan 2023, 09:29:20] smpboot: Booting Node 0 Processor 7 APIC 0xe
[Fr, 27. Jan 2023, 09:29:20] microcode: CPU7: patch_level=0x08701021
[Fr, 27. Jan 2023, 09:29:20] ACPI: \_SB_.PLTF.C00E: Found 2 idle states
[Fr, 27. Jan 2023, 09:29:20] CPU7 is up
[Fr, 27. Jan 2023, 09:29:20] smpboot: Booting Node 0 Processor 8 APIC 0x1
[Fr, 27. Jan 2023, 09:29:20] microcode: CPU8: patch_level=0x08701021
[Fr, 27. Jan 2023, 09:29:20] ACPI: \_SB_.PLTF.C001: Found 2 idle states
[Fr, 27. Jan 2023, 09:29:20] CPU8 is up
[Fr, 27. Jan 2023, 09:29:20] smpboot: Booting Node 0 Processor 9 APIC 0x3
[Fr, 27. Jan 2023, 09:29:20] microcode: CPU9: patch_level=0x08701021
[Fr, 27. Jan 2023, 09:29:20] ACPI: \_SB_.PLTF.C003: Found 2 idle states
[Fr, 27. Jan 2023, 09:29:20] CPU9 is up
[Fr, 27. Jan 2023, 09:29:20] smpboot: Booting Node 0 Processor 10 APIC 0x5
[Fr, 27. Jan 2023, 09:29:20] microcode: CPU10: patch_level=0x08701021
[Fr, 27. Jan 2023, 09:29:20] ACPI: \_SB_.PLTF.C005: Found 2 idle states
[Fr, 27. Jan 2023, 09:29:20] CPU10 is up
[Fr, 27. Jan 2023, 09:29:20] smpboot: Booting Node 0 Processor 11 APIC 0x7
[Fr, 27. Jan 2023, 09:29:20] microcode: CPU11: patch_level=0x08701021
[Fr, 27. Jan 2023, 09:29:20] ACPI: \_SB_.PLTF.C007: Found 2 idle states
[Fr, 27. Jan 2023, 09:29:20] CPU11 is up
[Fr, 27. Jan 2023, 09:29:20] smpboot: Booting Node 0 Processor 12 APIC 0x9
[Fr, 27. Jan 2023, 09:29:20] microcode: CPU12: patch_level=0x08701021
[Fr, 27. Jan 2023, 09:29:20] ACPI: \_SB_.PLTF.C009: Found 2 idle states
[Fr, 27. Jan 2023, 09:29:20] CPU12 is up
[Fr, 27. Jan 2023, 09:29:20] smpboot: Booting Node 0 Processor 13 APIC 0xb
[Fr, 27. Jan 2023, 09:29:20] microcode: CPU13: patch_level=0x08701021
[Fr, 27. Jan 2023, 09:29:20] ACPI: \_SB_.PLTF.C00B: Found 2 idle states
[Fr, 27. Jan 2023, 09:29:20] CPU13 is up
[Fr, 27. Jan 2023, 09:29:20] smpboot: Booting Node 0 Processor 14 APIC 0xd
[Fr, 27. Jan 2023, 09:29:20] microcode: CPU14: patch_level=0x08701021
[Fr, 27. Jan 2023, 09:29:20] ACPI: \_SB_.PLTF.C00D: Found 2 idle states
[Fr, 27. Jan 2023, 09:29:20] CPU14 is up
[Fr, 27. Jan 2023, 09:29:20] smpboot: Booting Node 0 Processor 15 APIC 0xf
[Fr, 27. Jan 2023, 09:29:20] microcode: CPU15: patch_level=0x08701021
[Fr, 27. Jan 2023, 09:29:20] ACPI: \_SB_.PLTF.C00F: Found 2 idle states
[Fr, 27. Jan 2023, 09:29:20] CPU15 is up
[Fr, 27. Jan 2023, 09:29:20] ACPI: PM: Waking up from system sleep state S3
[Fr, 27. Jan 2023, 09:29:20] hpet: Lost 7805 RTC interrupts
[Fr, 27. Jan 2023, 09:29:20] xhci_hcd 0000:02:00.0: xHC error in resume, USBSTS 0x401, Reinit
[Fr, 27. Jan 2023, 09:29:20] usb usb1: root hub lost power or was reset
[Fr, 27. Jan 2023, 09:29:20] usb usb2: root hub lost power or was reset
[Fr, 27. Jan 2023, 09:29:20] sd 11:0:0:0: [sdf] Starting disk
[Fr, 27. Jan 2023, 09:29:20] sd 3:0:0:0: [sdc] Starting disk
[Fr, 27. Jan 2023, 09:29:20] sd 2:0:0:0: [sdb] Starting disk
[Fr, 27. Jan 2023, 09:29:20] sd 5:0:0:0: [sde] Starting disk
[Fr, 27. Jan 2023, 09:29:20] sd 0:0:0:0: [sda] Starting disk
[Fr, 27. Jan 2023, 09:29:20] sd 4:0:0:0: [sdd] Starting disk
[Fr, 27. Jan 2023, 09:29:20] ata2: SATA link down (SStatus 0 SControl 300)
[Fr, 27. Jan 2023, 09:29:20] usb 1-8: reset full-speed USB device number 4 using xhci_hcd
[Fr, 27. Jan 2023, 09:29:20] ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fr, 27. Jan 2023, 09:29:20] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fr, 27. Jan 2023, 09:29:20] ata12.00: supports DRM functions and may not be fully accessible
[Fr, 27. Jan 2023, 09:29:20] ata1.00: supports DRM functions and may not be fully accessible
[Fr, 27. Jan 2023, 09:29:20] [drm] PCIE GART of 256M enabled (table at 0x000000F400800000).
[Fr, 27. Jan 2023, 09:29:20] ata1.00: supports DRM functions and may not be fully accessible
[Fr, 27. Jan 2023, 09:29:20] ata12.00: supports DRM functions and may not be fully accessible
[Fr, 27. Jan 2023, 09:29:20] ata1.00: configured for UDMA/133
[Fr, 27. Jan 2023, 09:29:20] ata12.00: configured for UDMA/133
[Fr, 27. Jan 2023, 09:29:20] ata12.00: Enabling discard_zeroes_data
[Fr, 27. Jan 2023, 09:29:20] usb 1-7: reset high-speed USB device number 3 using xhci_hcd
[Fr, 27. Jan 2023, 09:29:21] usb 1-9: reset full-speed USB device number 7 using xhci_hcd
[Fr, 27. Jan 2023, 09:29:21] [drm] Fence fallback timer expired on ring sdma0
[Fr, 27. Jan 2023, 09:29:21] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fr, 27. Jan 2023, 09:29:21] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fr, 27. Jan 2023, 09:29:21] ata3.00: configured for UDMA/133
[Fr, 27. Jan 2023, 09:29:21] usb 1-3: reset low-speed USB device number 2 using xhci_hcd
[Fr, 27. Jan 2023, 09:29:21] ata4.00: configured for UDMA/100
[Fr, 27. Jan 2023, 09:29:21] [drm] Fence fallback timer expired on ring sdma0
[Fr, 27. Jan 2023, 09:29:22] usb 1-7.2: reset full-speed USB device number 5 using xhci_hcd
[Fr, 27. Jan 2023, 09:29:22] [drm] Fence fallback timer expired on ring sdma0
[Fr, 27. Jan 2023, 09:29:22] [drm] Fence fallback timer expired on ring sdma0
[Fr, 27. Jan 2023, 09:29:23] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fr, 27. Jan 2023, 09:29:23] ata6.00: configured for UDMA/133
[Fr, 27. Jan 2023, 09:29:23] [drm] Fence fallback timer expired on ring sdma0
[Fr, 27. Jan 2023, 09:29:23] [drm] Fence fallback timer expired on ring sdma0
[Fr, 27. Jan 2023, 09:29:24] [drm] Fence fallback timer expired on ring sdma0
[Fr, 27. Jan 2023, 09:29:24] [drm] Fence fallback timer expired on ring sdma0
[Fr, 27. Jan 2023, 09:29:25] [drm] Fence fallback timer expired on ring sdma0
[Fr, 27. Jan 2023, 09:29:25] ata5: found unknown device (class 0)
[Fr, 27. Jan 2023, 09:29:25] [drm] Fence fallback timer expired on ring sdma0
[Fr, 27. Jan 2023, 09:29:26] [drm] Fence fallback timer expired on ring sdma0
[Fr, 27. Jan 2023, 09:29:26] [drm] UVD and UVD ENC initialized successfully.
[Fr, 27. Jan 2023, 09:29:26] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fr, 27. Jan 2023, 09:29:26] [drm] VCE initialized successfully.
[Fr, 27. Jan 2023, 09:29:26] ata5.00: configured for UDMA/133
[Fr, 27. Jan 2023, 09:29:26] OOM killer enabled.
[Fr, 27. Jan 2023, 09:29:26] Restarting tasks ... 
[Fr, 27. Jan 2023, 09:29:26] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[Fr, 27. Jan 2023, 09:29:26] Bluetooth: hci0: Boot Address: 0x24800
[Fr, 27. Jan 2023, 09:29:26] Bluetooth: hci0: Firmware Version: 15-45.22
[Fr, 27. Jan 2023, 09:29:26] Bluetooth: hci0: Firmware already loaded
[Fr, 27. Jan 2023, 09:29:26] done.
[Fr, 27. Jan 2023, 09:29:26] random: crng reseeded on system resumption
[Fr, 27. Jan 2023, 09:29:26] PM: suspend exit
[Fr, 27. Jan 2023, 09:29:26] usbcore: registered new interface driver rts5139
[Fr, 27. Jan 2023, 09:29:26] audit: type=1130 audit(1674808165.686:4469): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=atop comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fr, 27. Jan 2023, 09:29:26] audit: type=1130 audit(1674808165.713:4470): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fr, 27. Jan 2023, 09:29:26] audit: type=1131 audit(1674808165.713:4471): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fr, 27. Jan 2023, 09:29:26] RTL8226B_RTL8221B 2.5Gbps PHY r8169-0-2a00:00: attached PHY driver (mii_bus:phy_addr=r8169-0-2a00:00, irq=MAC)
[Fr, 27. Jan 2023, 09:29:26] audit: type=1130 audit(1674808165.796:4472): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=set-cfs-tweaks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fr, 27. Jan 2023, 09:29:26] audit: type=1131 audit(1674808165.796:4473): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=set-cfs-tweaks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fr, 27. Jan 2023, 09:29:26] Bluetooth: MGMT ver 1.22
[Fr, 27. Jan 2023, 09:29:26] r8169 0000:2a:00.0 p137p1: Link is Down
[Fr, 27. Jan 2023, 09:29:27] audit: type=1130 audit(1674808166.176:4474): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fr, 27. Jan 2023, 09:29:28] audit: type=1131 audit(1674808167.376:4475): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fr, 27. Jan 2023, 09:29:31] wlan0: authenticate with 38:10:d5:71:22:56
[Fr, 27. Jan 2023, 09:29:31] wlan0: 80 MHz not supported, disabling VHT
[Fr, 27. Jan 2023, 09:29:31] wlan0: send auth to 38:10:d5:71:22:56 (try 1/3)
[Fr, 27. Jan 2023, 09:29:31] wlan0: authenticated
[Fr, 27. Jan 2023, 09:29:31] wlan0: associate with 38:10:d5:71:22:56 (try 1/3)
[Fr, 27. Jan 2023, 09:29:31] wlan0: RX AssocResp from 38:10:d5:71:22:56 (capab=0x1431 status=0 aid=1)
[Fr, 27. Jan 2023, 09:29:31] wlan0: associated
[Fr, 27. Jan 2023, 09:29:31] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 38:10:d5:71:22:56
[Fr, 27. Jan 2023, 09:29:31] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[Fr, 27. Jan 2023, 09:29:32] audit: type=1131 audit(1674808171.216:4476): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fr, 27. Jan 2023, 09:29:35] wlan0: Driver requested disconnection from AP 38:10:d5:71:22:56
[Fr, 27. Jan 2023, 09:29:38] wlan0: authenticate with 38:10:d5:71:22:56
[Fr, 27. Jan 2023, 09:29:38] wlan0: 80 MHz not supported, disabling VHT
[Fr, 27. Jan 2023, 09:29:38] wlan0: send auth to 38:10:d5:71:22:56 (try 1/3)
[Fr, 27. Jan 2023, 09:29:38] wlan0: authenticated
[Fr, 27. Jan 2023, 09:29:38] wlan0: associate with 38:10:d5:71:22:56 (try 1/3)
[Fr, 27. Jan 2023, 09:29:38] wlan0: RX AssocResp from 38:10:d5:71:22:56 (capab=0x1431 status=0 aid=1)
[Fr, 27. Jan 2023, 09:29:38] wlan0: associated
[Fr, 27. Jan 2023, 09:29:38] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 38:10:d5:71:22:56
[Fr, 27. Jan 2023, 09:29:40] audit: type=1130 audit(1674808178.976:4477): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fr, 27. Jan 2023, 09:29:40] audit: type=1130 audit(1674808179.029:4478): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ntpd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fr, 27. Jan 2023, 09:29:50] audit: type=1131 audit(1674808189.143:4479): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Fr, 27. Jan 2023, 09:30:57] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 09:30:57] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 09:36:59] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 09:36:59] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 09:43:02] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 09:43:02] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 09:49:32] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 09:49:32] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 09:55:58] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 09:55:58] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 10:02:28] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 10:02:28] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 10:08:36] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 10:08:36] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 10:15:03] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 10:15:03] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 10:21:30] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 10:21:30] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 10:27:33] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 10:27:33] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 10:33:35] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 10:33:35] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 10:39:56] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 10:39:56] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 10:46:07] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 10:46:07] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 10:52:29] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 10:52:29] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 10:58:31] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 10:58:31] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 11:04:58] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 11:04:58] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 11:11:06] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 11:11:06] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 11:17:36] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 11:17:36] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 11:24:06] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 11:24:06] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 11:30:35] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 11:30:35] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 11:37:05] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 11:37:05] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 11:43:35] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 11:43:35] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 11:50:05] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 11:50:05] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 11:56:34] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 11:56:34] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 12:03:04] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 12:03:04] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 12:09:34] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 12:09:34] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 12:16:03] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 12:16:03] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 12:22:30] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 12:22:30] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 12:29:00] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 12:29:00] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 12:35:30] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 12:35:30] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 12:41:38] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 12:41:38] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 12:48:07] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 12:48:07] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 12:54:37] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 12:54:37] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 13:01:04] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 13:01:04] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 13:07:31] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 13:07:31] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 13:14:00] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 13:14:00] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 13:20:30] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 13:20:30] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 13:26:57] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 13:26:57] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 13:33:05] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 13:33:05] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 13:39:32] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 13:39:32] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 13:46:02] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 13:46:02] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.
[Fr, 27. Jan 2023, 13:52:31] systemd-journald[454]: Data hash table of /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal has a fill level at 75.0 (174763 of 233016 items, 109051904 file size, 623 bytes per hash table item), suggesting rotation.
[Fr, 27. Jan 2023, 13:52:31] systemd-journald[454]: /var/log/journal/a3d4f241710644fea2e7ca1f719d0e6e/user-1000.journal: Journal header limits reached or header out-of-date, rotating.

Environment

Since terminal is <unknown> in the output: It's xfce4-terminal (fig doesn't work in that yet)

fig-details:
  - 2.14.0-nightly.20230126
hardware-info:
  - model: 
  - model-id: 
  - chip-id: AMD Ryzen 7 3700X 8-Core Processor
  - cores: 8
  - mem: 62.72 GB
os-info:
  - kernel: 6.1.7-arch1-1
  - distro: "Arch Linux"
  - distro-build: rolling
environment:
  - shell: /usr/bin/bash
  - terminal: <unknown>
  - cwd: /var/log/journal
  - exe-path: /usr/bin/fig
  - install-method: unknown
  - env-vars:
    - SHELL: /bin/bash
    - FIG_SET_PARENT_CHECK: 1
    - FIGTERM_SESSION_ID: 3ab86465-bfeb-4d37-a9e3-e9d33927bb38
    - XDG_SESSION_TYPE: tty
    - XDG_CURRENT_DESKTOP: XFCE
    - FIG_TERM: 2.14.0-nightly.20230126
    - TERM: xterm-256color
    - FIG_PID: 23061
    - DISPLAY: :0.0
    - PATH: /opt/android-sdk/emulator:/opt/android-sdk/tools:/home/duda/perl5/bin:/opt/android-sdk/emulator:/opt/android-sdk/tools:/home/duda/perl5/bin:/home/duda/.nix-profile/bin:/nix/var/nix/profiles/default/bin:/opt/jython/bin/:/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/adobe-air-sdk/bin:/opt/android-sdk/emulator:/opt/android-sdk/platform-tools:/home/duda/.dotnet/tools:/usr/lib/emscripten:/home/duda/.local/share/flatpak/exports/bin:/var/lib/flatpak/exports/bin:/opt/flutter/bin:/usr/lib/jvm/default/bin:/opt/nessus/bin:/opt/nessus/sbin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/lib/plan9/bin:/usr/lib/servo:/home/duda/.local/bin:/home/duda/.fig/bin:/home/duda/.local/bin::/usr/local/share/arm-eabi-4.6/bin:/usr/local/games:/home/duda/.npm-packages/bin:/usr/local/share/toolchain/bin/:/home/duda/.local/bin::/usr/local/share/arm-eabi-4.6/bin:/usr/local/games:/home/duda/.npm-packages/bin:/usr/local/share/toolchain/bin/
schrmh commented 1 year ago

Yep, it indeed seems to be hibernation related. suspend (to RAM) alone doesn't lead to it but after hibernation (aka suspend to disk) attempt it starts going crazy with log file entries. Also seems like that fig restart doesn't actually stop that in each case so I will just uninstall fig and maybe reinstall it again when fig-apps is hopefully usable at some point (the only thing I care about anyways).

mschrage commented 1 year ago

Autocomplete is not fully supported on Linux right now. Sorry for the inconvenience.

chaynabors commented 1 year ago

since this is related to https://github.com/withfig/fig/issues/2392 but contains valuable info, I'm leaving open while I investigate.