5010 (D50D) Cannot Register with WMS

Tagged: , , , ,

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #51195
    wkatsak
    Participant
    • Total Post: 2
    • Newbie

    Hello,

    I have a number of Wyse Suse Linux terminals (5010-D50D) that I would like to move over to WMS, but I cannot seem to get them to register.

    I’ve upgraded the firmware to 11.3.110, and installed platform_util-1.0.4-0.1 as well as wda-2.0.13-00.1.

    I’ve tried configuring via DHCP as well as DNS. My current DNS configuration works for a brand new 3040 ThinOS box (I stood this up as a test).

    Output from the wda.log is as follows:

    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) CommandQueue::ParseAndExecuteJSONCommand(), Attempting discovery 2 time
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) CommandQueue::ParseAndExecuteJSONCommand() DiscDataDNSRecords
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) recordname = _WMS_CAVALIDATION, disctype = txt
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) DNSLookup::FetchTextRecord, data read for text record = FALSE
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) recordname = _WMS_GROUPTOKEN, disctype = txt
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) DNSLookup::FetchTextRecord, data read for text record = defaluzerneterms
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) recordname = _WMS_MGMT, disctype = srv
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) DNSLookup::fetch_srv_record srv_response = 0
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) DNSLookup::fetch_srv_record hostname = wmsvm-access.mydomain.local
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) DNSLookup::fetch_srv_record port = 443
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) recordname = _WMS_MQTT, disctype = srv
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) DNSLookup::fetch_srv_record srv_response = 0
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) DNSLookup::fetch_srv_record hostname = wmsvm-access.mydomain.local
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) DNSLookup::fetch_srv_record port = 1883
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) CommandQueue::ValidateDHCPInfo() ValidateDHCPInf discData size=4
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) StratusProtocol(): ValidateDHCPInf
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) StratusProtocol::ValidateDHCPInf() Discovery data:_WMS_CAVALIDATION:FALSE
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) CAvaliaton Tag Found with value = FALSE
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) HttpClient(): Entered ConvertCAValidationToLong, strCAValidation = FALSE
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) StratusProtocol::ValidateDHCPInf() Discovery data:_WMS_GROUPTOKEN:defaluzerneterms
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) StratusProtocol::ValidateDHCPInf() Discovery data:_WMS_MGMT._tcp:wmsvm-access.mydomain.local:443
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) StratusProtocol::ValidateDHCPInf() Discovery data:_WMS_MQTT._tcp:wmsvm-access.mydomain.local:1883
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) ProtocolModule() : ValidateDHCPInf() strmacaddress=84:7b:eb:ed:06:8a
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) HttpClient() GenerateUserAgentString():User-Agent: Stratus /2.7.0.0 CCM_AGENT (Linux 3.0.101-84-pae; en_US.utf8; i686; Revision:REV ; cls: A )
    Tue Nov 12 18:39:13 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) HttpClient(): SendGroupRegRequest
    Tue Nov 12 18:39:43 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) HttpClient(): CurlRegistrationRequest() CURLcode=28, http_code=0
    Tue Nov 12 18:39:43 2019 – 3049954160 – [ WDA ] <ERROR> :src/ProtocolLogger.cpp(112) HttpClient(): SendGroupRegRequest(): failed.
    Tue Nov 12 18:39:43 2019 – 3049954160 – [ WDA ] <ERROR> :src/ProtocolLogger.cpp(112) HttpClient(): CheckResponse
    Tue Nov 12 18:39:43 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) HttpClient(): HandleJSONError
    Tue Nov 12 18:39:43 2019 – 3049954160 – [ WDA ] <ERROR> :src/ProtocolLogger.cpp(112) HttpClient(): CheckResponse() response:
    Tue Nov 12 18:39:43 2019 – 3049954160 – [ WDA ] <ERROR> :src/ProtocolLogger.cpp(112) StratusProtocol() ValidateDHCPInf() SendGroupRegRequest FAILURE
    Tue Nov 12 18:39:43 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) StratusProtocol() CheckFailureResult() PR_FAILURE.
    Tue Nov 12 18:39:43 2019 – 3049954160 – [ WDA ] <INFO> :src/ProtocolLogger.cpp(70) CommandQueu::ValidateDHCPInfo() rResult=1
    Tue Nov 12 18:39:43 2019 – 3049954160 – [ WDA ] <ERROR> :src/ProtocolLogger.cpp(112) CommandQueue::ParseandExecuteJSONCommand(), Failed to validate DNS Data

    Any pointers would be appreciated.

    Thanks in advance!

    Sincerely,
    Bill

     

    #51208
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Have you tried to enter the WMS information manually in the WDA agent?

    CG

    #51217
    wkatsak
    Participant
    • Total Post: 2
    • Newbie

    I didn’t, because I am not on-site.

    The weird part is that I was able to get it to register to WMS Pro (Cloud) using an INI file config, but the exact same INI (just changed CA flag) would not work with local WMS 14 (fresh install).

    It may be a moot point because admin agreed to spring for WMS cloud licenses, but its pretty annoying.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.