bradboyington

triPOS Verifone Pad's Rebooting Daily

Discussion created by bradboyington on Oct 25, 2017
Latest reply on Oct 26, 2017 by jeff.gross@vantiv.com

Need some help here I have the verbose log here...  everyday we have stores where the pad just reboots at a specific time frame.    We show the VeriFone pad disconnects off the switch from the log files and it reloads all the forms then works correctly ..  This happens 1/2 times per day for some of our customers.   we have checked all power energy settings on the tri pos server.    and its set to not reboot.    is there some type of forced update agent in place?

 

2017-10-25 08:45:03,651 [STP SmartThreadPool Thread #954] triPOS TRACE - Recreating HMAC signature

2017-10-25 08:45:03,651 [STP SmartThreadPool Thread #954] triPOS TRACE - Building pipeline request

2017-10-25 08:45:03,651 [STP SmartThreadPool Thread #954] triPOS TRACE - Entering pipeline for idle request

2017-10-25 08:45:03,651 [STP SmartThreadPool Thread #954] triPOS TRACE - Creating a LaneContext for lane [1]

2017-10-25 08:45:03,651 [STP SmartThreadPool Thread #954] triPOS INFO  - PinPadConfig for lane [1]: BaudRate:9600, ComPort:, Driver:VeriFoneFormAgentXpi, IpAddress:10.100.1.11, IpPort:9001, TerminalType:PointOfSale

2017-10-25 08:45:03,651 [STP SmartThreadPool Thread #954] triPOS TRACE - Attempting to retrieve PIN pad with laneId:1

2017-10-25 08:45:03,666 [STP SmartThreadPool Thread #954] triPOS TRACE - PIN pad with laneId:1 was found?[True]

2017-10-25 08:45:03,666 [STP SmartThreadPool Thread #954] triPOS ERROR - Could not find a Configured PIN pad tethered to the lane specified in the request: 1

TriPos.Shared.Exceptions.LaneConfigurationNotFoundException: Could not find a Configured PIN pad tethered to the lane specified in the request: 1

   at TriPos.Pipeline.Common.LaneContextProvider.GetLane(ILaneIdentifier laneIdentifier)

   at TriPos.Pipeline.Processes.Transactions.Processes.IdlePipeline.ProcessRequest(IdleRequestDto request)

   at TriPos.Api.Services.IdleService.Post(IdleRequest request)

   at lambda_method(Closure , Object , Object )

   at ServiceStack.Host.ServiceRunner`1.Execute(IRequest request, Object instance, TRequest requestDto)

2017-10-25 08:45:03,666 [STP SmartThreadPool Thread #954] triPOS ERROR - [Service Exception Handler] Error error occured. Exception type: TriPos.Shared.Exceptions.LaneConfigurationNotFoundException, Exception message: Could not find a Configured PIN pad tethered to the lane specified in the request: 1

2017-10-25 08:45:18,636 [11] triPOS TRACE - Managing lanes.

2017-10-25 08:45:18,636 [11] triPOS TRACE - Attempting to remove orphaned PIN pads.

2017-10-25 08:45:18,636 [11] triPOS TRACE - Checking lane:1

2017-10-25 08:45:18,636 [11] triPOS TRACE - Attempting to retrieve PIN pad with laneId:1

2017-10-25 08:45:18,636 [11] triPOS TRACE - PIN pad with laneId:1 was found?[True]

2017-10-25 08:45:18,636 [11] triPOS TRACE - PIN pad connection status:False, for lane:1

2017-10-25 08:45:18,636 [11] triPOS TRACE - Starting PIN pad connection for lane:1

2017-10-25 08:45:18,668 [11] triPOS TRACE - VerifoneFAXPI XVER APP=4.7.5-20161025 XPIAPP=0053.00C XPIKERNEL=000027020 OS=MX200001/RFS30250800/ PACKAGES=alsa-lib:1.0.0; busybox:1.2.6.2501; captouch-flash:1.0.3.2501; cdgnetcfg:1.0.22.2509; cdgnetctrl:1.0.23.2509; dropbear:2012.55.3; ecr-lib:1.0.2; fancypants:1.0.20.2501; fonts-flash:1.0.10; hantrolib:1.0.6; i2c-tools:1.0.0; kmods:1.1.3; libgpl:1.0.0; libgraphic:1.0.3; libvp:1.0.8; libvpcfg:1.0.5; logapi:1.0.10.2504; logo_screen:1.0.0; mxlegacy:1.4.24; netutils:1.0.1; openssl:1.0.6; powermgt:1.0.18.2502; secins:1.12.10.2505; securemods:1.0.10.2502; security:1.3.10.2505; security-flash:4.2.6; skeletonfs:1.1.17.2516; svcstklibs:1.0.13; vfi-utils:1.2.16.2502; vfilib:1.1.23.2501; vfimods:1.1.28.2509; vfinetctrl:1.0.4; z_vats_unlock_rfs:1.0.0; z_vats_unlock_secrfs:1.0.0; zz_ctls_l2-security:1.0.32.00; zz_ctlshw-update:1.0.0; cgisvcstack:1.0.2; ecr-app:1.0.1; ecr-tools:1.0.1; mediaserver:1.0.6; svcmgrconfs:1.0.9; svcmgrstack:1.0.15; vfiservices:1.1.17.2512; vfiservices-dram:1.0.20.2504; vfiservices-flsh:1.0.12; vos-syslog-flash:1.0.0.2503; sred-version:4.1.83; vcl:4.1.83.1451; sysmode:1.5.24.2503; sysmode-themes:1.0.24.2503; zz_ctls_l2:4-1.12.02QA03H; powermgtctl:1.0.18.2502; powermgtctl-flash:1.0.16.2502; vhq_svc:1.0.7.1451; vhq_sys:1.4.9.1451; vhq_sys-certs:1.4.9.1451; printd:1.0.13; bin:1.0; configini:2.0; configusr1:2.1; faflash:2.1; fafrms:1.2; frmAgent:4.7.5; guimgr:3.25; lib_aci:2.4; lib_bintable:2.0; lib_ctls:2.30n; lib_dbg:2.13; lib_emvtbl:1.4; lib_ini:1.6; lib_odu:1.9; lib_rfcr:5.26; lib_rsa:4.2; lib_tcpip:2.0.19; lib_vcl:2.0; lib_vhq:2.5; lib_vsd:2.3; lib_xpiapp:5300c2; libs_other:1.2; pubkey:1.0; script:1.8; ssl:1.0; xpi:aslib2; xpifrms:161017; xpivss:1.0; ~triPosFormAgentBg:1.0.0; ~triPosFormAgentForms:1.1.4; ~triPosP2peConfig:1.0.0; ~triPosP2peFiles:1.0.0; ~triPosXpiBg:1.0.0; ~triPosXpiForms:1.1.0 GUIMGR=3.23 UNITID=284-227-488/12000000 MODEL=MX925 RFIDFW=VOS-CTLS-4-1.12.02H TCPIP=2.0.19 CLOCK=20171025134518 SECUREPACKETS=AES128

2017-10-25 08:45:18,668 [11] triPOS DEBUG - VerifoneFAXPI XVER response pair=XVER

2017-10-25 08:45:19,949 [11] triPOS TRACE - PIN pad connected for lane:1

2017-10-25 08:45:19,949 [11] triPOS TRACE - PIN pad connection status:True, for lane:1

2017-10-25 08:45:24,684 [11] triPOS TRACE - Configuring PIN pad on lane:1

2017-10-25 08:45:26,528 [11] triPOS TRACE - Did not find 'VeriFoneFormAgentXpiPinPadDownloadList.json' disk file

2017-10-25 08:45:26,528 [11] triPOS TRACE - Disk list 'VeriFoneFormAgentXpiPinPadDownloadList.json' not found

2017-10-25 08:45:26,528 [11] triPOS TRACE - Found 'TriPos.PinPads.Resources.VeriFoneFormAgentXpiPinPadDownloadList.json' resource file

2017-10-25 08:45:26,528 [11] triPOS TRACE - List has 6 items after merge

2017-10-25 08:45:26,528 [11] triPOS TRACE - List has 6 items after duplicates removed

2017-10-25 08:45:26,528 [11] triPOS INFO  - VerifoneFAXPI found 6 files in download list

2017-10-25 08:45:26,528 [11] triPOS INFO  - VerifoneFAXPI resource file name: dl.zhotfix-SC4-USB-OTG-4.2.7-PROD.tgz version: 4.2.7 package: zhotfix.os-USB-OTG

2017-10-25 08:45:26,528 [11] triPOS INFO  - VerifoneFAXPI resource file name: DL.CTLS_L2_CD4_1.12.02H-prod.tgz version: 1.0.0 package: zz_ctlshw-update

2017-10-25 08:45:26,544 [11] triPOS INFO  - VerifoneFAXPI ingoring USB file because transport is TCP/IP name: dl-fa435-xpi5200p3-usb_150824.tgz version: 4.3.5

2017-10-25 08:45:26,544 [11] triPOS INFO  - VerifoneFAXPI resource file name: dl-fa435-xpi5200p3-tcpip_150824.tgz version: 4.3.5 package: frmAgent

2017-10-25 08:45:26,544 [11] triPOS INFO  - VerifoneFAXPI resource file name: dl-triPOS.Mx.P2PE-1.0.0.tgz version: 1.0.0 package: ~triPosP2peConfig

2017-10-25 08:45:26,544 [11] triPOS INFO  - VerifoneFAXPI resource file name: dl-triPOS.Mx.FORMS-1.1.4.tgz version: 1.1.4 package: ~triPosFormAgentForms

2017-10-25 08:45:26,544 [11] triPOS INFO  - VerifoneFAXPI file should be downloaded because no other instance found on the PIN pad, name: dl.zhotfix-SC4-USB-OTG-4.2.7-PROD.tgz version: 4.2.7 package: zhotfix.os-USB-OTG

2017-10-25 08:45:26,544 [11] triPOS TRACE - VerifoneFAXPI downloading resource file name: dl.zhotfix-SC4-USB-OTG-4.2.7-PROD.tgz version: 4.2.7

2017-10-25 08:45:27,012 [11] triPOS TRACE - Found 'TriPos.PinPads.Resources.dl.zhotfix-SC4-USB-OTG-4.2.7-PROD.tgz' resource file

2017-10-25 08:45:35,279 [11] triPOS TRACE - VerifoneFA waiting for install after file download

2017-10-25 08:45:37,482 [11] triPOS TRACE - VerifoneFA install time 2.2 seconds

2017-10-25 08:45:37,482 [11] triPOS TRACE - VerifoneFAXPI waiting for reboot after file download

2017-10-25 08:45:38,592 [STP SmartThreadPool Thread #955] triPOS WARN  - The tp-request-id header was not found. It is highly recommened to supply a unique tp-request-id header with each request. The tp-request-id header should be a UUID/GUID that contains 32 hex digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

2017-10-25 08:45:38,592 [STP SmartThreadPool Thread #955] triPOS TRACE - Recreating HMAC signature

2017-10-25 08:45:38,592 [STP SmartThreadPool Thread #955] triPOS TRACE - Creating a LaneContext for lane [1]

2017-10-25 08:45:38,607 [STP SmartThreadPool Thread #955] triPOS INFO  - PinPadConfig for lane [1]: BaudRate:9600, ComPort:, Driver:VeriFoneFormAgentXpi, IpAddress:10.100.1.11, IpPort:9001, TerminalType:PointOfSale

2017-10-25 08:45:38,607 [STP SmartThreadPool Thread #955] triPOS TRACE - Attempting to retrieve PIN pad with laneId:1

2017-10-25 08:45:38,607 [STP SmartThreadPool Thread #955] triPOS TRACE - PIN pad with laneId:1 was found?[True]

2017-10-25 08:45:38,607 [STP SmartThreadPool Thread #955] triPOS ERROR - POST error

TriPos.Shared.Exceptions.LaneConfigurationNotFoundException: Could not find a Configured PIN pad tethered to the lane specified in the request: 1

   at TriPos.Pipeline.Common.LaneContextProvider.GetLane(ILaneIdentifier laneIdentifier)

   at TriPos.Api.Services.SaleService.ProcessRegularSale(SaleRequest request, SaleResponse response)

   at TriPos.Api.Services.SaleService.Post(SaleRequest request)

2017-10-25 08:47:20,009 [STP SmartThreadPool Thread #956] triPOS WARN  - The tp-request-id header was not found. It is highly recommened to supply a unique tp-request-id header with each request. The tp-request-id header should be a UUID/GUID that contains 32 hex digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

2017-10-25 08:47:20,009 [STP SmartThreadPool Thread #956] triPOS TRACE - Recreating HMAC signature

2017-10-25 08:47:20,009 [STP SmartThreadPool Thread #956] triPOS TRACE - Creating a LaneContext for lane [1]

2017-10-25 08:47:20,009 [STP SmartThreadPool Thread #956] triPOS INFO  - PinPadConfig for lane [1]: BaudRate:9600, ComPort:, Driver:VeriFoneFormAgentXpi, IpAddress:10.100.1.11, IpPort:9001, TerminalType:PointOfSale

2017-10-25 08:47:20,009 [STP SmartThreadPool Thread #956] triPOS TRACE - Attempting to retrieve PIN pad with laneId:1

2017-10-25 08:47:20,009 [STP SmartThreadPool Thread #956] triPOS TRACE - PIN pad with laneId:1 was found?[True]

2017-10-25 08:47:20,009 [STP SmartThreadPool Thread #956] triPOS ERROR - POST error

TriPos.Shared.Exceptions.LaneConfigurationNotFoundException: Could not find a Configured PIN pad tethered to the lane specified in the request: 1

   at TriPos.Pipeline.Common.LaneContextProvider.GetLane(ILaneIdentifier laneIdentifier)

   at TriPos.Api.Services.SaleService.ProcessRegularSale(SaleRequest request, SaleResponse response)

   at TriPos.Api.Services.SaleService.Post(SaleRequest request)

2017-10-25 08:47:35,573 [STP SmartThreadPool Thread #957] triPOS WARN  - The tp-request-id header was not found. It is highly recommened to supply a unique tp-request-id header with each request. The tp-request-id header should be a UUID/GUID that contains 32 hex digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

2017-10-25 08:47:35,573 [STP SmartThreadPool Thread #957] triPOS TRACE - Recreating HMAC signature

2017-10-25 08:47:35,573 [STP SmartThreadPool Thread #957] triPOS TRACE - Creating a LaneContext for lane [1]

2017-10-25 08:47:35,573 [STP SmartThreadPool Thread #957] triPOS INFO  - PinPadConfig for lane [1]: BaudRate:9600, ComPort:, Driver:VeriFoneFormAgentXpi, IpAddress:10.100.1.11, IpPort:9001, TerminalType:PointOfSale

2017-10-25 08:47:35,573 [STP SmartThreadPool Thread #957] triPOS TRACE - Attempting to retrieve PIN pad with laneId:1

2017-10-25 08:47:35,573 [STP SmartThreadPool Thread #957] triPOS TRACE - PIN pad with laneId:1 was found?[True]

2017-10-25 08:47:35,588 [STP SmartThreadPool Thread #957] triPOS ERROR - POST error

TriPos.Shared.Exceptions.LaneConfigurationNotFoundException: Could not find a Configured PIN pad tethered to the lane specified in the request: 1

   at TriPos.Pipeline.Common.LaneContextProvider.GetLane(ILaneIdentifier laneIdentifier)

   at TriPos.Api.Services.SaleService.ProcessRegularSale(SaleRequest request, SaleResponse response)

   at TriPos.Api.Services.SaleService.Post(SaleRequest request)

2017-10-25 08:48:03,169 [11] triPOS TRACE - VerifoneFAXPI XVER APP=4.7.5-20161025 XPIAPP=0053.00C XPIKERNEL=000027020 OS=MX200001/RFS30250800/ PACKAGES=alsa-lib:1.0.0; busybox:1.2.6.2501; captouch-flash:1.0.3.2501; cdgnetcfg:1.0.22.2509; cdgnetctrl:1.0.23.2509; dropbear:2012.55.3; ecr-lib:1.0.2; fancypants:1.0.20.2501; fonts-flash:1.0.10; hantrolib:1.0.6; i2c-tools:1.0.0; kmods:1.1.3; libgpl:1.0.0; libgraphic:1.0.3; libvp:1.0.8; libvpcfg:1.0.5; logapi:1.0.10.2504; logo_screen:1.0.0; mxlegacy:1.4.24; netutils:1.0.1; openssl:1.0.6; powermgt:1.0.18.2502; secins:1.12.10.2505; securemods:1.0.10.2502; security:1.3.10.2505; security-flash:4.2.6; skeletonfs:1.1.17.2516; svcstklibs:1.0.13; vfi-utils:1.2.16.2502; vfilib:1.1.23.2501; vfimods:1.1.28.2509; vfinetctrl:1.0.4; z_vats_unlock_rfs:1.0.0; z_vats_unlock_secrfs:1.0.0; zz_ctls_l2-security:1.0.32.00; zz_ctlshw-update:1.0.0; cgisvcstack:1.0.2; ecr-app:1.0.1; ecr-tools:1.0.1; mediaserver:1.0.6; svcmgrconfs:1.0.9; svcmgrstack:1.0.15; vfiservices:1.1.17.2512; vfiservices-dram:1.0.20.2504; vfiservices-flsh:1.0.12; vos-syslog-flash:1.0.0.2503; sred-version:4.1.83; vcl:4.1.83.1451; sysmode:1.5.24.2503; sysmode-themes:1.0.24.2503; zz_ctls_l2:4-1.12.02QA03H; powermgtctl:1.0.18.2502; powermgtctl-flash:1.0.16.2502; vhq_svc:1.0.7.1451; vhq_sys:1.4.9.1451; vhq_sys-certs:1.4.9.1451; printd:1.0.13; bin:1.0; configini:2.0; configusr1:2.1; faflash:2.1; fafrms:1.2; frmAgent:4.7.5; guimgr:3.25; lib_aci:2.4; lib_bintable:2.0; lib_ctls:2.30n; lib_dbg:2.13; lib_emvtbl:1.4; lib_ini:1.6; lib_odu:1.9; lib_rfcr:5.26; lib_rsa:4.2; lib_tcpip:2.0.19; lib_vcl:2.0; lib_vhq:2.5; lib_vsd:2.3; lib_xpiapp:5300c2; libs_other:1.2; pubkey:1.0; script:1.8; ssl:1.0; xpi:aslib2; xpifrms:161017; xpivss:1.0; ~triPosFormAgentBg:1.0.0; ~triPosFormAgentForms:1.1.4; ~triPosP2peConfig:1.0.0; ~triPosP2peFiles:1.0.0; ~triPosXpiBg:1.0.0; ~triPosXpiForms:1.1.0 GUIMGR=3.23 UNITID=284-227-488/12000000 MODEL=MX925 RFIDFW=VOS-CTLS-4-1.12.02H TCPIP=2.0.19 CLOCK=20171025134802 SECUREPACKETS=AES128

2017-10-25 08:48:03,185 [11] triPOS DEBUG - VerifoneFAXPI XVER response pair=XVER

2017-10-25 08:48:03,185 [11] triPOS INFO  - VerifoneFAXPI found file on PIN pad, name: zz_ctlshw-update package: zz_ctlshw-update

2017-10-25 08:48:03,185 [11] triPOS INFO  - VerifoneFAXPI file should not be downloaded because same or less version found on the PIN pad, name: DL.CTLS_L2_CD4_1.12.02H-prod.tgz download version: 1.0.0 PIN pad version: 1.0.0 package: zz_ctlshw-update

2017-10-25 08:48:03,185 [11] triPOS INFO  - VerifoneFAXPI found file on PIN pad, name: frmAgent package: frmAgent

2017-10-25 08:48:03,185 [11] triPOS INFO  - VerifoneFAXPI file should not be downloaded because same or less version found on the PIN pad, name: dl-fa435-xpi5200p3-tcpip_150824.tgz download version: 4.3.5 PIN pad version: 4.7.5 package: frmAgent

2017-10-25 08:48:03,185 [11] triPOS INFO  - VerifoneFAXPI found file on PIN pad, name: ~triPosP2peConfig package: ~triPosP2peConfig

2017-10-25 08:48:03,185 [11] triPOS INFO  - VerifoneFAXPI file should not be downloaded because same or less version found on the PIN pad, name: dl-triPOS.Mx.P2PE-1.0.0.tgz download version: 1.0.0 PIN pad version: 1.0.0 package: ~triPosP2peConfig

2017-10-25 08:48:03,185 [11] triPOS INFO  - VerifoneFAXPI found file on PIN pad, name: ~triPosFormAgentForms package: ~triPosFormAgentForms

Outcomes