고객지원

질문과 답변 (Q&A)

자주 묻는 질문(FAQ) 에서 원하는 답변을 찾지 못하셨을 경우 문의해 주세요.
최대한 빠르게 답변해 드리겠습니다.

XCom

제품문의 S1F1 응답이 늦어지는 문제 2018-08-17
최상규 skchoi@kohyoun.gocm 200
안녕하세요. 제품 사용 중에 이슈가 있어서 문의드립니다.

S1F1 응답이 18:27:32 ~ 35(3초), 18:29:32 ~ 18:29:40 (8초) 로 늦어지더니 18:31:38에 socket error=10053이 발생하였습니다.

S1F1은 XCOM Driver에서 해주는 것으로 알고 있는데, 이 응답이 느려지는 원인과 해결 방안을 문의드립니다.

이상입니다.



18:27:32 [SECS-II:Rcv]
S1, F1 [Are You There Request (R)], Device ID = 0, WBit = 1, SystemByte = 00000BE8
18:27:35 [SECS-II:Send]
S1, F2 [On Line Data (D)], Device ID = 0, WBit = 0, SystemByte = 00000BE8
LIST, 2
ASCII, 1, [MDLN] <0>
ASCII, 6, [SOFTREV] <2.2.10>
18:27:36 [Socket:Send]
00 00 00 17 00 00 01 02 00 00 00 00 0B E8 01 02 41 01 30 41 06 32 2E 32 2E 31 30
18:28:01 [Socket:Rcv]
00 00 00 0A FF FF 00 00 00 05 80 00 2F 17
18:28:02 [HSMS:Rcv] Linktest.req, 80002F17
18:28:03 [HSMS:Send] Linktest.rsp, 80002F17
18:28:04 [Socket:Send]
00 00 00 0A FF FF 00 00 00 06 80 00 2F 17
18:28:33 [Socket:Rcv]
00 00 00 0A FF FF 00 00 00 05 80 00 2F 18
18:28:34 [HSMS:Rcv] Linktest.req, 80002F18
18:28:38 [HSMS:Send] Linktest.rsp, 80002F18
18:28:39 [Socket:Send]
00 00 00 0A FF FF 00 00 00 06 80 00 2F 18
18:29:09 [Socket:Rcv]
00 00 00 0A FF FF 00 00 00 05 80 00 2F 19
18:29:10 [HSMS:Rcv] Linktest.req, 80002F19
18:29:13 [HSMS:Send] Linktest.rsp, 80002F19
18:29:14 [Socket:Send]
00 00 00 0A FF FF 00 00 00 06 80 00 2F 19
18:29:32 [Socket:Rcv]
00 00 00 0A 00 00 81 01 00 00 00 00 0B E9
18:29:32 [SECS-II:Rcv]
S1, F1 [Are You There Request (R)], Device ID = 0, WBit = 1, SystemByte = 00000BE9
18:29:40 [SECS-II:Send]
S1, F2 [On Line Data (D)], Device ID = 0, WBit = 0, SystemByte = 00000BE9
LIST, 2
ASCII, 1, [MDLN] <0>
ASCII, 6, [SOFTREV] <2.2.10>
18:29:41 [Socket:Send]
00 00 00 17 00 00 01 02 00 00 00 00 0B E9 01 02 41 01 30 41 06 32 2E 32 2E 31 30
18:29:44 [Socket:Rcv]
00 00 00 0A FF FF 00 00 00 05 80 00 2F 1A
18:29:45 [HSMS:Rcv] Linktest.req, 80002F1A
18:29:46 [HSMS:Send] Linktest.rsp, 80002F1A
18:29:47 [Socket:Send]
00 00 00 0A FF FF 00 00 00 06 80 00 2F 1A
18:30:17 [Socket:Rcv]
00 00 00 0A FF FF 00 00 00 05 80 00 2F 1B
18:30:18 [HSMS:Rcv] Linktest.req, 80002F1B
18:30:21 [HSMS:Send] Linktest.rsp, 80002F1B
18:30:22 [Socket:Send]
00 00 00 0A FF FF 00 00 00 06 80 00 2F 1B
18:30:52 [Socket:Rcv]
00 00 00 0A FF FF 00 00 00 05 80 00 2F 1C
18:30:52 [HSMS:Rcv] Linktest.req, 80002F1C
18:30:56 [HSMS:Send] Linktest.rsp, 80002F1C
18:30:57 [Socket:Send]
00 00 00 0A FF FF 00 00 00 06 80 00 2F 1C
18:31:27 [Socket:Rcv]
00 00 00 0A FF FF 00 00 00 05 80 00 2F 1D
18:31:28 [HSMS:Rcv] Linktest.req, 80002F1D
18:31:31 [HSMS:Send] Linktest.rsp, 80002F1D
18:31:37 [Socket:Send]
00 00 00 0A FF FF 00 00 00 06 80 00 2F 1D
18:31:38 [Proc:Alarm] socket error=10053 : connection closed in socket event
18:31:39 [HSMS:Event] Socket closed
18:31:40 [Proc:Event] handling network close
18:31:41 [HSMS:State] State Changed : Selected -> Not Connected
18:31:42 [Proc:Alarm] Passive HSMS will restart after T5.
18:31:53 [Proc:Event] XCom restarting
18:31:53 [Proc:Event] XCom Stopped
18:31:54 [Proc:Event] XCom Started
18:31:56 [Proc:Event] XCom restarted
18:32:12 [I/F:Alarm] Cannot send S1F13 [system bytes=0000a238] - Not selected state; -12004
18:32:13 [SECS-II:Send] XCom.Send() failed
18:32:16 [HSMS:State] State Changed : Not Connected -> Not Selected
18:32:17 [Socket:Rcv]
00 00 00 0A FF FF 00 00 00 01 80 00 2F 21
18:32:18 [Socket:Rcv]
00 00 00 0A FF FF 00 00 00 09 80 00 2F 22
18:32:19 [HSMS:Rcv] Select.req, 80002F21
18:32:20 [HSMS:Send] Select.rsp, 80002F21
18:32:21 [Proc:Alarm] socket error=10054 : connection closed by forign host
18:32:21 [Proc:Alarm] Socket send data error: 10054
18:32:22 [Socket:Dump] dump of message stream failed sending for the socket error (10054), elapsed time=1891631104
00 00 00 0A FF FF 00 00 00 02 80 00 2F 21
18:32:23 [Proc:Alarm] socket error=0 : connection closed in socket event
18:32:24 [HSMS:Event] Socket closed
18:32:25 [HSMS:Rcv] Separate.req, 80002F22
18:32:26 [HSMS:Rcv] HSMS control message was received in HSMS NOT SELECTED state, sysbyte=80002F22
18:32:27 [Proc:Alarm] HSMS receive error [-12004]
18:32:28 [HSMS:Alarm] T7 Timeout
18:32:28 [Proc:Event] HSMS socket was closed.
18:32:29 [HSMS:State] State Changed : Not Selected -> Not Connected
18:32:33 [Proc:Event] XCom restarting
18:32:34 [Proc:Event] XCom Stopped
18:32:35 [Proc:Event] XCom Started
18:32:36 [Proc:Event] XCom restarted
18:32:43 [Proc:Event] XCom restarting
18:32:43 [Proc:Event] XCom Stopped
18:32:44 [Proc:Event] XCom Started
18:32:45 [Proc:Event] XCom restarted
18:32:49 [HSMS:State] State Changed : Not Connected -> Not Selected
18:32:51 [Socket:Rcv]
00 00 00 0A FF FF 00 00 00 01 80 00 2F 25
18:32:52 [HSMS:Rcv] Select.req, 80002F25
18:32:53 [HSMS:Send] Select.rsp, 80002F25
18:32:54 [Socket:Send]
00 00 00 0A FF FF 00 00 00 02 80 00 2F 25
18:32:55 [HSMS:State] State Changed : Not Selected -> Selected
18:32:59 [Socket:Rcv]
00 00 00 0A FF FF 00 00 00 05 80 00 2F 26 00 00 00 0C 00 00 81 0D 00 00 80 00 20 83 01 00
18:33:00 [HSMS:Rcv] Linktest.req, 80002F26
18:33:01 [HSMS:Send] Linktest.rsp, 80002F26
18:33:02 [Socket:Send]
00 00 00 0A FF FF 00 00 00 06 80 00 2F 26
==================================================
안녕하세요

링크제니시스입니다.

Socket Error 는 XCom이 발생시키는 것이 아니고 윈도우 소켓에서 발생하는 Microsoft의 WinSock Error Code 입니다.

소켓 에러가 발생되면 XCom 을 종료하고 재시작하고 재연결 시도를 합니다.

https://msdn.microsoft.com/en-us/library/ms740668(VS.85).aspx

문제가 발생하기 전부터 S1F1 응답이 점점 느려졌다가 Socket Closed 가 되었다면 네트워크에 문제가 있을 수 있습니다.

이상입니다.
감사합니다.


답변 목록

  답변XCom제품문의S1F1 응답이 늦어지는 문제2018-08-17


  이전글XCom운영중문의XGEM Configuration 내의 Report 항목 사라지는 문제.
  다음글XCom제품문의Host 끊김현상 관련 내용 문의