免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 8395 | 回复: 9

heartbeat IPaddr2 monitor timeout [复制链接]

论坛徽章:
0
发表于 2010-01-16 09:43 |显示全部楼层
10可用积分
各位同学,

现在我使用了heartbeat 2.1.3 版本于生产系统。

发现了两次IPaddr2 monitor timeout,  不知是linux系统的原因, 还是heartbeat的bug,
希望见过类似问题的同学, 能否分享一下。


heartbeat  利用 IPaddr2 这个resource agent 监控ip,  我用heartbeat有一年半了,
用于生产系统也有一年左右的时间。 所以相信在配置上应该没有问题。

现在偶发了两次很奇怪的问题。IPaddr2 monitor 竟然 timeout,
heartbeat发现这种情况后,  会去restart一下这个resource group,
如何restart呢, 先stop  service resrouce agent
(什么叫resource agent呢, 例如我们写一个支持ocf规范的shell脚本, 称为resource agent, 来管理我们的应用进程。),
再 stop IPaddr2 这个resource agent.
结果呢, stop service resrouce agent 时又超时(20秒的timer啊), 而我那个service resrouce agent 的stop操作非常简单,
没有block的地方, 它竟然超时20秒。

这会引起heartbeat对service resrouce agent脱管, 变成所谓 un-managed.
我开始以为是时间漂移, 后来发现不是的。

但是在出问题的这段时间内(38秒), 的确我们有个其他进程在做备份操作, 会占用大量的I/O,
但是我想也不至于让操作系统瘫痪的地步。 毕竟这个操作每天这个点都做, 为什么单单就这一天会影响到heartbeat呢 ?

如果这是heartbeat的bug, 我想网上早就有这样的案例, 但是没有搜索到类似的问题, 所以我想应该不是heartbeat的问题。

不知道各位同学在使用时有没有碰到类似问题。企盼分享一下。



+++++++++++++++++++++++++++++++++++++++++  /var/log/ha-debug  +++++++++++++

iptv_user_agent[1443][1454]: 2009/12/19_19:02:08 INFO: user_agent running
iptv_user_agent[1483][1494]: 2009/12/19_19:02:10 INFO: user_agent running
iptv_user_agent[1495][1534]: 2009/12/19_19:02:16 INFO: user_agent running
lrmd[4456]: 2009/12/19_19:02:18 WARN: IPaddr2_1:monitor process (PID 1497) timed out (try 1).  Killing with signal SIGTERM (15).
lrmd[4456]: 2009/12/19_19:02:18 WARN: operation monitor[24] on ocf::IPaddr2::IPaddr2_1 for client 4459, its parameters: CRM_meta_interval=[5000] ip=[172.17.5.15] cidr_netmask=[24] CRM_meta_id=[IPaddr2_1_mon] CRM_meta_timeout=[5000] crm_feature_set=[2.0] iflabel=[0] CRM_meta_name=[monitor] nic=[eth1] : pid [1497] timed out
crmd[4459]: 2009/12/19_19:02:18 ERROR: process_lrm_event: LRM operation IPaddr2_1_monitor_5000 (24) Timed Out (timeout=5000ms)
tengine[11725]: 2009/12/19_19:02:19 info: process_graph_event: Detected action IPaddr2_1_monitor_5000 from a different transition: 8 vs. 18
tengine[11725]: 2009/12/19_19:02:19 info: update_abort_priority: Abort priority upgraded to 1000000
tengine[11725]: 2009/12/19_19:02:19 WARN: update_failcount: Updating failcount for IPaddr2_1 on f7a40064-99bc-4647-aea2-a064cbc762be after failed monitor: rc=-2
crmd[4459]: 2009/12/19_19:02:19 info: do_state_transition: State transition S_IDLE -> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_IPC_MESSAGE origin=route_message ]
crmd[4459]: 2009/12/19_19:02:19 info: do_state_transition: All 2 cluster nodes are eligible to run resources.
pengine[11726]: 2009/12/19_19:02:20 info: determine_online_status: Node aaa-a is online
pengine[11726]: 2009/12/19_19:02:20 info: common_apply_stickiness: Setting failure stickiness for IPaddr2_1 on aaa-a: -100
pengine[11726]: 2009/12/19_19:02:20 WARN: unpack_rsc_op: Processing failed op IPaddr2_1_monitor_5000 on aaa-a: Timed Out
pengine[11726]: 2009/12/19_19:02:20 info: determine_online_status: Node aaa-b is online
pengine[11726]: 2009/12/19_19:02:20 notice: group_print: Resource Group: group_1
pengine[11726]: 2009/12/19_19:02:20 notice: native_print:     IPaddr2_1 (heartbeat:cf:IPaddr2):       Started aaa-a FAILED
pengine[11726]: 2009/12/19_19:02:20 notice: native_print:     iptv_user_agent   (heartbeat:cf:iptv_user_agent):       Started aaa-a
pengine[11726]: 2009/12/19_19:02:20 notice: NoRoleChange: Recover resource IPaddr2_1    (aaa-a)
pengine[11726]: 2009/12/19_19:02:20 notice: StopRsc:   aaa-a    Stop IPaddr2_1
pengine[11726]: 2009/12/19_19:02:20 notice: StartRsc:  aaa-a    Start IPaddr2_1
pengine[11726]: 2009/12/19_19:02:20 notice: RecurringOp: aaa-a     IPaddr2_1_monitor_5000
pengine[11726]: 2009/12/19_19:02:20 notice: NoRoleChange: Leave resource iptv_user_agent        (aaa-a)
crmd[4459]: 2009/12/19_19:02:21 info: do_state_transition: State transition S_POLICY_ENGINE -> S_TRANSITION_ENGINE [ input=I_PE_SUCCESS cause=C_IPC_MESSAGE origin=route_message ]
tengine[11725]: 2009/12/19_19:02:21 info: unpack_graph: Unpacked transition 19: 11 actions in 11 synapses
tengine[11725]: 2009/12/19_19:02:21 info: te_pseudo_action: Pseudo action 13 fired and confirmed
tengine[11725]: 2009/12/19_19:02:21 info: send_rsc_command: Initiating action 9: iptv_user_agent_stop_0 on aaa-a
crmd[4459]: 2009/12/19_19:02:21 info: do_lrm_rsc_op: Performing op=iptv_user_agent_stop_0 key=9:19:cf4b6798-33c3-4fcb-880c-0b87b803ba39)
iptv_user_agent[1535][1547]: 2009/12/19_19:02:23 INFO: user_agent running
crmd[4459]: 2009/12/19_19:02:23 info: process_lrm_event: LRM operation iptv_user_agent_monitor_2000 (call=26, rc=-2) Cancelled
lrmd[4456]: 2009/12/19_19:02:23 info: rsc:iptv_user_agent: stop
pengine[11726]: 2009/12/19_19:02:25 info: process_pe_message: Transition 19: PEngine Input stored in: /var/lib/heartbeat/pengine/pe-input-79.bz2
pengine[11726]: 2009/12/19_19:02:25 ERROR: subsystem_msg_dispatch: pengine took 5570ms to complete
iptv_user_agent[1576][1586]: 2009/12/19_19:02:25 INFO: user_agent: enter iptv_stop
iptv_user_agent[1576][1587]: 2009/12/19_19:02:25 INFO: generate user_agent alarm
tengine[11725]: 2009/12/19_19:02:41 WARN: action_timer_callback: Timer popped (abort_level=0, complete=false)
tengine[11725]: 2009/12/19_19:02:41 WARN: print_elem: Action missed its timeout[Action 9]: In-flight (id: iptv_user_agent_stop_0, loc: aaa-a, priority: 0)
lrmd[4456]: 2009/12/19_19:02:43 WARN: iptv_user_agent:stop process (PID 1576) timed out (try 1).  Killing with signal SIGTERM (15).
lrmd[4456]: 2009/12/19_19:02:43 info: RA output: (iptv_user_agent:stop:stderr)
Session terminated, killing shell...
crmd[4459]: 2009/12/19_19:02:43 ERROR: process_lrm_event: LRM operation iptv_user_agent_stop_0 (27) Timed Out (timeout=20000ms)
lrmd[4456]: 2009/12/19_19:02:43 WARN: operation stop[27] on ocf::iptv_user_agent::iptv_user_agent for client 4459, its parameters: CRM_meta_timeout=[20000] crm_feature_set=[2.0] : pid [1576] timed out
tengine[11725]: 2009/12/19_19:02:43 info: status_from_rc: Re-mapping op status to LRM_OP_ERROR for rc=-2

论坛徽章:
0
发表于 2010-01-16 10:35 |显示全部楼层
希望heartbeat的爱好者和有使用经验的多多发言。

使用heartbeat有一两年了, 真是爱恨交加。
感觉写heartbeat的人因该是牛人, 但是好像几乎没有人后续维护,
所以有不少小问题。

heartbeat是保护service的, 往往service没事, 敏感的heartbeat到出了问题, 反倒把service给干掉了。

不知道使用过heartbeat的有何感受。

分享一下。

论坛徽章:
0
发表于 2010-01-18 13:51 |显示全部楼层

回复 #2 leeedward 的帖子

现在基本确定下来了。

这不是heartbeat自身的问题, 是一个其他的进程在做备份操作,  会占用大量的memory,
操作系统 过了较长时间才会调度到这个IPaddr2 monitor 进程。
(我做了一个简单的实验, 一个最简单的shell脚本, 被block约10秒才被执行。)

其实当时memory还有很多free, 但是这个备份进程会连续将 200M Bytes 大小的memory sync到disk.
不知OS为什么会短暂的hicup。

我会将IPaddr2 monitor的timer从5秒调大到约60秒, 来规避这个问题。

特此分享一下。

论坛徽章:
0
发表于 2012-02-23 14:02 |显示全部楼层
我也遇到过time out 问题跟你的很像,不过我这边是cpu很高,不知道为什么会很高

论坛徽章:
0
发表于 2012-08-16 10:06 |显示全部楼层
楼主帮我也看看,我这个也遇到个monitor timeout ,不知道是不是与你这个有些类似
lrmd[22856]: 2012/08/10_23:00:18 WARN: ipservice:monitor process (PID 6516) timed out (try 1).  Killing with signal SIGTERM (15).
lrmd[22856]: 2012/08/10_23:00:18 WARN: operation monitor[17] on lsb::ipresources::ipservice for client 22859, its parameters: CRM_meta_interval=[5000] CRM_meta_id=[ipmon] CRM_meta_timeout=[10000] crm_feature_set=[2.0] CRM_meta_description=[ipmonitors] CRM_meta_name=[monitor] : pid [6516] timed out
crmd[22859]: 2012/08/10_23:00:18 ERROR: process_lrm_event: LRM operation ipservice_monitor_5000 (17) Timed Out (timeout=10000ms)
tengine[22875]: 2012/08/10_23:00:18 info: process_graph_event: Action ipservice_monitor_5000 arrived after a completed transition
tengine[22875]: 2012/08/10_23:00:18 info: update_abort_priority: Abort priority upgraded to 1000000
tengine[22875]: 2012/08/10_23:00:18 WARN: update_failcount: Updating failcount for ipservice on 98f8988d-dde0-437d-b4d4-2127401130a8 after failed monitor: rc=-2
crmd[22859]: 2012/08/10_23:00:18 info: do_state_transition: State transition S_IDLE -> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_IPC_MESSAGE origin=route_message ]
crmd[22859]: 2012/08/10_23:00:18 info: do_state_transition: All 1 cluster nodes are eligible to run resources.
pengine[22876]: 2012/08/10_23:00:18 notice: unpack_config: On loss of CCM Quorum: Ignore
pengine[22876]: 2012/08/10_23:00:18 info: determine_online_status: Node ha1 is online
pengine[22876]: 2012/08/10_23:00:18 info: common_apply_stickiness: Setting failure stickiness for ipservice on ha1: -200
pengine[22876]: 2012/08/10_23:00:18 WARN: unpack_rsc_op: Processing failed op ipservice_monitor_5000 on ha1: Timed Out
pengine[22876]: 2012/08/10_23:00:20 notice: group_print: Resource Group: group_1
tengine[22875]: 2012/08/10_23:00:20 info: extract_event: Aborting on transient_attributes changes for 98f8988d-dde0-437d-b4d4-2127401130a8
pengine[22876]: 2012/08/10_23:00:20 notice: native_print:     ipservice        (lsb:ipresources):        Started ha1 FAILED
tengine[22875]: 2012/08/10_23:00:20 WARN: notify_crmd: Delaying completion until all CIB updates complete
tengine[22875]: 2012/08/10_23:00:20 info: te_update_diff: Aborting on transient_attributes deletions
pengine[22876]: 2012/08/10_23:00:20 notice: NoRoleChange: Recover resource ipservice        (ha1)
tengine[22875]: 2012/08/10_23:00:20 WARN: notify_crmd: Delaying completion until all CIB updates complete
pengine[22876]: 2012/08/10_23:00:20 notice: StopRsc:   ha1        Stop ipservice
pengine[22876]: 2012/08/10_23:00:20 notice: StartRsc:  ha1        Start ipservice
pengine[22876]: 2012/08/10_23:00:20 notice: RecurringOp: ha1           ipservice_monitor_5000
pengine[22876]: 2012/08/10_23:00:20 info: process_pe_message: Transition 212: PEngine Input stored in: /var/lib/heartbeat/pengine/pe-input-212.bz2
pengine[22876]: 2012/08/10_23:00:20 notice: unpack_config: On loss of CCM Quorum: Ignore
pengine[22876]: 2012/08/10_23:00:20 info: determine_online_status: Node ha1 is online
pengine[22876]: 2012/08/10_23:00:20 info: common_apply_stickiness: Setting failure stickiness for ipservice on ha1: -300
pengine[22876]: 2012/08/10_23:00:20 WARN: unpack_rsc_op: Processing failed op ipservice_monitor_5000 on ha1: Timed Out
pengine[22876]: 2012/08/10_23:00:20 notice: group_print: Resource Group: group_1
pengine[22876]: 2012/08/10_23:00:20 notice: native_print:     ipservice        (lsb:ipresources):        Started ha1 FAILED
pengine[22876]: 2012/08/10_23:00:20 WARN: native_color: Resource ipservice cannot run anywhere
pengine[22876]: 2012/08/10_23:00:20 notice: StopRsc:   ha1        Stop ipservice
crmd[22859]: 2012/08/10_23:00:20 info: do_state_transition: State transition S_POLICY_ENGINE -> S_TRANSITION_ENGINE [ input=I_PE_SUCCESS cause=C_IPC_MESSAGE origin=route_message ]
tengine[22875]: 2012/08/10_23:00:20 info: unpack_graph: Unpacked transition 213: 4 actions in 4 synapses
tengine[22875]: 2012/08/10_23:00:20 info: te_pseudo_action: Pseudo action 8 fired and confirmed
tengine[22875]: 2012/08/10_23:00:20 info: send_rsc_command: Initiating action 2: ipservice_stop_0 on ha1
crmd[22859]: 2012/08/10_23:00:20 info: do_lrm_rsc_op: Performing op=ipservice_stop_0 key=2:213:b44f9dac-4adf-4fe5-b5fa-97facac3f586)
lrmd[22856]: 2012/08/10_23:00:20 info: rsc:ipservice: stop
crmd[22859]: 2012/08/10_23:00:20 info: process_lrm_event: LRM operation ipservice_monitor_5000 (call=17, rc=-2) Cancelled
lrmd[6527]: 2012/08/10_23:00:20 WARN: For LSB init script, no additional parameters are needed.
pengine[22876]: 2012/08/10_23:00:20 WARN: process_pe_message: Transition 213: WARNINGs found during PE processing. PEngine Input stored in: /var/lib/heartbeat/pengine/pe-warn-0.bz2
pengine[22876]: 2012/08/10_23:00:20 info: process_pe_message: Configuration WARNINGs found during PE processing.  Please run "crm_verify -L" to identify issues.
lrmd[22856]: 2012/08/10_23:00:20 info: RA output: (ipservice:stop:stdout) Stopping ldirectord...
lrmd[22856]: 2012/08/10_23:00:21 info: RA output: (ipservice:stop:stdout) success

论坛徽章:
3
天秤座
日期:2014-10-29 11:37:572015元宵节徽章
日期:2015-03-06 15:50:39NBA常规赛纪念章
日期:2015-05-04 22:32:03
发表于 2013-05-17 13:27 |显示全部楼层
怎么会fired 呢,把资源给解雇了??
我也这样啊。不知道咋回事

  1. heartbeat[6983]: 2013/05/16_13:00:39 info: glib: ucast: write socket priority set to IPTOS_LOWDELAY on eth1
  2. heartbeat[6983]: 2013/05/16_13:00:39 info: glib: ucast: bound send socket to device: eth1
  3. "ha-log" 9410L, 1018003C
  4. pengine[27850]: 2013/05/17_11:10:44 info: unpack_rsc_op: Remapping httpd_2_monitor_120000 (rc=7) on intel-01 to an ERROR (expected 0)
  5. pengine[27850]: 2013/05/17_11:10:44 WARN: unpack_rsc_op: Processing failed op httpd_2_monitor_120000 on intel-01: Error
  6. pengine[27850]: 2013/05/17_11:10:44 info: unpack_rsc_op: Remapping httpd_2_start_0 (rc=1) on intel-01 to an ERROR (expected 0)
  7. pengine[27850]: 2013/05/17_11:10:44 WARN: unpack_rsc_op: Processing failed op httpd_2_start_0 on intel-01: Error
  8. pengine[27850]: 2013/05/17_11:10:44 WARN: unpack_rsc_op: Compatability handling for failed op httpd_2_start_0 on intel-01
  9. pengine[27850]: 2013/05/17_11:10:44 notice: group_print: Resource Group: group_1
  10. pengine[27850]: 2013/05/17_11:10:44 notice: native_print:     IPaddr_192_168_7_189      (ocf::heartbeat:IPaddr):        Started intel-02
  11. pengine[27850]: 2013/05/17_11:10:44 notice: native_print:     httpd_2   (lsb:httpd):    Started intel-02
  12. pengine[27850]: 2013/05/17_11:10:44 WARN: native_color: Resource httpd_2 cannot run anywhere
  13. pengine[27850]: 2013/05/17_11:10:44 notice: NoRoleChange: Leave resource IPaddr_192_168_7_189   (Started intel-02)
  14. pengine[27850]: 2013/05/17_11:10:44 notice: NoRoleChange: Stop resource httpd_2 (Started intel-02)
  15. pengine[27850]: 2013/05/17_11:10:44 notice: StopRsc:   intel-02 Stop httpd_2
  16. crmd[27835]: 2013/05/17_11:10:44 info: do_state_transition: State transition S_POLICY_ENGINE -> S_TRANSITION_ENGINE [ input=I_PE_SUCCESS cause=C_IPC_MESSAGE origin=route_message ]
  17. tengine[27849]: 2013/05/17_11:10:44 info: process_te_message: Processing graph derived from /var/lib/heartbeat/pengine/pe-warn-40.bz2
  18. tengine[27849]: 2013/05/17_11:10:44 info: unpack_graph: Unpacked transition 10: 4 actions in 4 synapses
  19. tengine[27849]: 2013/05/17_11:10:44 info: te_pseudo_action: Pseudo action 11 fired and confirmed
  20. tengine[27849]: 2013/05/17_11:10:44 info: send_rsc_command: Initiating action 8: stop httpd_2_stop_0 on intel-02
  21. pengine[27850]: 2013/05/17_11:10:44 WARN: process_pe_message: Transition 10: WARNINGs found during PE processing. PEngine Input stored in: /var/lib/heartbeat/pengine/pe-warn-40.bz2
  22. crmd[27835]: 2013/05/17_11:10:44 info: do_lrm_rsc_op: Performing op=httpd_2_stop_0 key=8:10:0:2a241abe-1246-4478-830a-f0bb697001c0)
  23. pengine[27850]: 2013/05/17_11:10:44 info: process_pe_message: Configuration WARNINGs found during PE processing.  Please run "crm_verify -L" to identify issues.
  24. lrmd[27832]: 2013/05/17_11:10:44 info: rsc:httpd_2: stop
  25. lrmd[10451]: 2013/05/17_11:10:44 WARN: For LSB init script, no additional parameters are needed.
  26. lrmd[27832]: 2013/05/17_11:10:44 info: RA output: (httpd_2:stop:stdout) Stopping httpd:
  27. lrmd[27832]: 2013/05/17_11:10:44 info: RA output: (httpd_2:stop:stdout) [
  28. lrmd[27832]: 2013/05/17_11:10:44 info: RA output: (httpd_2:stop:stdout)   OK  ]^M
  29. lrmd[27832]: 2013/05/17_11:10:44 info: RA output: (httpd_2:stop:stdout)

  30. crmd[27835]: 2013/05/17_11:10:44 info: process_lrm_event: LRM operation httpd_2_stop_0 (call=12, rc=0) complete
  31. tengine[27849]: 2013/05/17_11:10:44 info: match_graph_event: Action httpd_2_stop_0 (8) confirmed on intel-02 (rc=0)
  32. tengine[27849]: 2013/05/17_11:10:44 info: te_pseudo_action: Pseudo action 12 fired and confirmed
  33. tengine[27849]: 2013/05/17_11:10:44 info: te_pseudo_action: Pseudo action 2 fired and confirmed
  34. tengine[27849]: 2013/05/17_11:10:44 info: run_graph: Transition 10: (Complete=4, Pending=0, Fired=0, Skipped=0, Incomplete=0)
  35. tengine[27849]: 2013/05/17_11:10:44 info: notify_crmd: Transition 10 status: te_complete - <null>
  36. crmd[27835]: 2013/05/17_11:10:44 info: do_state_transition: State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS cause=C_IPC_MESSAGE origin=route_message ]
复制代码

论坛徽章:
3
天秤座
日期:2014-10-29 11:37:572015元宵节徽章
日期:2015-03-06 15:50:39NBA常规赛纪念章
日期:2015-05-04 22:32:03
发表于 2013-05-17 14:58 |显示全部楼层
回复 5# 402550990


    你这个问题是怎么解决的?

论坛徽章:
16
IT运维版块每日发帖之星
日期:2015-10-02 06:20:00IT运维版块每月发帖之星
日期:2015-09-11 19:30:52IT运维版块每周发帖之星
日期:2015-09-11 19:20:31IT运维版块每日发帖之星
日期:2015-08-26 06:20:00每日论坛发贴之星
日期:2015-08-20 06:20:00IT运维版块每日发帖之星
日期:2015-08-20 06:20:002015年辞旧岁徽章
日期:2015-03-03 16:54:15金牛座
日期:2014-05-04 16:58:09双子座
日期:2013-12-17 16:44:37辰龙
日期:2013-11-22 15:20:59狮子座
日期:2013-11-18 22:55:08射手座
日期:2013-11-12 10:54:26
发表于 2013-05-17 17:47 |显示全部楼层
timeout=5000ms
能把这个值给改的大一些么?
试一下

论坛徽章:
3
天秤座
日期:2014-10-29 11:37:572015元宵节徽章
日期:2015-03-06 15:50:39NBA常规赛纪念章
日期:2015-05-04 22:32:03
发表于 2013-05-17 18:10 |显示全部楼层
回复 8# wenhq


    你是说, 修改这里的timeout?
  1.       
  2.         <primitive class="lsb" id="httpd_2" provider="heartbeat" type="httpd">
  3.            <operations>
  4.              <op id="httpd_2_mon" interval="120s" name="monitor" timeout="60s" start_delay="0" disabled="false" role="Started"/>
  5.            </operations>
  6.            <meta_attributes id="httpd_2_meta_attrs">
  7.              <attributes>
  8.                <nvpair id="httpd_2_metaattr_resource_stickiness" name="resource_stickiness" value="100"/>
  9.                <nvpair id="httpd_2_metaattr_resource_failure_stickiness" name="resource_failure_stickiness" value="-20"/>
  10.              </attributes>
  11.            </meta_attributes>
  12.          </primitive>
复制代码

论坛徽章:
16
IT运维版块每日发帖之星
日期:2015-10-02 06:20:00IT运维版块每月发帖之星
日期:2015-09-11 19:30:52IT运维版块每周发帖之星
日期:2015-09-11 19:20:31IT运维版块每日发帖之星
日期:2015-08-26 06:20:00每日论坛发贴之星
日期:2015-08-20 06:20:00IT运维版块每日发帖之星
日期:2015-08-20 06:20:002015年辞旧岁徽章
日期:2015-03-03 16:54:15金牛座
日期:2014-05-04 16:58:09双子座
日期:2013-12-17 16:44:37辰龙
日期:2013-11-22 15:20:59狮子座
日期:2013-11-18 22:55:08射手座
日期:2013-11-12 10:54:26
发表于 2013-05-17 18:15 |显示全部楼层
本帖最后由 wenhq 于 2013-05-17 18:16 编辑

不对啊,看你的抱错是5000ms怎么配置里是60s呢?
难到还有别的设置?
anyway 试试把.
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP