首页 手机软件 手机游戏 单机游戏 资讯文章 专题下载 游戏合集 文章合集 php下载 php教程 电脑软件
+ -
当前位置：首页 → 问答吧 → 关于NIM Thread Blocked

关于NIM Thread Blocked

时间：2010-03-30

来源：互联网



今天检查机器看到报了几条 NIM Thread Blocked
详细错误信息如下:
  1. >errpt -aj 3D32B80D
  2. ---------------------------------------------------------------------------
  3. LABEL:          TS_NIM_ERROR_STUCK_
  4. IDENTIFIER:     3D32B80D
  5. Date/Time:       Mon Mar  8 19:11:36 BEIST 2010
  6. Sequence Number: 2914
  7. Machine Id:      00C879D24C00
  8. Node Id:         app
  9. Class:           S
  10. Type:            PERM
  11. Resource Name:   topsvcs
  12. Description
  13. NIM thread blocked
  14. Probable Causes
  15. A thread in a Topology Services Network Interface Module (NIM) process
  16. was blocked
  17. Topology Services NIM process cannot get timely access to CPU
  18. User Causes
  19. Excessive memory consumption is causing high memory contention
  20. Excessive disk I/O is causing high memory contention
  21.         Recommended Actions
  22.         Examine I/O and memory activity on the system
  23.         Reduce load on the system
  24.         Tune virtual memory parameters
  25.         Call IBM Service if problem persists
  26. Failure Causes
  27. Excessive virtual memory activity prevents NIM from making progress
  28. Excessive disk I/O traffic is interfering with paging I/O
  29.         Recommended Actions
  30.         Examine I/O and memory activity on the system
  31.         Reduce load on the system
  32.         Tune virtual memory parameters
  33.         Call IBM Service if problem persists
  34. Detail Data
  35. DETECTING MODULE
  36. rsct,nim_control.C,1.39.1.22,5947
  37. ERROR ID
  38. 6BUfAx.chBZ9//oq./oD2g0...................
  39. REFERENCE CODE
  40. Thread which was blocked
  41. receive thread
  42. Interval in seconds during which process was blocked
  43.          261
  44. Interface name
  45. en0
  46. ---------------------------------------------------------------------------
  47. LABEL:          TS_NIM_ERROR_STUCK_
  48. IDENTIFIER:     3D32B80D
  49. Date/Time:       Mon Mar  8 19:11:36 BEIST 2010
  50. Sequence Number: 2913
  51. Machine Id:      00C879D24C00
  52. Node Id:         app
  53. Class:           S
  54. Type:            PERM
  55. Resource Name:   topsvcs
  56. Description
  57. NIM thread blocked
  58. Probable Causes
  59. A thread in a Topology Services Network Interface Module (NIM) process
  60. was blocked
  61. Topology Services NIM process cannot get timely access to CPU
  62. User Causes
  63. Excessive memory consumption is causing high memory contention
  64. Excessive disk I/O is causing high memory contention
  65.         Recommended Actions
  66.         Examine I/O and memory activity on the system
  67.         Reduce load on the system
  68.         Tune virtual memory parameters
  69.         Call IBM Service if problem persists
  70. Failure Causes
  71. Excessive virtual memory activity prevents NIM from making progress
  72. Excessive disk I/O traffic is interfering with paging I/O
  73.         Recommended Actions
  74.         Examine I/O and memory activity on the system
  75.         Reduce load on the system
  76.         Tune virtual memory parameters
  77.         Call IBM Service if problem persists
  78. Detail Data
  79. DETECTING MODULE
  80. rsct,nim_control.C,1.39.1.22,5947
  81. ERROR ID
  82. 6BUfAx.chBZ9/2Mj./oD2g0...................
  83. REFERENCE CODE
  84. Thread which was blocked
  85. receive thread
  86. Interval in seconds during which process was blocked
  87.          260
  88. Interface name
  89. en2
  90. ---------------------------------------------------------------------------
  91. LABEL:          TS_NIM_ERROR_STUCK_
  92. IDENTIFIER:     3D32B80D
  93. Date/Time:       Mon Mar  8 19:11:36 BEIST 2010
  94. Sequence Number: 2912
  95. Machine Id:      00C879D24C00
  96. Node Id:         app
  97. Class:           S
  98. Type:            PERM
  99. Resource Name:   topsvcs
  100. Description
  101. NIM thread blocked
  102. Probable Causes
  103. A thread in a Topology Services Network Interface Module (NIM) process
  104. was blocked
  105. Topology Services NIM process cannot get timely access to CPU
  106. User Causes
  107. Excessive memory consumption is causing high memory contention
  108. Excessive disk I/O is causing high memory contention
  109.         Recommended Actions
  110.         Examine I/O and memory activity on the system
  111.         Reduce load on the system
  112.         Tune virtual memory parameters
  113.         Call IBM Service if problem persists
  114. Failure Causes
  115. Excessive virtual memory activity prevents NIM from making progress
  116. Excessive disk I/O traffic is interfering with paging I/O
  117.         Recommended Actions
  118.         Examine I/O and memory activity on the system
  119.         Reduce load on the system
  120.         Tune virtual memory parameters
  121.         Call IBM Service if problem persists
  122. Detail Data
  123. DETECTING MODULE
  124. rsct,nim_control.C,1.39.1.22,5947
  125. ERROR ID
  126. 6BUfAx.chBZ9/W.E./oD2g0...................
  127. REFERENCE CODE
  128. Thread which was blocked
  129. send thread
  130. Interval in seconds during which process was blocked
  131.          260
  132. Interface name
  133. tty0
  134. ---------------------------------------------------------------------------
  135. LABEL:          TS_NIM_ERROR_STUCK_
  136. IDENTIFIER:     3D32B80D
  137. Date/Time:       Mon Mar  8 19:11:36 BEIST 2010
  138. Sequence Number: 2911
  139. Machine Id:      00C879D24C00
  140. Node Id:         app
  141. Class:           S
  142. Type:            PERM
  143. Resource Name:   topsvcs
  144. Description
  145. NIM thread blocked
  146. Probable Causes
  147. A thread in a Topology Services Network Interface Module (NIM) process
  148. was blocked
  149. Topology Services NIM process cannot get timely access to CPU
  150. User Causes
  151. Excessive memory consumption is causing high memory contention
  152. Excessive disk I/O is causing high memory contention
  153.         Recommended Actions
  154.         Examine I/O and memory activity on the system
  155.         Reduce load on the system
  156.         Tune virtual memory parameters
  157.         Call IBM Service if problem persists
  158. Failure Causes
  159. Excessive virtual memory activity prevents NIM from making progress
  160. Excessive disk I/O traffic is interfering with paging I/O
  161.         Recommended Actions
  162.         Examine I/O and memory activity on the system
  163.         Reduce load on the system
  164.         Tune virtual memory parameters
  165.         Call IBM Service if problem persists
  166. Detail Data
  167. DETECTING MODULE
  168. rsct,nim_control.C,1.39.1.22,5947
  169. ERROR ID
  170. 6BUfAx.chBZ9/PYD./oD2g0...................
  171. REFERENCE CODE
  172. Thread which was blocked
  173. receive thread
  174. Interval in seconds during which process was blocked
  175.          260
  176. Interface name
  177. tty0
  178. ---------------------------------------------------------------------------
  179. LABEL:          TS_NIM_ERROR_STUCK_
  180. IDENTIFIER:     3D32B80D
  181. Date/Time:       Mon Mar  8 19:11:36 BEIST 2010
  182. Sequence Number: 2910
  183. Machine Id:      00C879D24C00
  184. Node Id:         app
  185. Class:           S
  186. Type:            PERM
  187. Resource Name:   topsvcs
  188. Description
  189. NIM thread blocked
  190. Probable Causes
  191. A thread in a Topology Services Network Interface Module (NIM) process
  192. was blocked
  193. Topology Services NIM process cannot get timely access to CPU
  194. User Causes
  195. Excessive memory consumption is causing high memory contention
  196. Excessive disk I/O is causing high memory contention
  197.         Recommended Actions
  198.         Examine I/O and memory activity on the system
  199.         Reduce load on the system
  200.         Tune virtual memory parameters
  201.         Call IBM Service if problem persists
  202. Failure Causes
  203. Excessive virtual memory activity prevents NIM from making progress
  204. Excessive disk I/O traffic is interfering with paging I/O
  205.         Recommended Actions
  206.         Examine I/O and memory activity on the system
  207.         Reduce load on the system
  208.         Tune virtual memory parameters
  209.         Call IBM Service if problem persists
  210. Detail Data
  211. DETECTING MODULE
  212. rsct,nim_control.C,1.39.1.22,5947
  213. ERROR ID
  214. 6BUfAx.chBZ9/g1D./oD2g0...................
  215. REFERENCE CODE
  216. Thread which was blocked
  217. command receive thread
  218. Interval in seconds during which process was blocked
  219.          263
  220. Interface name
  221. en2
  222. ---------------------------------------------------------------------------
  223. LABEL:          TS_NIM_ERROR_STUCK_
  224. IDENTIFIER:     3D32B80D
  225. Date/Time:       Mon Mar  8 19:11:36 BEIST 2010
  226. Sequence Number: 2909
  227. Machine Id:      00C879D24C00
  228. Node Id:         app
  229. Class:           S
  230. Type:            PERM
  231. Resource Name:   topsvcs
  232. Description
  233. NIM thread blocked
  234. Probable Causes
  235. A thread in a Topology Services Network Interface Module (NIM) process
  236. was blocked
  237. Topology Services NIM process cannot get timely access to CPU
  238. User Causes
  239. Excessive memory consumption is causing high memory contention
  240. Excessive disk I/O is causing high memory contention
  241.         Recommended Actions
  242.         Examine I/O and memory activity on the system
  243.         Reduce load on the system
  244.         Tune virtual memory parameters
  245.         Call IBM Service if problem persists
  246. Failure Causes
  247. Excessive virtual memory activity prevents NIM from making progress
  248. Excessive disk I/O traffic is interfering with paging I/O
  249.         Recommended Actions
  250.         Examine I/O and memory activity on the system
  251.         Reduce load on the system
  252.         Tune virtual memory parameters
  253.         Call IBM Service if problem persists
  254. Detail Data
  255. DETECTING MODULE
  256. rsct,nim_control.C,1.39.1.22,5947
  257. ERROR ID
  258. 6BUfAx.chBZ9/zWC./oD2g0...................
  259. REFERENCE CODE
  260. Thread which was blocked
  261. command receive thread
  262. Interval in seconds during which process was blocked
  263.          266
  264. Interface name
  265. en0
  266. ---------------------------------------------------------------------------
  267. LABEL:          TS_NIM_ERROR_STUCK_
  268. IDENTIFIER:     3D32B80D
  269. Date/Time:       Mon Mar  8 19:11:36 BEIST 2010
  270. Sequence Number: 2908
  271. Machine Id:      00C879D24C00
  272. Node Id:         app
  273. Class:           S
  274. Type:            PERM
  275. Resource Name:   topsvcs
  276. Description
  277. NIM thread blocked
  278. Probable Causes
  279. A thread in a Topology Services Network Interface Module (NIM) process
  280. was blocked
  281. Topology Services NIM process cannot get timely access to CPU
  282. User Causes
  283. Excessive memory consumption is causing high memory contention
  284. Excessive disk I/O is causing high memory contention
  285.         Recommended Actions
  286.         Examine I/O and memory activity on the system
  287.         Reduce load on the system
  288.         Tune virtual memory parameters
  289.         Call IBM Service if problem persists
  290. Failure Causes
  291. Excessive virtual memory activity prevents NIM from making progress
  292. Excessive disk I/O traffic is interfering with paging I/O
  293.         Recommended Actions
  294.         Examine I/O and memory activity on the system
  295.         Reduce load on the system
  296.         Tune virtual memory parameters
  297.         Call IBM Service if problem persists
  298. Detail Data
  299. DETECTING MODULE
  300. rsct,nim_control.C,1.39.1.22,5947
  301. ERROR ID
  302. 6BUfAx.chBZ9/54C./oD2g0...................
  303. REFERENCE CODE
  304. Thread which was blocked
  305. command receive thread
  306. Interval in seconds during which process was blocked
  307.          263
  308. Interface name
  309. tty0
  310. ---------------------------------------------------------------------------
  311. LABEL:          TS_NIM_ERROR_STUCK_
  312. IDENTIFIER:     3D32B80D
  313. Date/Time:       Mon Mar  8 19:11:36 BEIST 2010
  314. Sequence Number: 2907
  315. Machine Id:      00C879D24C00
  316. Node Id:         app
  317. Class:           S
  318. Type:            PERM
  319. Resource Name:   topsvcs
  320. Description
  321. NIM thread blocked
  322. Probable Causes
  323. A thread in a Topology Services Network Interface Module (NIM) process
  324. was blocked
  325. Topology Services NIM process cannot get timely access to CPU
  326. User Causes
  327. Excessive memory consumption is causing high memory contention
  328. Excessive disk I/O is causing high memory contention
  329.         Recommended Actions
  330.         Examine I/O and memory activity on the system
  331.         Reduce load on the system
  332.         Tune virtual memory parameters
  333.         Call IBM Service if problem persists
  334. Failure Causes
  335. Excessive virtual memory activity prevents NIM from making progress
  336. Excessive disk I/O traffic is interfering with paging I/O
  337.         Recommended Actions
  338.         Examine I/O and memory activity on the system
  339.         Reduce load on the system
  340.         Tune virtual memory parameters
  341.         Call IBM Service if problem persists
  342. Detail Data
  343. DETECTING MODULE
  344. rsct,nim_control.C,1.39.1.22,5947
  345. ERROR ID
  346. 6BUfAx.chBZ9/ggB./oD2g0...................
  347. REFERENCE CODE
  348. Thread which was blocked
  349. main thread
  350. Interval in seconds during which process was blocked
  351.          260
  352. Interface name
  353. en2
  354. ---------------------------------------------------------------------------
  355. LABEL:          TS_NIM_ERROR_STUCK_
  356. IDENTIFIER:     3D32B80D
  357. Date/Time:       Mon Mar  8 19:11:36 BEIST 2010
  358. Sequence Number: 2906
  359. Machine Id:      00C879D24C00
  360. Node Id:         app
  361. Class:           S
  362. Type:            PERM
  363. Resource Name:   topsvcs
  364. Description
  365. NIM thread blocked
  366. Probable Causes
  367. A thread in a Topology Services Network Interface Module (NIM) process
  368. was blocked
  369. Topology Services NIM process cannot get timely access to CPU
  370. User Causes
  371. Excessive memory consumption is causing high memory contention
  372. Excessive disk I/O is causing high memory contention
  373.         Recommended Actions
  374.         Examine I/O and memory activity on the system
  375.         Reduce load on the system
  376.         Tune virtual memory parameters
  377.         Call IBM Service if problem persists
  378. Failure Causes
  379. Excessive virtual memory activity prevents NIM from making progress
  380. Excessive disk I/O traffic is interfering with paging I/O
  381.         Recommended Actions
  382.         Examine I/O and memory activity on the system
  383.         Reduce load on the system
  384.         Tune virtual memory parameters
  385.         Call IBM Service if problem persists
  386. Detail Data
  387. DETECTING MODULE
  388. rsct,nim_control.C,1.39.1.22,5947
  389. ERROR ID
  390. 6BUfAx.chBZ9/xEB./oD2g0...................
  391. REFERENCE CODE
  392. Thread which was blocked
  393. send thread
  394. Interval in seconds during which process was blocked
  395.          261
  396. Interface name
  397. en0
  398. ---------------------------------------------------------------------------
  399. LABEL:          TS_NIM_ERROR_STUCK_
  400. IDENTIFIER:     3D32B80D
  401. Date/Time:       Mon Mar  8 19:11:36 BEIST 2010
  402. Sequence Number: 2905
  403. Machine Id:      00C879D24C00
  404. Node Id:         app
  405. Class:           S
  406. Type:            PERM
  407. Resource Name:   topsvcs
  408. Description
  409. NIM thread blocked
  410. Probable Causes
  411. A thread in a Topology Services Network Interface Module (NIM) process
  412. was blocked
  413. Topology Services NIM process cannot get timely access to CPU
  414. User Causes
  415. Excessive memory consumption is causing high memory contention
  416. Excessive disk I/O is causing high memory contention
  417.         Recommended Actions
  418.         Examine I/O and memory activity on the system
  419.         Reduce load on the system
  420.         Tune virtual memory parameters
  421.         Call IBM Service if problem persists
  422. Failure Causes
  423. Excessive virtual memory activity prevents NIM from making progress
  424. Excessive disk I/O traffic is interfering with paging I/O
  425.         Recommended Actions
  426.         Examine I/O and memory activity on the system
  427.         Reduce load on the system
  428.         Tune virtual memory parameters
  429.         Call IBM Service if problem persists
  430. Detail Data
  431. DETECTING MODULE
  432. rsct,nim_control.C,1.39.1.22,5947
  433. ERROR ID
  434. 6BUfAx.chBZ9/tkA./oD2g0...................
  435. REFERENCE CODE
  436. Thread which was blocked
  437. main thread
  438. Interval in seconds during which process was blocked
  439.          260
  440. Interface name
  441. tty0
  442. ---------------------------------------------------------------------------
  443. LABEL:          TS_NIM_ERROR_STUCK_
  444. IDENTIFIER:     3D32B80D
  445. Date/Time:       Mon Mar  8 19:11:36 BEIST 2010
  446. Sequence Number: 2904
  447. Machine Id:      00C879D24C00
  448. Node Id:         app
  449. Class:           S
  450. Type:            PERM
  451. Resource Name:   topsvcs
  452. Description
  453. NIM thread blocked
  454. Probable Causes
  455. A thread in a Topology Services Network Interface Module (NIM) process
  456. was blocked
  457. Topology Services NIM process cannot get timely access to CPU
  458. User Causes
  459. Excessive memory consumption is causing high memory contention
  460. Excessive disk I/O is causing high memory contention
  461.         Recommended Actions
  462.         Examine I/O and memory activity on the system
  463.         Reduce load on the system
  464.         Tune virtual memory parameters
  465.         Call IBM Service if problem persists
  466. Failure Causes
  467. Excessive virtual memory activity prevents NIM from making progress
  468. Excessive disk I/O traffic is interfering with paging I/O
  469.         Recommended Actions
  470.         Examine I/O and memory activity on the system
  471.         Reduce load on the system
  472.         Tune virtual memory parameters
  473.         Call IBM Service if problem persists
  474. Detail Data
  475. DETECTING MODULE
  476. rsct,nim_control.C,1.39.1.22,5947
  477. ERROR ID
  478. 6BUfAx.chBZ9/4JA./oD2g0...................
  479. REFERENCE CODE
  480. Thread which was blocked
  481. send thread
  482. Interval in seconds during which process was blocked
  483.          260
  484. Interface name
  485. en2
  486. ---------------------------------------------------------------------------
  487. LABEL:          TS_NIM_ERROR_STUCK_
  488. IDENTIFIER:     3D32B80D
  489. Date/Time:       Mon Mar  8 19:11:36 BEIST 2010
  490. Sequence Number: 2903
  491. Machine Id:      00C879D24C00
  492. Node Id:         app
  493. Class:           S
  494. Type:            PERM
  495. Resource Name:   topsvcs
  496. Description
  497. NIM thread blocked
  498. Probable Causes
  499. A thread in a Topology Services Network Interface Module (NIM) process
  500. was blocked
  501. Topology Services NIM process cannot get timely access to CPU
  502. User Causes
  503. Excessive memory consumption is causing high memory contention
  504. Excessive disk I/O is causing high memory contention
  505.         Recommended Actions
  506.         Examine I/O and memory activity on the system
  507.         Reduce load on the system
  508.         Tune virtual memory parameters
  509.         Call IBM Service if problem persists
  510. Failure Causes
  511. Excessive virtual memory activity prevents NIM from making progress
  512. Excessive disk I/O traffic is interfering with paging I/O
  513.         Recommended Actions
  514.         Examine I/O and memory activity on the system
  515.         Reduce load on the system
  516.         Tune virtual memory parameters
  517.         Call IBM Service if problem persists
  518. Detail Data
  519. DETECTING MODULE
  520. rsct,nim_control.C,1.39.1.22,5947
  521. ERROR ID
  522. 6BUfAx.chBZ9/At9./oD2g0...................
  523. REFERENCE CODE
  524. Thread which was blocked
  525. main thread
  526. Interval in seconds during which process was blocked
  527.          260
  528. Interface name
  529. en0
复制代码
机器:9119-595
OS:5300-08

800问了18M,得到答复是无大碍,持续观察
查了些资料,有一些说tty需要调优,还有说因为page space 操作过于频繁,

请各位师兄鉴定一下我的情况属于哪种?

如果不频繁报错的话,是否可以暂时忽略?

作者: zykoo   发布时间: 2010-03-30

18M说的是正确的。区分呢，就不能只看这个了，要看其他的。你不能只会看errpt 吧？

作者: 老农   发布时间: 2010-03-30

行,知道了. 最近持续观察一下.

谢谢,老农

作者: zykoo   发布时间: 2010-03-30

对了,如果block的时间持续过久是否会触发双机接管切换呢?

作者: zykoo   发布时间: 2010-03-30

时间过久   可能直接备机宕掉

作者: 349317925   发布时间: 2010-03-30

IBM 工程师的解释,提供给大家


直观理解是，两个节点间的通讯被阻塞了一定的时间。

如下的情况可能引起NIM阻塞：
1.当时系统忙，没有时间处理两个节点之间通讯，引起en/tty阻塞。
2.当时系统在做时间调整，会引en/tty起阻塞。
3.由于机房环境中的高频信号干扰，引起tty的阻塞。

对系统的影响：
短暂的阻隔，不会对系统造成伤害。
如果由于系统性能不佳，长时间阻断，会引起系统hang,系统发生hacmp切换

作者: zykoo   发布时间: 2010-03-31

直接备机就宕掉啦

作者: leikai   发布时间: 2010-03-31

备机就宕掉了?为什么会宕掉啊?

如果需要分析当时发生错误时操作系统的状况,还需要查哪些系统日志呢?

作者: zykoo   发布时间: 2010-03-31

DMS啊。备机以为心跳没了，备机准备接管，而其实心跳还在，发现主机还幸福而快乐地活着。但准备接管的命令已经发出去，为了避免冲突，备机干脆自杀以保全主机名节。

作者: orian   发布时间: 2010-03-31

orian的回答很形象啊

作者: relianni   发布时间: 2010-04-01

DMS啊。备机以为心跳没了，备机准备接管，而其实心跳还在，发现主机还幸福而快乐地活着。但准备接管的命令已 ...
orian 发表于 2010-3-31 21:55



    备机还是个烈妇啊，，，

作者: baochengchen   发布时间: 2010-04-01

备机比较忠诚。呵呵。

作者: 五“宅”一生   发布时间: 2010-04-07

很好。。。。学习了。。。。。谢谢啦！！！

作者: jiafan   发布时间: 2011-12-16

很好。。。。学习了。。。。。谢谢啦！！！

作者: jiafan   发布时间: 2011-12-16

相关阅读 更多

热门阅读

热门下载

更多
关于本站 免责申明 联系我们

Copyright 2006-2020 php爱好者(phpfans.net) All Rights Reserved.备案号：湘ICP备2023016114号-2

本站为非盈利性网站，不接受任何广告。本站所有资源均由网友上传，如有侵权，请发邮件至 [email protected] phpfans.net