Loading

Ask Data Process Failed To Start Up After Making Some Topology Change

Data pubblicazione: Apr 29, 2025
Descrizione

Ask Data process failed to start up after some topology change is made (or IP address(es) change), for example adding a new node on Tableau Server (or static IPs not being configured)

The following error(s) may be found in the stdout_nlp_node#-0.log:

"2022-11-30T10:25:35.3535497-05:00" level=error msg="failed to TryLock" error="failed to execute lock query [guard.go:114]: pq: no pg_hba.conf entry for host \"fe80::2264:1234:9876:2211%13\", user \"rails\", database \"workgroup\", SSL off"

"2022-12-03T22:24:32.0854708-06:00" level=error msg="failed to start server" error="failed to discover all required services [api.serve.go:151]: failed to update elastic server config via service discovery service [utils.go:73]: failed to list first elasticserver service instance info [client.go:304]: Failed to get random service instance {portType: primary, serviceName: elasticserver} [client.go:205]: ListServiceInstances failed: failed to connect: host may be invalid, or server unreachable [client.go:259]: rpc error: code = Unavailable desc = last connection error: connection error: desc = \"transport: Error while dialing dial tcp [fe80::9d56:9876:a234:9fe1%Ethernet0]:8491: connectex: No connection could be made because the target machine actively refused it.\""
Error: [/root/go/src/tableau/nlp/nlpcore/pegasus/tasks/api.serve.go:135]tried but failed to start server
For usage information, try `pegasus help api:serve`

Cause

IPv6 address is preferred over IPv4 address.

NOTE: Windows Server 2019 IPv6 default precedences changed from previous Windows Server versions, causing IPv6 to be preferred over IPv4.
Risoluzione
Use [netsh interface ipv6 show prefixpolicies] command to check the current precedence of multiple IP addresses, and use [netsh int ipv6 set prefixpolicy] command to modify the precedence. NOTE: These steps need to be performed on all Nodes. 

Below is an example where IPv6 is preferred over IPv4.

Precedence   Label  Prefix
----------  -----  --------------------------------
        50      0  ::1/128
        40      1  ::/0
        35      4  ::ffff:0:0/96
        30      2  2002::/16
         5      5  2001::/32
         3     13  fc00::/7
         1     11  fec0::/10
         1     12  3ffe::/16
         1      3  ::/96

To change the precedence to make sure IPv4 is preferred, you need to execute the following steps:
    a) Run [tsm stop] command to stop Tableau Server.
    b) Run the following commands to adjust precedences of IP addresses.
          netsh int ipv6 set prefixpolicy ::ffff:0:0/96 50 0
          netsh int ipv6 set prefixpolicy ::1/128 40 1
          netsh int ipv6 set prefixpolicy ::/0 30 2
          netsh int ipv6 set prefixpolicy  2002::/16 20 3
          netsh int ipv6 set prefixpolicy  2001::/32 5 5
          netsh int ipv6 set prefixpolicy  ::/96 1 4

NOTE: In HA or Multi-Node environments, the IPv6 changes MUST be done on all Nodes running Windows Server 2019.
 
    c) Reboot OS to flush IP connections and restart Tableau Server administrative services.
    d) Confirm all Tableau Server services are running and [tsm status -v] indicates that Tableau Server is stopped.
    e) Run [tsm pending-changes apply] - (This step is critical, even though there will be no changes to apply)
    f) Run [tsm start] command to start up Tableau Server.
Risorse aggiuntive
Also use [netsh interface ipv4 show interface] command to check if there is multiple NICs and they are in expected order.

Configure the Order of Network Interfaces

Numero articolo Knowledge

001534187

 
Caricamento
Salesforce Help | Article