82 lines
1.8 KiB
Markdown
82 lines
1.8 KiB
Markdown
|
# xxg40.166系统卡死现象调查
|
|||
|
|
|
|||
|
|
| ID | Creation Date | Assignee | Status |
|
|||
|
|
|----|----------------|----------|--------|
|
|||
|
|
| OMPUB-7 | 2020-05-08T10:35:19.000+0800 | 王宇 | 完成 |
|
|||
|
|
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
xxg 40.166 （adc mcn0）出现系统卡死现象，首次发现日期2020-05-08，通过系统日志判断卡死时间为 2020-05-06 21:37:44，下图为卡死现场拍摄图片
|
|||
|
|
|
|||
|
|
!image-2020-05-08-10-34-39-917.png|width=811,height=609!
|
|||
|
|
|
|||
|
|
第二次卡死发现时间2020-06-01
|
|||
|
|
|
|||
|
|
!image-2020-06-01-13-38-08-163.png!**zhangzhihan** commented on *2020-05-22T14:36:54.803+0800*:
|
|||
|
|
|
|||
|
|
从2020-05-08后再未出现该故障，暂时关闭该issues，若发现故障则开启本issues
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
**wangyu** commented on *2020-06-05T15:39:37.333+0800*:
|
|||
|
|
|
|||
|
|
*40.166系统卡死机调研进度*
|
|||
|
|
|
|||
|
|
[^40.166死机调研文档.docx]
|
|||
|
|
|
|||
|
|
根据报错信息，大多报错都是内存报错。后来对40.166的内存进行监控发现buff/cache缓存一直在升高，不会自动进行释放。目前进行了系统配置可以让缓存达到一定的阈值后进行释放。
|
|||
|
|
|
|||
|
|
6月5号改完系统配置，40.166监控内存脚本还在运行。再观察几天，如果buff/cache不再增长，就看是否还会发生死机现象。
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
**wangyu** commented on *2020-06-10T12:37:02.085+0800*:
|
|||
|
|
|
|||
|
|
任务进度：
|
|||
|
|
# 修改完系统配置后，通过监控脚本没有发现buff/cache升高。
|
|||
|
|
# 现需要暂停任务，看过一段时间后会不会再次出现卡死现象。
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
**wangyu** commented on *2020-09-02T14:59:20.333+0800*:
|
|||
|
|
|
|||
|
|
40.166到现在一切正常。
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
## Attachments
|
|||
|
|
|
|||
|
|
**11689/40.166死机调研文档.docx**
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
**11176/image-2020-05-08-10-34-39-917.png**
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
**11561/image-2020-06-01-13-38-08-163.png**
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
**11726/image-2020-06-08-13-19-33-356.png**
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
**11727/image-2020-06-08-13-21-23-385.png**
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|