4 ms·
So, if you care about logs, don't depend on journalctl... Well that's fine if you can ship logs off the box, and if the log shipping is working. But if you have
by 0xbadcafebee 6y ago
So, if you care about logs, don't depend on journalctl... Well that's fine if you can ship logs off the box, and if the log shipping is working. But if you have to troubleshoot on the machine itself (hello, desktops?) then having tools that don't come with a lot of pain and big learning curve is critical to addressing the issue quickly. What's the point in even having these tools if we're not supposed to use them?
Normally, Unix-like tools are not as painful as journalctl. But Poettering's interfaces are a gauntlet of unusual concepts and hidden inter-relationships, with no common examples or intuitiveness. And things like dbus make it worse, now that there are many parts of a modern Linux system that have no console interface, because nobody's written one for the particular application you need to view or change the right dbus settings. And /sys/ is literally a wilderness of random undocumented settings that are often the only interface to critical system functions.
Linux distributions are now a tiresome no-mans-land of overcomplicated mysterious crap. I'm willing to bet the major Linux distributions will be abandoned over the next decade for simpler systems that are cloud-native, mobile-friendly, and have less Kafkaesque interfaces.
- fullstop 6y agoWhat kind of desktop do you have where your journal is constantly getting corrupted? Most distributions log both to the journal and to /var/log/, so I'm seriously struggling to understand the complaint here. GP's message about centralized logging is saying that if logs are that important to you, you will keep them stored in a centralized location. You should be able to catch the server on fire and have logs recorded centrally up until that point. This would be the case with or without journald. You started with a strawman about caring about logs, and ended complaining about sysfs.
- 0xbadcafebee 6y agoYeah I digressed quite a bit, sorry. > I'm seriously struggling to understand the complaint here The complaint was trying to explain a parent commenter's point about journald "They’re really nice until everything on the node is completely broken. Then they are a massive obstruction to access and understanding what went wrong due to the opaqueness." Point: Logs are really annoying to manage on systems with journald. Counter-point: Ship your logs somewhere else / you probably don't have these problems in real life Counter-Counter: If we're not supposed to use these tools on our hosts, exactly why are they installed?
- fullstop 6y agoLogs are written to both the journal and /var/log/ I would argue that logs are less annoying to manage on systems with journald, once you take the time to learn how to leverage the tools. I would also argue that shipping mission-critical logs off-server is a worthy endeavor, regardless of logging system used. I like journald because it lets me isolate logs for a particular unit without grepping and accidentally including output from unrelated services. It's faster to find the data that I need between time ranges rather than manually comparing time stamps. I can count on one finger the number of times the journal has been corrupted on the servers that I manage, and it was because of hardware failure.
- deleted 6y ago[deleted]
- mousepilot 6y agoI have this fantasy that all the pro systemd posts are really just bots run by leonard
- fullstop 6y agoI, Leonard, do not know of what you speak. ;-)