Results 1 to 6 of 6

Thread: SOS Urgent **** Ubuntu 20.04 LTS (Focal Fossa) creating 360 mb journal per minute

  1. #1
    Join Date
    Jun 2020
    Beans
    2

    Exclamation SOS Urgent **** Ubuntu 20.04 LTS (Focal Fossa) creating 360 mb journal per minute

    SOS Urgent **** Ubuntu 20.04 LTS (Focal Fossa) creating Automatically 360 MB of journal files per minute and system crashes after the hard disk gets full

    Hi All,

    In my Ubuntu 20 Desktop system Every Minute 360 MB of journal log data is generated and my processor is busy with 100% utilization running systemd-journal.

    Kindly help me urgently as every minute it is storing 128Mb * 3 files in /var/log/journal/42b76941196c44ebabf29f6efc5047c7/ Folder

    I am clearing log with this command manually >
    Code:
    sudo journalctl --vacuum-size=50M
    Deleted archived journal /var/log/journal/42b76941196c44ebabf29f6efc5047c7/system@00000000000000000000000000000000-00000000015de62d-0005a8bd92211c3a.journal (128.0M).
    Deleted archived journal /var/log/journal/42b76941196c44ebabf29f6efc5047c7/system@00000000000000000000000000000000-000000000160c6b7-0005a8bd93351c1b.journal (128.0M).
    Deleted archived journal /var/log/journal/42b76941196c44ebabf29f6efc5047c7/system@00000000000000000000000000000000-000000000163a7b1-0005a8bd945c0bf2.journal (128.0M).
    Vacuuming done, freed 3.8G of archived journals from /var/log/journal/42b76941196c44ebabf29f6efc5047c7.
    Vacuuming done, freed 0B of archived journals from /run/log/journal.
    3.8 GB of data created in just few minutes and the journal files keeps on getting created and my cpu is busy always 100%

    Currently i have done this setting changed :---

    In sudo nano /etc/systemd/journald.conf file modified this settings

    Code:
    SystemMaxUse=50M
    MaxLevelStore=err
    MaxLevelSyslog=warning
    MaxLevelKMsg=warning
    MaxLevelConsole=err
    >
    Code:
    top
    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                                                                                             >
    328 root      19  -1  468040 265696 263872 R 100.0   1.6  31:13.14 systemd-journal
    Code:
    /var/log/journal/42b76941196c44ebabf29f6efc5047c7  ls -lhsa
    total 3.5G
     12K drwxr-sr-x+ 2 root systemd-journal  12K Jun 23 11:01 .
    4.0K drwxr-sr-x+ 3 root systemd-journal 4.0K Jun 15 02:45 ..
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:53 system@00000000000000000000000000000...0cff991.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:53 system@00000000000000000000000000000...1dfebc1.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:53 system@00000000000000000000000000000...327bbb9.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:54 system@00000000000000000000000000000...491ec30.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:54 system@00000000000000000000000000000...5a40899.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:54 system@00000000000000000000000000000...6bf31e1.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:54 system@00000000000000000000000000000...7e08298.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:55 system@00000000000000000000000000000...8f27c6f.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:55 system@00000000000000000000000000000...a0eb633.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:55 system@00000000000000000000000000000...b414cea.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:56 system@00000000000000000000000000000...c5b194e.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:56 system@00000000000000000000000000000...d7f5e1d.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:56 system@00000000000000000000000000000...e9a9369.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:57 system@00000000000000000000000000000...fbe668e.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:57 system@00000000000000000000000000000...0d8c9fe.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:57 system@00000000000000000000000000000...1ee85f3.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:58 system@00000000000000000000000000000...3092fa2.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:58 system@00000000000000000000000000000...420b7d5.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:58 system@00000000000000000000000000000...592ecbf.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:59 system@00000000000000000000000000000...6fd52a8.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:59 system@00000000000000000000000000000...8164432.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 10:59 system@00000000000000000000000000000...9297455.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 11:00 system@00000000000000000000000000000...a453704.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 11:00 system@00000000000000000000000000000...b770daa.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 11:00 system@00000000000000000000000000000...c92d47f.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 11:01 system@00000000000000000000000000000...dac401f.journal
    129M -rw-r-----+ 1 root systemd-journal 128M Jun 23 11:01 system@00000000000000000000000000000...ecfe4c3.journal
     24M -rw-r-----+ 1 root systemd-journal  24M Jun 23 11:01 system.journal
    8.0M -rw-r-----+ 1 root systemd-journal 8.0M Jun 23 11:01 user-1000.journal
    System Details :

    Code:
    cat /etc/os-release
    
    NAME="Ubuntu"
    VERSION="20.04 LTS (Focal Fossa)"
    ID=ubuntu
    ID_LIKE=debian
    PRETTY_NAME="Ubuntu 20.04 LTS"
    VERSION_ID="20.04"
    HOME_URL="https://www.ubuntu.com/"
    SUPPORT_URL="https://help.ubuntu.com/"
    BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
    PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
    VERSION_CODENAME=focal
    UBUNTU_CODENAME=focal


    Kindly guide me to resolve this issue at the earliest its very urgent, Thanks in advance.

    Regards
    Last edited by crusader5; 1 Week Ago at 01:20 PM. Reason: code tags

  2. #2
    Join Date
    Nov 2012
    Location
    Halloween Town
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: SOS Urgent **** Ubuntu 20.04 LTS (Focal Fossa) creating 360 mb journal per minut

    Please use code tags when posting output, because when posted as plain text it loses its formatting and parts of it sometimes turn into smileys making it difficult to read and understand.

  3. #3
    Join Date
    Apr 2011
    Location
    Mystletainn Kick!
    Beans
    11,225
    Distro
    Ubuntu

    Re: SOS Urgent **** Ubuntu 20.04 LTS (Focal Fossa) creating 360 mb journal per minut

    Cleaning helps, but you need to post what the logs are saying.
    If anything ever log spams it means an error is occurring.
    Try taking a snippet of the logs before deleting them and post it.
    Typically just copy the end of it with
    Code:
    journalctl -b | tail -n 100
    to get the last 100 lines, which normally is enough to get a fair idea of the issues.

    (Most of the time when logs get spammed it's one particular issue, repeating itself ad nauseam.
    Splat Double Splat Triple Splat
    Earn Your Keep
    Don't mind me, I'm only passing through.
    Once in a blue moon, I'm actually helpful
    .

  4. #4
    Join Date
    Jun 2020
    Beans
    2

    Re: SOS Urgent **** Ubuntu 20.04 LTS (Focal Fossa) creating 360 mb journal per minut

    Hi All,

    Thanks for the reply.

    Here are few steps which I performed after looking at the logs.

    In my /var/log folder these two files were also taking up space.

    Code:
    ls -lsha
    71G -rw-r-----   1 syslog            adm              71G Jun 24 15:51 kern.log
    71G -rw-r-----   1 syslog            adm              71G Jun 24 15:52 syslog
    as suggested by deadflowr did tailing on this files

    Code:
    sudo tail -n 10 /var/log/syslog
    Jun 24 15:52:17 crusader update-notifier.desktop[3393]: Cannot stat file /proc/3137/fd/10: Permission denied
    Jun 24 15:52:17 crusader update-notifier.desktop[3393]: Cannot stat file /proc/3137/fd/11: Permission denied
    Jun 24 15:52:17 crusader update-notifier.desktop[3393]: Cannot stat file /proc/3137/fd/16: Permission denied
    Jun 24 15:52:17 crusader update-notifier.desktop[3393]: Cannot stat file /proc/3137/fd/17: Permission denied
    Jun 24 15:52:48 crusader gnome-shell[1903]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
    Jun 24 15:52:48 crusader gnome-shell[1903]: ../clutter/clutter/clutter-actor.c:10556: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function.
    Code:
    sudo tail -n 10 /var/log/kern.log
    ieport 0000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jun 2 pcieport 0000:00:1c.5: AER: device [8086:9d15] error status/mask=00000001/00002000 kernel: [ 178.057760] pcieport 0000:00:1c.5: AER: [ 0] RxErr
    I opened the grub file and modified this line..

    Code:
    sudo nano /etc/default/grub
    
    GRUB_CMDLINE_LINUX_DEFAULT='quiet splash'
    
    with this below line
    
    GRUB_CMDLINE_LINUX_DEFAULT='quiet splash pci=noaer'
    and rebooted my system and when I run top command now my cpu utilization is back to earlier. ie, systemd-journal process is not running and not utilizing 100% of my cpu usage.

    While I was googling through found that if system was utilizing more power not sure about it but I connected the external air cooler pad in laptop usb and laptop exhaust was blowing out lot of hot air. was this because my system was unable to manage power management ?


    Any other steps do you suggest for me.

    as of now system is running fine.

    I also ran few commands to before running this commands.

    Code:
    sudo apt-get update
    sudo apt-get dist-upgrade

    Thanks will wait and watch the stability of my laptop hope it should work fine.
    Last edited by crusader5; 1 Week Ago at 04:41 PM.

  5. #5
    Join Date
    Apr 2014
    Beans
    17
    Distro
    Xubuntu

    Re: SOS Urgent **** Ubuntu 20.04 LTS (Focal Fossa) creating 360 mb journal per minut

    Is this a fresh install or upgrade via apt?

  6. #6
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: SOS Urgent **** Ubuntu 20.04 LTS (Focal Fossa) creating 360 mb journal per minut

    What brand/model system?

    Some need boot parameters.

    Problems Installing on ASUS F555U needed boot option pci=nomsi
    http://ubuntuforums.org/showthread.php?t=2303665
    Asus x555u w/o pci=nomsi - space issue on drive and runaway log files filling drive
    https://ubuntuforums.org/showthread....2327103&page=3
    https://ubuntuforums.org/showthread.php?t=2327570
    For more info on UEFI boot install & repair - Regularly Updated :
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •