[Rezolvat] Log-uri de eroare dupa restart

#1
lucifer76

Posted 14 January 2018 - 07:29

Bashtan

Grup: Moderators
Posts: 32,574
Înscris: 13.06.2007

Folosesc Manjaro KDE. Mi s-a intamplat sa plec de langa laptop, iar cand ma intorc ecranul sa fie stins si hdd-ul sa mearga de nebun. Ecranul nu am reusit sa il mai aprind cu nici o combinatie de taste si a trebuit sa dau restart din buton. Nici ssh-ul nu mai raspundea, imi arata ca se conecteaza dar nu aparea mesajul de intampinare si cursorul.
Bun, cum dau de logurile de eroare, journalctl -b imi arata ce se intampla doar de la pornirea calculatorului, nu ce s-a intamplat inainte.

Back to top

#2
dexterash

Posted 14 January 2018 - 08:40

--something---

Grup: Senior Members
Posts: 22,912
Înscris: 19.08.2004

Ii zice "syslog", e [aproape] de cand a luat fiinta Linuxu' (anii '90, adica), da' tre' configurat si "pastorit".

Back to top

#3
tavitu

Posted 14 January 2018 - 08:53

Minune: HE a �nceput s� emit� facturile!

Grup: Senior Members
Posts: 5,598
Înscris: 16.02.2009

Ai două posibilități cu journalctl:

Ori specifici intervalul exact.

Quote

-S, --since=, -U, --until=
   Start showing entries on or newer than the specified date, or on or
   older than the specified date, respectively. Date specifications
   should be of the format "2012-10-30 18:17:16". If the time part is
   omitted, "00:00:00" is assumed. If only the seconds component is
   omitted, ":00" is assumed. If the date component is omitted, the
   current day is assumed. Alternatively the strings "yesterday",
   "today", "tomorrow" are understood, which refer to 00:00:00 of the
   day before the current day, the current day, or the day after the
   current day, respectively.  "now" refers to the current time.
   Finally, relative times may be specified, prefixed with "-" or "+",
   referring to times before or after the current time, respectively.

Ori dai un argument la -b

Quote

-b [ID][+-offset], --boot=[ID][+-offset]
   Show messages from a specific boot. This will add a match for
   "_BOOT_ID=".
   The argument may be empty, in which case logs for the current boot
   will be shown.
   If the boot ID is omitted, a positive offset will look up the boots
   starting from the beginning of the journal, and a
   equal-or-less-than zero offset will look up boots starting from the
   end of the journal. Thus, 1 means the first boot found in the
   journal in chronological order, 2 the second and so on; while -0 is
   the last boot, -1 the boot before last, and so on. An empty offset
   is equivalent to specifying -0, except when the current boot is not
   the last boot (e.g. because --directory was specified to look at
   logs from a different machine).
   If the 32-character ID is specified, it may optionally be followed
   by offset which identifies the boot relative to the one given by
   boot ID. Negative values mean earlier boots and a positive values
   mean later boots. If offset is not specified, a value of zero is
   assumed, and the logs for the boot given by ID are shown.

Back to top

#4
lucifer76

Posted 14 January 2018 - 10:00

Bashtan

Grup: Moderators
Posts: 32,574
Înscris: 13.06.2007

dexterash, on 14 ianuarie 2018 - 08:40, said:

Ii zice "syslog", e [aproape] de cand a luat fiinta Linuxu' (anii '90, adica), da' tre' configurat si "pastorit".

Nu cred ca se mai foloseste Posted Image

tavitu, on 14 ianuarie 2018 - 08:53, said:

Ori dai un argument la -b

S-a rezolvat destul de simplu cu:

journalctl -b -1 -err

Merge si cu:

journalctl -S "2018-01-14 07:00:00" -U "2018-01-14 07:10:00"

Edited by lucifer76, 14 January 2018 - 10:01.

Back to top

#5
marco71

Posted 19 January 2018 - 18:48

Active Member

Grup: Members
Posts: 1,487
Înscris: 23.11.2004

dexterash said:

Ii zice "syslog", e [aproape] de cand a luat fiinta Linuxu' (anii '90, adica)..."

lucifer76 said:

Nu cred ca se mai foloseste Posted Image

se mai foloseste inca system-log-ul in linux si nu o sa dispara prea curand, doar ca pachetele de instalare au cunoscut modificari, vechea combinatie syslogd+klogd fiind inlocuita de syslog-ng/rsyslog si mai apoi integrat in systemd, cand o minte creata de la Fedora (cu acceptul gigantului RedHoit), a besit fantezii cu log-uri binare in loc de 'plaintext' si a inventat si impus ineptia de systemd ... scuze de off-topic, ma duc sa Posted Image