Mdthbs

ISP is not hashing the password I log in with online. Should I take any action?

Harley Davidson clattering noise from engine, backfire and failure to start

Can an escape pod land on Earth from orbit and not be immediately detected?

Is it true that "only photographers care about noise"?

Can I use 220 V outlets on a 15 ampere breaker and wire it up as 110 V?

Why is it bad to use your whole foot in rock climbing

Idiom for 'person who gets violent when drunk"

usage of mir gefallen

Does the UK delegate some immigration control to the Republic of Ireland?

Changing the PK column of a data extension without completely recreating it

What did the 8086 (and 8088) do upon encountering an illegal instruction?

Why are ambiguous grammars bad?

Simple log rotation script

Can you open the door or die? v2

Can I get a photo of an Ancient Arrow?

In Pandemic, why take the extra step of eradicating a disease after you've cured it?

Approach sick days in feedback meeting

What publication claimed that Michael Jackson died in a nuclear holocaust?

Placement of positioning lights on A320 winglets

Is Jesus the last Prophet?

Is it possible to have battery technology that can't be duplicated?

Why would a car salesman tell me not to get my credit pulled again?

Someone who is granted access to information but not expected to read it

Part of my house is inexplicably gone

How to read *.journal files in Fedora 21?

Howto inspect systemd system.journal from another systemSystem freezing on Fedora 15 - graphics issue?Why is my systemd journal not persistent across reboots?systemd, rsyslogd - where are the logs?fedora 24 won't boot after dnf upgradeFedora Linux: I installed sendmail but now I don't get mail notifications when I log inIs it possible to reduce systemd-journald size stored format (and thus size)?How should I manage the logs from my own systemd services?Why do “journalctl --disk-usage” and “journalctl | wc” not correspond well?How to prevent a process from writing to the systemd journal?change the name of the journal files in /var/log/journal/remote coming from /var/log/journal/upload

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

1

1

I want to see the previous dmesg log before the reboot. In previous versions of fedora, It used to be in /var/log/messages. But from Fedora 20, it's being stored through systemd i.e. journalctl.

I've a directory /var/log/journal. It has many files and all of them having extension as .journal. I tried to open them with gedit. But couldn't succeed. I tried with notepad++. It's showing unreadable data as if a binary file. How to read them?

fedora dmesg systemd-journald

share|improve this question

edited Sep 23 '17 at 20:05

sourcejedi

27.3k446121

asked Jun 17 '15 at 6:21

RatDonRatDon

1091214

add a comment | 

1

1

I want to see the previous dmesg log before the reboot. In previous versions of fedora, It used to be in /var/log/messages. But from Fedora 20, it's being stored through systemd i.e. journalctl.

I've a directory /var/log/journal. It has many files and all of them having extension as .journal. I tried to open them with gedit. But couldn't succeed. I tried with notepad++. It's showing unreadable data as if a binary file. How to read them?

fedora dmesg systemd-journald

share|improve this question

edited Sep 23 '17 at 20:05

sourcejedi

27.3k446121

asked Jun 17 '15 at 6:21

RatDonRatDon

1091214

add a comment | 

I want to see the previous dmesg log before the reboot. In previous versions of fedora, It used to be in /var/log/messages. But from Fedora 20, it's being stored through systemd i.e. journalctl.

I've a directory /var/log/journal. It has many files and all of them having extension as .journal. I tried to open them with gedit. But couldn't succeed. I tried with notepad++. It's showing unreadable data as if a binary file. How to read them?

fedora dmesg systemd-journald

share|improve this question

edited Sep 23 '17 at 20:05

sourcejedi

27.3k446121

asked Jun 17 '15 at 6:21

RatDonRatDon

1091214

share|improve this question

edited Sep 23 '17 at 20:05

sourcejedi

27.3k446121

asked Jun 17 '15 at 6:21

RatDonRatDon

1091214

share|improve this question

edited Sep 23 '17 at 20:05

sourcejedi

27.3k446121

asked Jun 17 '15 at 6:21

RatDonRatDon

1091214

edited Sep 23 '17 at 20:05

sourcejedi

27.3k446121

edited Sep 23 '17 at 20:05

sourcejedi

27.3k446121

asked Jun 17 '15 at 6:21

RatDonRatDon

1091214

asked Jun 17 '15 at 6:21

RatDonRatDon

1091214

2 Answers
2

active

oldest

votes

2

You are not supposed to read them. These are binary files. Only the tool "journalctl" with correct user permission can read them. Its a feature of "systemd". Any normal user can't read the system logs, unlike the traditional "syslog" system where any user can "cat" the "/var/log/messages" and see all the system logs.

share|improve this answer

edited Jun 17 '15 at 8:57

answered Jun 17 '15 at 6:34

x1b2jx1b2j

39213

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Just a remark: Even in a 'traditional "syslog" system,' most log files in /var/log are normally only root-readable. Ubuntu is the only system I know of that has loosened these restrictions and allows non-root users read access to /var/log/syslog and probably /var/log/messages, for whatever reasons.
  
  – Dubu
  Jun 17 '15 at 9:16
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The question isn't "should I" but "how do I." Your response would have been better left as a comment.
  
  – Stephan
  55 mins ago
  

  
  
  
  

add a comment | 

0

Borrowed from this answer:

journalctl --file, e. g. journalctl --file /path/to/some/file.journal

As indicated in the other answer, these logs are regularly rotated, and may not stretch back as far as you might hope.

share|improve this answer

answered 52 mins ago

StephanStephan

1,900814

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f210150%2fhow-to-read-journal-files-in-fedora-21%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

2

You are not supposed to read them. These are binary files. Only the tool "journalctl" with correct user permission can read them. Its a feature of "systemd". Any normal user can't read the system logs, unlike the traditional "syslog" system where any user can "cat" the "/var/log/messages" and see all the system logs.

share|improve this answer

edited Jun 17 '15 at 8:57

answered Jun 17 '15 at 6:34

x1b2jx1b2j

39213

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Just a remark: Even in a 'traditional "syslog" system,' most log files in /var/log are normally only root-readable. Ubuntu is the only system I know of that has loosened these restrictions and allows non-root users read access to /var/log/syslog and probably /var/log/messages, for whatever reasons.
  
  – Dubu
  Jun 17 '15 at 9:16
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The question isn't "should I" but "how do I." Your response would have been better left as a comment.
  
  – Stephan
  55 mins ago
  

  
  
  
  

add a comment | 

2

You are not supposed to read them. These are binary files. Only the tool "journalctl" with correct user permission can read them. Its a feature of "systemd". Any normal user can't read the system logs, unlike the traditional "syslog" system where any user can "cat" the "/var/log/messages" and see all the system logs.

share|improve this answer

edited Jun 17 '15 at 8:57

answered Jun 17 '15 at 6:34

x1b2jx1b2j

39213

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Just a remark: Even in a 'traditional "syslog" system,' most log files in /var/log are normally only root-readable. Ubuntu is the only system I know of that has loosened these restrictions and allows non-root users read access to /var/log/syslog and probably /var/log/messages, for whatever reasons.
  
  – Dubu
  Jun 17 '15 at 9:16
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The question isn't "should I" but "how do I." Your response would have been better left as a comment.
  
  – Stephan
  55 mins ago
  

  
  
  
  

add a comment | 

You are not supposed to read them. These are binary files. Only the tool "journalctl" with correct user permission can read them. Its a feature of "systemd". Any normal user can't read the system logs, unlike the traditional "syslog" system where any user can "cat" the "/var/log/messages" and see all the system logs.

share|improve this answer

edited Jun 17 '15 at 8:57

answered Jun 17 '15 at 6:34

x1b2jx1b2j

39213

share|improve this answer

edited Jun 17 '15 at 8:57

answered Jun 17 '15 at 6:34

x1b2jx1b2j

39213

answered Jun 17 '15 at 6:34

x1b2jx1b2j

39213

answered Jun 17 '15 at 6:34

x1b2jx1b2j

39213

0

Borrowed from this answer:

journalctl --file, e. g. journalctl --file /path/to/some/file.journal

As indicated in the other answer, these logs are regularly rotated, and may not stretch back as far as you might hope.

share|improve this answer

answered 52 mins ago

StephanStephan

1,900814

add a comment | 

0

Borrowed from this answer:

journalctl --file, e. g. journalctl --file /path/to/some/file.journal

As indicated in the other answer, these logs are regularly rotated, and may not stretch back as far as you might hope.

share|improve this answer

answered 52 mins ago

StephanStephan

1,900814

add a comment | 

Borrowed from this answer:

journalctl --file, e. g. journalctl --file /path/to/some/file.journal

As indicated in the other answer, these logs are regularly rotated, and may not stretch back as far as you might hope.

share|improve this answer

answered 52 mins ago

StephanStephan

1,900814

share|improve this answer

answered 52 mins ago

StephanStephan

1,900814

answered 52 mins ago

StephanStephan

1,900814

answered 52 mins ago

StephanStephan

1,900814