• (wie) kann ich die Konsole in macOS Sierra (10.12.3) wieder gebrauchbar/lesbar machen? (UPDATE)

    Ich benutzte bisher (also bis macOS 10.11) die Konsole (Console.app) manchmal um zu gucken, was in der letzten Zeit passiert ist, insbesondere wenn es ein Problem gab oder wenn cih wissen wollte, ob bzw. wie das letzte TimeMachine-Backup abgelaufen ist (erwartete vs. geschriebene datenmengen usw).

    Seit "Sierra" kapiere ich die Konsole überhaupt nicht mehr: ich gucke rein, sehe über tausend Einträge aus den letzten 5 Minuten – und nicht davor. Früher waren die einträge viel weniger, scheint mir, so, dass man nach einem Begriff suchen konte, zB "backupd" für Aktivitäten von TimeMachine, und sich mit einem "Früher"-Butten die Zeitfenster rückwärts arbeiten bis man was findet. Das suchen-Feld gibts noch, aber das findet oft nix mehr, weil durch die schiere Masse der Einträge die einzelnen Zeilen viel zu schnell aus dem einzigen sichtbaren Zeitfenster verdrängt werden.

    Bin ich nur zu doof, und man kann das Vor-Sierra-Verhalten wieder herstellen, oder ist das jetzt halt so (und ich sollte das gut finden weil: ...)?

    UPDATE: ok, ich bin einen schrittt weiter: das alte "Konsole.log" scheint das unter Berichte > Diagnose- und Nutzerberichte zu sein. Trotzdem sehe ich keine Möglichkeit mehr als ca. 2.000 meldungen zu sehen (also: keine Möglichkeit zusehen was davor passiert ist).

    UPDATE2: siehe meine Antwort eins drunter

    Danke, fby

    • Ah, finde gerade einen Artikel, der sagt dass die Konsole in Sierra a) komplett neu und b) sch*** (beta) ist

      "Overall, Console 1.0 looks promising. It has some rough edges – in parts very rough indeed – and is far from the complete tool which we need. Even performing fairly basic checks such as verifying that the last Time Machine backup completed correctly – something I could do in a few seconds in Old Console – are either acts of supreme intellectual challenge, or flatly impossible. I suppose that we will just have to limp on until Apple finishes it off. For now, I am afraid that it is a definite beta release. Oh – and I have already got it to hang a few times too."
      https://eclecticlight.co/2016/09/23/sierras-console-promising-but-incomplete/

      Na super. Mal wieder echt Apple-Bananensoftware: altes rausschmeißen bevor man einen stabil laufenden Ersatz hat.

      • Am genannten Ort gibt's noch einen Artikel und ein Tool

        https://eclecticlight.co/2016/11/17/a-console-replacement-for-examining-past-logs-in-sierra-loglogger-5a/
        ->
        https://eclecticlightdotcom.files.wordpress.com/2017/01/loglogger5d.zip

        A Console replacement for examining past logs in Sierra: LogLogger 5b (updated)

        Examining the logs in OS X / macOS is a very important function when investigating many problems. The logs can reveal what happened when, and give you powerful clues as to why things went wrong, enabling you to fix those problems. Even simple tasks, like checking whether the last Time Machine backup completed without errors, become impossible without access to the logs.

        With macOS Sierra, Apple has introduced a completely new and very powerful log system, with much greater capabilities than that in El Capitan (or, indeed, other comparable operating systems). However its current app for accessing those logs, Console 1.0, has almost no features to access the logs from the past, even a second before you start the app. In macOS Sierra 10.12 to 10.12.2, the only way of gaining useful access to logs of the past is through the command tool log (which is not without its own problems).

        LogLogger5b is an updated and improved version of my simple AppleScript app to give as complete access to past logs as you might obtain using the log show command in Terminal. Its improvements over LogLogger5 are:

        it comes with its own 15-page PDF documentation, which includes excerpts from the tutorials posted here,
        it now performs AND NOT and AND OR operations on predicates properly,
        it writes the shell command which it executed at the end of each output file, so that you can understand any issues that have arisen, and even learn to use the log show command yourself, if you wish.
        As with LogLogger5, the radio buttons and popup menus in its main dialog are not yet persistent between runs, I am afraid. I hope to be working on that issue shortly.

        LogLogger5b is exactly the same as 5a, but I think that I have now got my code signing working. This means that when you first run it after downloading, it should validate correctly with Gatekeeper and work first time, without having to bypass Gatekeeper using the Finder’s Open command. If you already use a copy of 5a (which Gatekeeper has then checked and authorised), there should be no detectable difference in use.

        If you want to distribute it more widely, please link to this page. I don’t wish to prevent anyone from making copies available elsewhere, but that does ensure a common source. Here is the zipped app and docs for download: loglogger5d

        I hope that you find this a practical tool which helps you diagnose issues. If you have any problems, find bugs, or have any suggestions, please add them here as comments (or send them by email to me).

        I have now replaced version 5b with 5d, which should work properly when you first download it. If it reports that it cannot be run because it is not from a recognised developer, simply select the app in the Finder and use the Finder’s Open command to run it instead.

        (Updated 19 January 2017 for version 5d.)
        ----------
        macOS 10.4, 10.14, 10.15, 11, 12, 13 sowie iOS 12, 15 und 17