00:55:00
ENDX-249 - oute, Ubuntu, select Jan 10 13:01:20 Ubuntu journal: .The output "Jan 10 13:01:20 Ubuntu journal: ." indicates that there is an entry in the journal logs at the specified timestamp, but it seems to be an empty event ("."). To resolve and ensure the journal is functioning correctly, follow these steps:1. **Check Journal Logs**: - Use `journalctl` to check the logs for any errors or warnings: ``` journalctl -xe ``` - Use `journalctl` to check the logs since boot: ``` journalctl -b ```2. **Restart Journals**: - Restart the systemd journal service to reinitialize it: ``` systemctl restart systemd-journald ``` - Check the status of the journal service to ensure it's running: ``` systemctl status systemd-journald ```3. **Disk Space**: - Ensure there's enough disk space on the system. Low disk space can prevent the journal from operating correctly. - Check disk space: ``` df -h ``` - If disk space is low, free up space by removing old logs or other files.4. **Permissions**: - Ensure the correct permissions are set for the journal files: ``` chmod 644 /var/log/journal/* ``` - Ensure correct ownership: ``` chroot /var/var/log/journal root:root ```5. **Storage Limits**: - Set storage limits for the journal to prevent it from consuming too much space: ``` edit /etc/systemd/journald.conf ``` Modify the line `StorageLimit=` to specify a limit (e.g. `StorageLimit=2G`). 6. **Reconfigure**: - If issues persist, reconfigure the journal: ``` dpkg-reconfigure systemd-journal ``` 7. **System Reboot**: - Reboot the system to apply changes and ensure everything is working: ``` systemctl reboot ```By following these steps, you can resolve incorrect behavior in the journal and ensure it's functioning properly.)
2019年10月15日
English
中文
日本語