Linux查看指定时间的日志信息

本文档展示了如何使用Linux命令来筛选特定日期和时间范围内的日志信息,以及如何定位错误日志条目。通过`sed`和`grep`命令,可以高效地查找某一天、某一时段或包含特定错误信息的日志记录,这对于系统监控和故障排除至关重要。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

一、查看某天指定时间段日志信息

sed -n ‘/某年某月某日某时/,/某年某月某日某时/p’ 日志文件

[root@bj-oldboy-muban 09:36:57 log]# sed -n '/May 31 13:57:04/,/May 31 16:08:11/p' messages-20220605 
May 31 13:57:04 bj-oldboy-muban rz[14177]: [root] no.name/ZMODEM: got error
May 31 13:57:24 bj-oldboy-muban rz[14179]: [root] jdk-8u201-linux-x64.tar.gz/ZMODEM: 191817140 Bytes, 33431550 BPS
May 31 14:00:12 bj-oldboy-muban su: (to app) root on pts/0
May 31 14:01:01 bj-oldboy-muban systemd: Started Session 132 of user root.
May 31 14:01:01 bj-oldboy-muban systemd: Starting Session 132 of user root.
May 31 14:03:52 bj-oldboy-muban su: (to root) root on pts/0
May 31 14:05:24 bj-oldboy-muban su: (to app) root on pts/0
May 31 14:07:41 bj-oldboy-muban su: (to root) root on pts/0
May 31 14:08:47 bj-oldboy-muban su: (to app) root on pts/0
May 31 14:10:07 bj-oldboy-muban su: (to root) root on pts/0
May 31 14:25:11 bj-oldboy-muban systemd-logind: New session 133 of user root.
May 31 14:25:11 bj-oldboy-muban systemd: Started Session 133 of user root.
May 31 14:25:11 bj-oldboy-muban systemd: Starting Session 133 of user root.
May 31 14:25:35 bj-oldboy-muban systemd-logind: Removed session 133.
May 31 14:48:47 bj-oldboy-muban systemd-logind: Removed session 131.
May 31 14:53:21 bj-oldboy-muban systemd: Started Session 134 of user root.
May 31 14:53:21 bj-oldboy-muban systemd-logind: New session 134 of user root.
May 31 14:53:21 bj-oldboy-muban systemd: Starting Session 134 of user root.
May 31 15:00:04 bj-oldboy-muban systemd: Reloading.
May 31 15:00:23 bj-oldboy-muban systemd: Reloading.
May 31 15:00:29 bj-oldboy-muban systemd: Starting mongodb...
May 31 15:00:29 bj-oldboy-muban mongod: 2022-05-31T15:00:29.118+0800 I CONTROL  [main] note: noprealloc may hurt performance in many applications
May 31 15:00:29 bj-oldboy-muban mongod: about to fork child process, waiting until server is ready for connections.
May 31 15:00:29 bj-oldboy-muban mongod: forked process: 14898
May 31 15:00:29 bj-oldboy-muban mongod: child process started successfully, parent exiting
May 31 15:00:29 bj-oldboy-muban systemd: Started mongodb.
May 31 15:01:01 bj-oldboy-muban systemd: Started Session 135 of user root.
May 31 15:01:01 bj-oldboy-muban systemd: Starting Session 135 of user root.
May 31 15:22:15 bj-oldboy-muban systemd: Stopping mongodb...
May 31 15:22:15 bj-oldboy-muban systemd: Stopped mongodb.
May 31 15:36:40 bj-oldboy-muban rz[15079]: [root] no.name/ZMODEM: got error
May 31 15:37:16 bj-oldboy-muban sz[15085]: [root] mongodb-linux-x86_64-4.0.4.tgz/ZMODEM: 71435492 Bytes, 11347996 BPS
May 31 15:44:35 bj-oldboy-muban rz[15113]: [root] no.name/ZMODEM: got error
May 31 15:44:58 bj-oldboy-muban rz[15114]: [root] mongod_bak.sh/ZMODEM: 901 Bytes, 142070 BPS
May 31 16:01:01 bj-oldboy-muban systemd: Started Session 136 of user root.
May 31 16:01:01 bj-oldboy-muban systemd: Starting Session 136 of user root.
May 31 16:08:11 bj-oldboy-muban rz[15146]: [root] no.name/ZMODEM: got error

二、查看某天指定时间段报错日志信息

sed -n ‘/某年某月某日某时/,/某年某月某日某时/p’ 日志文件 | grep -Ei “报错信息|报错信息”

[root@bj-oldboy-muban 10:53:54 log]# sed -n '/May 31 13:57:04/,/May 31 16:08:11/p' messages-20220605 | grep -Ei "error|fails"
May 31 13:57:04 bj-oldboy-muban rz[14177]: [root] no.name/ZMODEM: got error
May 31 15:36:40 bj-oldboy-muban rz[15079]: [root] no.name/ZMODEM: got error
May 31 15:44:35 bj-oldboy-muban rz[15113]: [root] no.name/ZMODEM: got error
May 31 16:08:11 bj-oldboy-muban rz[15146]: [root] no.name/ZMODEM: got error

三、查看某天的日志信息

grep -i “某年某月某日.*” 日志文件

[root@bj-oldboy-muban 10:31:21 log]# grep -i "May 31.*" messages-20220605
May 31 00:01:01 bj-oldboy-muban systemd: Started Session 117 of user root.
May 31 00:01:01 bj-oldboy-muban systemd: Starting Session 117 of user root.
May 31 01:01:01 bj-oldboy-muban systemd: Started Session 118 of user root.
May 31 01:01:01 bj-oldboy-muban systemd: Starting Session 118 of user root.
May 31 02:01:01 bj-oldboy-muban systemd: Started Session 119 of user root.
May 31 02:01:01 bj-oldboy-muban systemd: Starting Session 119 of user root.
May 31 03:01:01 bj-oldboy-muban systemd: Started Session 120 of user root.
May 31 03:01:01 bj-oldboy-muban systemd: Starting Session 120 of user root.
May 31 04:01:01 bj-oldboy-muban systemd: Started Session 121 of user root.
May 31 04:01:01 bj-oldboy-muban systemd: Starting Session 121 of user root.
May 31 05:01:01 bj-oldboy-muban systemd: Started Session 122 of user root.
May 31 05:01:01 bj-oldboy-muban systemd: Starting Session 122 of user root.
May 31 06:01:01 bj-oldboy-muban systemd: Started Session 123 of user root.
May 31 06:01:01 bj-oldboy-muban systemd: Starting Session 123 of user root.
May 31 07:01:01 bj-oldboy-muban systemd: Started Session 124 of user root.
May 31 07:01:01 bj-oldboy-muban systemd: Starting Session 124 of user root.
May 31 08:01:01 bj-oldboy-muban systemd: Started Session 125 of user root.
May 31 08:01:01 bj-oldboy-muban systemd: Starting Session 125 of user root.
May 31 09:01:01 bj-oldboy-muban systemd: Started Session 126 of user root.
May 31 09:01:01 bj-oldboy-muban systemd: Starting Session 126 of user root.
May 31 10:01:01 bj-oldboy-muban systemd: Started Session 127 of user root.
May 31 10:01:01 bj-oldboy-muban systemd: Starting Session 127 of user root.
May 31 11:01:01 bj-oldboy-muban systemd: Started Session 128 of user root.
May 31 11:01:01 bj-oldboy-muban systemd: Starting Session 128 of user root.
May 31 12:01:01 bj-oldboy-muban systemd: Started Session 129 of user root.
May 31 12:01:01 bj-oldboy-muban systemd: Starting Session 129 of user root.
May 31 13:01:01 bj-oldboy-muban systemd: Started Session 130 of user root.
May 31 13:01:01 bj-oldboy-muban systemd: Starting Session 130 of user root.
May 31 13:06:47 bj-oldboy-muban systemd: Started Session 131 of user root.
May 31 13:06:47 bj-oldboy-muban systemd-logind: New session 131 of user root.
May 31 13:06:47 bj-oldboy-muban systemd: Starting Session 131 of user root.
May 31 13:21:30 bj-oldboy-muban rz[14009]: [root] sersync-master.zip/ZMODEM: 1981010 Bytes, 27215359 BPS
May 31 13:37:57 bj-oldboy-muban systemd: Starting Cleanup of Temporary Directories...
May 31 13:37:57 bj-oldboy-muban systemd: Started Cleanup of Temporary Directories.
May 31 13:52:07 bj-oldboy-muban su: (to app) root on pts/0
May 31 13:53:09 bj-oldboy-muban su: (to root) root on pts/0
May 31 13:53:25 bj-oldboy-muban su: (to app) root on pts/0
May 31 13:57:04 bj-oldboy-muban rz[14177]: [root] no.name/ZMODEM: got error
May 31 13:57:24 bj-oldboy-muban rz[14179]: [root] jdk-8u201-linux-x64.tar.gz/ZMODEM: 191817140 Bytes, 33431550 BPS
May 31 14:00:12 bj-oldboy-muban su: (to app) root on pts/0
May 31 14:01:01 bj-oldboy-muban systemd: Started Session 132 of user root.
May 31 14:01:01 bj-oldboy-muban systemd: Starting Session 132 of user root.
May 31 14:03:52 bj-oldboy-muban su: (to root) root on pts/0
May 31 14:05:24 bj-oldboy-muban su: (to app) root on pts/0
May 31 14:07:41 bj-oldboy-muban su: (to root) root on pts/0
May 31 14:08:47 bj-oldboy-muban su: (to app) root on pts/0
May 31 14:10:07 bj-oldboy-muban su: (to root) root on pts/0
May 31 14:25:11 bj-oldboy-muban systemd-logind: New session 133 of user root.
May 31 14:25:11 bj-oldboy-muban systemd: Started Session 133 of user root.
May 31 14:25:11 bj-oldboy-muban systemd: Starting Session 133 of user root.
May 31 14:25:35 bj-oldboy-muban systemd-logind: Removed session 133.
May 31 14:48:47 bj-oldboy-muban systemd-logind: Removed session 131.
May 31 14:53:21 bj-oldboy-muban systemd: Started Session 134 of user root.
May 31 14:53:21 bj-oldboy-muban systemd-logind: New session 134 of user root.
May 31 14:53:21 bj-oldboy-muban systemd: Starting Session 134 of user root.
May 31 15:00:04 bj-oldboy-muban systemd: Reloading.
May 31 15:00:23 bj-oldboy-muban systemd: Reloading.
May 31 15:00:29 bj-oldboy-muban systemd: Starting mongodb...
May 31 15:00:29 bj-oldboy-muban mongod: 2022-05-31T15:00:29.118+0800 I CONTROL  [main] note: noprealloc may hurt performance in many applications
May 31 15:00:29 bj-oldboy-muban mongod: about to fork child process, waiting until server is ready for connections.

四、查看某天的报错日志信息

grep -Ei “某年某月某日.*报错信息|报错信息” 日志文件

[root@bj-oldboy-muban 10:41:51 log]# grep -Ei "May 31.*error|fails" messages-20220605
May 31 13:57:04 bj-oldboy-muban rz[14177]: [root] no.name/ZMODEM: got error
May 31 15:36:40 bj-oldboy-muban rz[15079]: [root] no.name/ZMODEM: got error
May 31 15:44:35 bj-oldboy-muban rz[15113]: [root] no.name/ZMODEM: got error
May 31 16:08:11 bj-oldboy-muban rz[15146]: [root] no.name/ZMODEM: got error

五、查看某天某时的日志信息

grep -i “某年某月某日某时.*” 日志文件

[root@bj-oldboy-muban 10:33:14 log]# grep -i "May 31 13.*" messages-20220605
May 31 13:01:01 bj-oldboy-muban systemd: Started Session 130 of user root.
May 31 13:01:01 bj-oldboy-muban systemd: Starting Session 130 of user root.
May 31 13:06:47 bj-oldboy-muban systemd: Started Session 131 of user root.
May 31 13:06:47 bj-oldboy-muban systemd-logind: New session 131 of user root.
May 31 13:06:47 bj-oldboy-muban systemd: Starting Session 131 of user root.
May 31 13:21:30 bj-oldboy-muban rz[14009]: [root] sersync-master.zip/ZMODEM: 1981010 Bytes, 27215359 BPS
May 31 13:37:57 bj-oldboy-muban systemd: Starting Cleanup of Temporary Directories...
May 31 13:37:57 bj-oldboy-muban systemd: Started Cleanup of Temporary Directories.
May 31 13:52:07 bj-oldboy-muban su: (to app) root on pts/0
May 31 13:53:09 bj-oldboy-muban su: (to root) root on pts/0
May 31 13:53:25 bj-oldboy-muban su: (to app) root on pts/0
May 31 13:57:04 bj-oldboy-muban rz[14177]: [root] no.name/ZMODEM: got error
May 31 13:57:24 bj-oldboy-muban rz[14179]: [root] jdk-8u201-linux-x64.tar.gz/ZMODEM: 191817140 Bytes, 33431550 BPS

六、查看某天某时的报错日志信息

grep -Ei “某年某月某日某时.*报错信息|报错信息” 日志文件

[root@bj-oldboy-muban 10:41:59 log]# grep -Ei "May 31.13:.*error|fails" messages-20220605 
May 31 13:57:04 bj-oldboy-muban rz[14177]: [root] no.name/ZMODEM: got error

七、按分钟查看日志信息

查看2022年01月6号11点34分到11点37分之间的日志信息

grep   '2022-01-06 11:3[4-7]' log.log

八、按秒查看日志信息

查看2022年01月6号11点42分1秒到59秒的日志信息

grep '2022-01-06 11:42:[01-59]' log.log

九、按小时查看日志信息

查看2022年01月6号10点到11点的日志信息

grep '2022-01-06 1[0-1]' log.log

十、按指定时间精准查看日志信息

查看2022年01月6号11点42分的日志信息

grep '2022-01-06 11:42' log.log
Linux系统中查找特定时间段日志内容是一个常见的需求。通常可以结合`grep`、`awk`或者其他文本处理工具完成此操作。 ### 方法一: 使用 `journalctl`(适用于 systemd 系统) 如果您的系统使用的是 `systemd` ,那么可以直接通过命令行查看系统的日志文件,并且支持直接按时间过滤: ```bash # 查看从 "2023-10-01 08:00" 到 "2023-10-05 17:00" 的所有日志 journalctl --since="2023-10-01 08:00" --until="2023-10-05 17:00" ``` 这将显示给定日期范围内生成的所有日志消息。 --- ### 方法二: 结合 grep 和 awk (针对普通log文件) 对于传统的纯文本格式日志(比如 `/var/log/syslog`, 或者 Nginx/apache 日志等),需要手动筛选出包含指定时间戳的部分。 示例如下: 假设我们需要检查 /var/log/messages 文件里发生在 `"Oct 4"` 那一天的数据 #### 步骤1 - 过滤日期范围内的记录: ```bash cat /path/to/yourlogfile | sed -n '/^Oct 4/,/^Oct 6/p' ``` 该指令会打印从“ Oct 4” 开始直到遇到下一个非连续日子 “Oct 6”之间的所有行。(这里的路径替换实际的 log 路径) #### 步骤2 – 更精确地控制开始结束时刻 进一步细化到具体的时间点上,则需要用到强大的 `awk` 命令了, 例如只想得到某服务启动期间(如 '9am 至 1pm')产生的错误信息: ```shell awk '$0 >= from && $0 <= to { print } /^Oct/{ split($0,a," "); timestamp=a[2]" "a[3]; } BEGIN{from="Oct 4 09:00";to="Oct 4 13:00"}' your_log_file.log ``` 上述脚本首先设置了一个变量用于存储目标区间两端;接着每当读取一行新数据就尝试解析其头部作为当前时间标记并与预设值比较判断是否应该输出这条目. --- 以上两种方法分别适应于现代基于 systemctl 架构及传统 syslog 格式环境下的场景应用,在日常运维工作中非常实用。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值