Debian Bookworm error 65146.899451 systemd [1] failed to start journal service
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Debian Bookworm error 65146.899451 systemd [1] failed to start journal service
Okay folks I have a "small" problem.
My computer freezes, it does it bad enough that I have to push and hold the power button to turn it off and then power it back on (hard reboot, power cycle, etc.) to get it unfrozen. I've looked everywhere I can think of and can't find anything in the log files, dmesg,etc and nothing.
When it freezes it shows my memory usage is at 100% and CPU is at 20% (via Conky).
Once in a awhile I can open a terminal session, either by using Ctl+Alt+F2 or Ctl+Alt+T, and it shows the message in the terminal after logging in as Root/Sudo.
Soooo, the $64.00 question is, how do I find what's causing it? That way I can report the bug to the proper place.
Ideas welcomed and thanks in advance for any help given.
CPU: AMD A6-7400K Radeon R5 2C+4G (2) @ 4.091GHz
GPU: AMD ATI Radeon R5 Graphics with 8 GB RAM.
Disk is 46.7GB/ 92.0 GB
Memtest is fine. Inside is clean,
That I know of, it's just sitting with my email program running (Evolution getting GMail & local mails [Log reports]) so nothing major.
I am getting notices about Exim Panic log having a non-zero size.But it's from Popularity Contest and I have a bug filed about that.
I just want to figure out what's having a tissey fit so I can report it or at least know how to find it so I can kill it.
DMESG doesn't show anything or any log files I can find.
Does /var/log/journal/ exist? If not, create it, if you would like a persistent journal. For current boot, simply sudo journalctl -b should be as much log as needed for scanning. If you think something is failing, try sudo journalctl -b | grep -i Failed. man journalctl
Failing to start the journal service the only thing I can think of would be a disk write error, but I would expect automatic retry to succeed, or a more serious error message to follow. Did it subsequently start? Are there any messages on vtty10 or any other vtty? Is /var/log/ and everything in it except exi* owned by root:root, root:4 or root:modem?
Well I tried the commands that MRMAZDA gave and grepping for Failed and Error doesn't show much of anything: So maybe I'm missing something. This only started within the last 5 upgrades (Dist-upgrade) so I'm reasonably(?) sure it's software related. The log file is there and of course it has nothing useful there either. I'll test the disk with S.M.A.R.T. monitoring and see if it's my disk.
Thanks for the help so far.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.