404 Not Found

\n\n\n\n

1<\/div>\n

2<\/div>\n

3<\/div>\n

4<\/div>\n

5<\/div>\n

6<\/div>\n

7<\/div>\n

8<\/div>\n

9<\/div>\n

10<\/div>\n

11<\/div>\n

12<\/div>\n

13<\/div>\n

14<\/div>\n

15<\/div>\n

16<\/div>\n

17<\/div>\n

18<\/div>\n

19<\/div>\n

20<\/div>\n

21<\/div>\n

22<\/div>\n

23<\/div>\n<\/td>\n

{<\/span><\/div>\n

“__CURSOR”<\/span> :<\/span> “s=bf93c444c3a2499095953159a3cba8c2;i=40c14;b=fbde6d3112084cd097c250aee3bab030;m=4f30cd3897;t=5199f269b9024;x=a424fc0dd9da81c4”<\/span>,<\/span><\/div>\n

“__REALTIME_TIMESTAMP”<\/span> :<\/span> “1435546221776932”<\/span>,<\/span><\/div>\n

“__MONOTONIC_TIMESTAMP”<\/span> :<\/span> “340121172119”<\/span>,<\/span><\/div>\n

“_BOOT_ID”<\/span> :<\/span> “fbde6d3112084cd097c250aee3bab030”<\/span>,<\/span><\/div>\n

“_TRANSPORT”<\/span> :<\/span> “syslog”<\/span>,<\/span><\/div>\n

“PRIORITY”<\/span> :<\/span> “6”<\/span>,<\/span><\/div>\n

“SYSLOG_FACILITY”<\/span> :<\/span> “10”<\/span>,<\/span> “SYSLOG_IDENTIFIER”<\/span> :<\/span> “sshd”<\/span>,<\/span><\/div>\n

“MESSAGE”<\/span> :<\/span> “pam_succeed_if(sshd:auth): requirement “<\/span>uid<\/span> &<\/span>gt<\/span>;<\/span>=<\/span> 1000<\/span>” not met by user “<\/span>root<\/span>“”<\/span>,<\/span><\/div>\n

“_UID”<\/span> :<\/span> “0”<\/span>,<\/span><\/div>\n

“_GID”<\/span> :<\/span> “0”<\/span>,<\/span><\/div>\n

“_COMM”<\/span> :<\/span> “sshd”<\/span>,<\/span><\/div>\n

“_EXE”<\/span> :<\/span> “\/usr\/sbin\/sshd”<\/span>,<\/span><\/div>\n

“_CMDLINE”<\/span> :<\/span> “sshd: root [priv] \u00a0\u00a0“<\/span>,<\/span><\/div>\n

“_CAP_EFFECTIVE”<\/span> :<\/span> “1fffffffff”<\/span>,<\/span> “_SYSTEMD_CGROUP”<\/span> :<\/span> “\/system.slice\/sshd.service”<\/span>,<\/span><\/div>\n

“_SYSTEMD_UNIT”<\/span> :<\/span> “sshd.service”<\/span>,<\/span><\/div>\n

“_SYSTEMD_SLICE”<\/span> :<\/span> “system.slice”<\/span>,<\/span><\/div>\n

“_MACHINE_ID”<\/span> :<\/span> “fd8cf26e06e411e4a9d004010897bd01”<\/span>,<\/span><\/div>\n

“_HOSTNAME”<\/span> :<\/span> “test-centos7”<\/span>,<\/span><\/div>\n

“SYSLOG_PID”<\/span> :<\/span> “32724”<\/span>,<\/span><\/div>\n

“_PID”<\/span> :<\/span> “32724”<\/span>,<\/span><\/div>\n

“_SOURCE_REALTIME_TIMESTAMP”<\/span> :<\/span> “1435546221776510”<\/span><\/div>\n

}<\/span><\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Por Prioridade<\/h2>\n

Use a op\u00e7\u00e3o -p<\/strong> para filtrar mensagens com base em um n\u00edvel de prioridade. Para ver quais n\u00edveis de prioridade est\u00e3o dispon\u00edveis, consulte a se\u00e7\u00e3o sobre par\u00e2metros de configura\u00e7\u00e3o Systemd-journald<\/strong> e os poss\u00edveis valores de par\u00e2metros MaxLevelStore<\/strong>. Se um \u00fanico n\u00edvel de prioridade for especificado, todas as mensagens com esse n\u00edvel de prioridade e abaixo dela ser\u00e3o exibidos. Para usar uma gama de n\u00edveis de prioridade, use o “FROM…TO”. Como um exemplo, o comando abaixo mostrar\u00e1 todas as mensagens com prioridade entre emerg\u00eancia e cr\u00edtico<\/strong> do \u00faltimo boot:<\/p>\n

journalctl<\/span> -<\/span>b<\/span> -<\/span>1<\/span> \u00a0-<\/span>p<\/span> \"crit\"<\/span><\/pre>\nPor Usu\u00e1rio<\/h2>\nPara localizar todas as mensagens relacionadas a um usu\u00e1rio espec\u00edfico, use o UID do usu\u00e1rio. No exemplo a seguir, n\u00f3s estamos encontrando o UID do usu\u00e1rio mysql:<\/p>\n
id mysql<\/pre>\nIsso retorna uma linha como esta:<\/p>\n
uid<\/span>=<\/span>108<\/span>(<\/span>mysql<\/span>)<\/span> gid<\/span>=<\/span>116<\/span>(<\/span>mysql<\/span>)<\/span> groups<\/span>=<\/span>116<\/span>(<\/span>mysql<\/span>)<\/span><\/pre>\nE ent\u00e3o n\u00f3s iremos consultar no journal\u00a0todas as mensagens registradas por esse usu\u00e1rio:<\/p>\n
journalctl <\/span>_UID<\/span>=<\/span>108<\/span><\/pre>\nA sa\u00edda seria assim:<\/p>\n
\n<\/div>\n<\/div>\n\n\n\n\n\n1<\/div>\n2<\/div>\n3<\/div>\n4<\/div>\n5<\/div>\n6<\/div>\n7<\/div>\n8<\/div>\n9<\/div>\n10<\/div>\n11<\/div>\n12<\/div>\n<\/td>\n \n—<\/span> Logs <\/span>begin <\/span>at <\/span>Thu<\/span> 2015<\/span>–<\/span>06<\/span>–<\/span>25<\/span> 00<\/span>:<\/span>34<\/span>:<\/span>38<\/span> EDT<\/span>,<\/span> end<\/span> at <\/span>Sun<\/span> 2015<\/span>–<\/span>06<\/span>–<\/span>28<\/span> 23<\/span>:<\/span>16<\/span>:<\/span>08<\/span> EDT<\/span>.<\/span> —<\/span><\/div>\nJun<\/span> 25<\/span> 00<\/span>:<\/span>53<\/span>:<\/span>21<\/span> test<\/span>–<\/span>ubuntu15 <\/span>mysqld_safe<\/span>[<\/span>11177<\/span>]<\/span>:<\/span> 150625<\/span> 00<\/span>:<\/span>53<\/span>:<\/span>21<\/span> mysqld_safe <\/span>Can<\/span>‘t log to error log and syslog at the same time. \u00a0Remove all –log-error configuration options for –syslog to take effect.<\/span><\/div>\nJun 25 00:53:21 test-ubuntu15 mysqld_safe[11177]: 150625 00:53:21 mysqld_safe Logging to ‘<\/span>\/<\/span>var<\/span>\/<\/span>log<\/span>\/<\/span>mysql<\/span>\/<\/span>error<\/span>.<\/span>log<\/span>‘.<\/span><\/div>\nJun 25 00:53:21 test-ubuntu15 mysqld_safe[11177]: 150625 00:53:21 mysqld_safe Starting mysqld daemon with databases from \/var\/lib\/mysql<\/span><\/div>\nJun 27 21:41:26 test-ubuntu15 mysqld_safe[11177]: Could not open required defaults file: \/etc\/mysql\/debian.cnf<\/span><\/div>\nJun 27 21:41:26 test-ubuntu15 mysqld_safe[11177]: Fatal error in defaults handling. Program aborted<\/span><\/div>\nJun 27 21:41:26 test-ubuntu15 mysqld_safe[11177]: 150627 21:41:26 mysqld_safe mysqld from pid file \/var\/run\/mysqld\/mysqld.pid ended<\/span><\/div>\n<\/div>\n<b>– Reboot –<\/b><\/span><\/div>\nJun 27 21:41:33 test-ubuntu15 mysqld_safe[561]: 150627 21:41:33 mysqld_safe Can’<\/span>t<\/span> log <\/span>to<\/span> error <\/span>log <\/span>and<\/span> syslog <\/span>at <\/span>the <\/span>same <\/span>time<\/span>.<\/span> \u00a0Remove <\/span>all<\/span> —<\/span>log<\/span>–<\/span>error <\/span>configuration <\/span>options <\/span>for<\/span> —<\/span>syslog <\/span>to<\/span> take <\/span>effect<\/span>.<\/span><\/div>\nJun<\/span> 27<\/span> 21<\/span>:<\/span>41<\/span>:<\/span>33<\/span> test<\/span>–<\/span>ubuntu15 <\/span>mysqld_safe<\/span>[<\/span>561<\/span>]<\/span>:<\/span> 150627<\/span> 21<\/span>:<\/span>41<\/span>:<\/span>33<\/span> mysqld_safe <\/span>Logging <\/span>to<\/span> ‘\/var\/log\/mysql\/error.log’<\/span>.<\/span><\/div>\nJun<\/span> 27<\/span> 21<\/span>:<\/span>41<\/span>:<\/span>33<\/span> test<\/span>–<\/span>ubuntu15 <\/span>mysqld_safe<\/span>[<\/span>561<\/span>]<\/span>:<\/span> 150627<\/span> 21<\/span>:<\/span>41<\/span>:<\/span>33<\/span> mysqld_safe <\/span>Starting <\/span>mysqld <\/span>daemon <\/span>with <\/span>databases <\/span>from<\/span> \/<\/span>var<\/span>\/<\/span>lib<\/span>\/<\/span>mysql<\/span><\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nBom pessoal, como falei no come\u00e7o do artigo, para maiores informa\u00e7\u00f5es consulte a p\u00e1gina de manual do jounalctl<\/a><\/span>.<\/p>\n
Ferramentas Visuais<\/h2>\n<\/div>\n<\/div>\nSe voc\u00ea estiver usando distros como o SUSE Enterprise ou o openSUSE<\/a><\/span> por exemplo, poder\u00e1 tamb\u00e9m checar os registros do journal usando o m\u00f3dulo do Yast<\/strong> chamado journal-systemd, ou “Entradas do Di\u00e1rio”, conforme imagem abaixo.<\/p>\n
Obs.<\/strong> O painel de controle Yast tamb\u00e9m funciona em modo texto no terminal. Ent\u00e3o poderia ser usado mesmo se voc\u00ea n\u00e3o possuir ambiente desktop instalado no SUSE\/openSUSE.<\/p>\n
<\/a> \u00a0\u00a0<\/a><\/p>\n
Voc\u00ea poder\u00e1 alterar o filtro que desejar usando o bot\u00e3o “Mudar Filtro…”<\/strong>\u00a0no canto inferior esquerdo, e repare que quase todas<\/strong> as op\u00e7\u00f5es que citamos neste artigo, ou seja, o desde e at\u00e9 (since e until), desde o \u00faltimo boot, ou boot anterior, por unidade, por comando ou execut\u00e1veis, e por prioridade (com uma combo-box para voc\u00ea definir a prioridade), s\u00e3o exibidas na ferramenta.<\/p>\n
<\/p>\n
Gnome-logs<\/h4>\nExiste tamb\u00e9m uma ferramenta do Gnome, (que n\u00e3o vem instalada por padr\u00e3o, mas voc\u00ea poder\u00e1 instal\u00e1-la usando o seu gerenciador de pacotes), chamada gnome-logs que mostra para voc\u00ea mensagens do seu journal e lhe permite pesquisar por elas. Mas esta n\u00e3o \u00e9 t\u00e3o completa, pois n\u00e3o lhe permite realizar filtragens, apenas possui algumas categorias. Com certeza o m\u00f3dulo do Yast \u00e9 bem mais completo que esta, mas talvez possa ser \u00fatil para voc\u00ea.<\/p>\n<\/a><\/p>\n
Conclus\u00e3o<\/h3>\nBom, realmente o journalctl \u00e9 bem legal com seus diversos filtros e a possibilidade de podermos combin\u00e1-los. Usando-o\u00a0no terminal existem muito mais op\u00e7\u00f5es\u00a0de filtros que podemos combinar.
\nA maioria das Distribui\u00e7\u00f5es Linux est\u00e3o usando ou migrando para o systemd, e por isso o journalctl, ent\u00e3o creio que \u00e9 uma boa ideia nos acostumarmos a analisarmos os logs nesta ferramenta.<\/p>\n
Outro artigo que pode ajudar a entender como gerenciar servi\u00e7os do Systemd \u00e9 esse abaixo:<\/p>\n<\/a><\/p>\n
Aquele abra\u00e7o!<\/p>\n
Cleuber<\/p>\n
fonte: (eu mesmo rs)
\ne\u00a0loggly.com<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Todo administrador tem como rotina checar os servi\u00e7os de um servidor atr\u00e1s de problemas e ent\u00e3o realizar medidas para corrigir os problemas. Algumas distribui\u00e7\u00f5es Linux usam o Rsyslog como sistema de log, e outras o Journalctl. As que usam o Systemd ao inv\u00e9s do init ou outro similar, trazem o utilit\u00e1rio\u00a0Journalctl. E existe uma mudan\u00e7a …<\/p>\n","protected":false},"author":1,"featured_media":11027,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[51,488,348],"tags":[601,522,602],"class_list":["post-11029","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dicas-e-tutoriais","category-seguranca","category-servidores-linux","tag-journalctl","tag-logs","tag-systemd"],"_links":{"self":[{"href":"https:\/\/cleuber.com.br\/index.php\/wp-json\/wp\/v2\/posts\/11029","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cleuber.com.br\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cleuber.com.br\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cleuber.com.br\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cleuber.com.br\/index.php\/wp-json\/wp\/v2\/comments?post=11029"}],"version-history":[{"count":0,"href":"https:\/\/cleuber.com.br\/index.php\/wp-json\/wp\/v2\/posts\/11029\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cleuber.com.br\/index.php\/wp-json\/wp\/v2\/media\/11027"}],"wp:attachment":[{"href":"https:\/\/cleuber.com.br\/index.php\/wp-json\/wp\/v2\/media?parent=11029"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cleuber.com.br\/index.php\/wp-json\/wp\/v2\/categories?post=11029"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cleuber.com.br\/index.php\/wp-json\/wp\/v2\/tags?post=11029"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}