systemd-journald.service: Failed with result 'timeout'.

Hello.
I haven’t used my Manjaro for half a year, decided to come back and did ‘pamac update’. After the update, the startup of the system freezes for two minutes trying to start systemd-journald service, but then it seem to try again and succeeds. I wish to get rid of that 2 minute delay. I have tried deleting /var/log/journal and reinitializing it, but that didn’t help.

apr   22 23:26:12 rodent systemd-fsck[399]: fsck.fat 4.2 (2021-01-31)
apr   22 23:26:12 rodent systemd-fsck[399]: /dev/sdb1: 188 files, 6544/130812 clusters
apr   22 23:26:12 rodent systemd-fsck[392]: /dev/sdb4: clean, 801390/25853952 files, 64130571/103399761 blocks
apr   22 23:26:12 rodent ufw-init[585]: Skip starting firewall: ufw (not enabled)
apr   22 23:26:12 rodent systemd-journald[318]: Journal stopped
apr   22 23:26:12 rodent systemd[1]: systemd-journald.service: Failed with result 'timeout'.
apr   22 23:26:12 rodent systemd[1]: Failed to start Journal Service.
apr   22 23:26:12 rodent systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
apr   22 23:26:12 rodent systemd[1]: Starting Journal Service...
apr   22 23:26:12 rodent systemd-journald[625]: Collecting audit messages is disabled.
apr   22 23:26:12 rodent systemd-journald[625]: Journal started
apr   22 23:26:12 rodent systemd-journald[625]: Runtime Journal (/run/log/journal/85b99d722a6c464a9fa46161156dc8b6) is 8M, max 1.5G, 1.5G free.
apr   22 23:26:12 rodent systemd[1]: Started Journal Service.
apr   22 23:26:12 rodent systemd[1]: Starting Flush Journal to Persistent Storage...
apr   22 23:26:12 rodent systemd-journald[625]: Time spent on flushing to /var/log/journal/85b99d722a6c464a9fa46161156dc8b6 is 97.395ms for 1145 entries.
apr   22 23:26:12 rodent systemd-journald[625]: System Journal (/var/log/journal/85b99d722a6c464a9fa46161156dc8b6) is 24M, max 1.5G, 1.4G free.
apr   22 23:26:12 rodent systemd-journald[625]: Received client request to flush runtime journal.
apr   22 23:26:12 rodent systemd[1]: Finished Flush Journal to Persistent Storage.
apr   22 23:26:12 rodent systemd[1]: Starting Create System Files and Directories...
apr   22 23:26:13 rodent systemd-timesyncd[312]: Network configuration changed, trying to establish connection.
apr   22 23:26:13 rodent systemd-timesyncd[312]: Network configuration changed, trying to establish connection.
apr   22 23:26:13 rodent systemd-timesyncd[312]: Network configuration changed, trying to establish connection.
apr   22 23:26:13 rodent systemd-timesyncd[312]: Network configuration changed, trying to establish connection.

Moderator edit: Thank you for providing logs. Useless photos have been removed in order to make the forum backup smaller

There is your issue.

Manjaro is a rolling-release distribution which requires constant attention; frequent updates. When this doesn’t occur for an extended period, package versions on your machine become too far removed from those of current updates.

While it’s possible to carefully update, correcting each and every issue of the last half year, it’s not recommended.

The fastest approach is to perform a full reinstall using the latest Manjaro Installer ISO. I’ll also take the opportunity to suggest Ventoy as the bootable USB solution of choice.

Regards.


Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit:


Update Announcements

The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.

System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, but for Support purposes more in depth information is usually needed;

It’s best to ask your system directly. :eyes:

Output of the inxi command with appropriate parameters will achieve this (naturally, formatted according to forum guidelines) and will generally be more useful for those wishing to help:

inxi --filter --verbosity=8

or the short form:

inxi -zv8

Be prepared to provide output from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.

Highly Recommended
Required Reading
Technical Resources

Perhaps the storage is full?

You probably did check that.

df -h

lsblk -f

and
inxi -zv8

could provide more insight

In addition to the above, please also provide the output of:

systemctl status systemd-journald.service

and

journalctl --priority=warning..crit --no-pager --unit=systemd-journald.service

Where:

  • The --priority=warning..err argument limits the output to warnings and errors only;
  • --no-pager formats the output nicely for use here, on the forum;
  • the --unit=systemd-journald.service argument limits the messages to be from the specified unit only.

More:

Note that the above text is partially pre-prepared as general information. Please take the time to follow the given links and learn more.

And also:

systemd-analyze blame --no-pager