CentOS7: systemd-journald[4372]: Failed to open system journal: Not a directory.
by Sum1 from LinuxQuestions.org on (#5FCCX)
I have a CentOS 7 server acting as a Samba Active Directory Domain Controller.
Suddenly today - about half of the Windows (7/8/10) clients joined to the domain can not access fileshares and the other server.
DNS is working correctly and everyone can access the internet.
All clients can authenticate to the domain.
I thought it might be related to hardware so I cloned the CentOS 7 server to a different ssd hard drive and ran it from a different server. The same result --- only about half of the Windows clients can access the fileshares.
Even Connecting to the server via ssh was very slow and the terminal would hang when trying to run 'dmesg' or 'htop'.
When I run the dmesg on a local machine terminal I see a flood of the following messages:
systemd-journald[4372]: Failed to open system journal: Not a directory.
They appear in bursts of 20 or so, every 3 seconds.
I cannot find much on this message and do not know what to try to alleviate the congestion on the server and regain access for LAN clients.
I would appreciate any help or suggestions. Thank you for reading.
Suddenly today - about half of the Windows (7/8/10) clients joined to the domain can not access fileshares and the other server.
DNS is working correctly and everyone can access the internet.
All clients can authenticate to the domain.
I thought it might be related to hardware so I cloned the CentOS 7 server to a different ssd hard drive and ran it from a different server. The same result --- only about half of the Windows clients can access the fileshares.
Even Connecting to the server via ssh was very slow and the terminal would hang when trying to run 'dmesg' or 'htop'.
When I run the dmesg on a local machine terminal I see a flood of the following messages:
systemd-journald[4372]: Failed to open system journal: Not a directory.
They appear in bursts of 20 or so, every 3 seconds.
I cannot find much on this message and do not know what to try to alleviate the congestion on the server and regain access for LAN clients.
I would appreciate any help or suggestions. Thank you for reading.