IBM Support

JR62824: ELASTICSEARCH IN THE PFS-VALIDATE TOOL FAILS IF THE PROCESS FEDERATION SERVER MACHINE HAS MULTIPLE NETWORK INTERFACES

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

Direct link to fix

 

APAR status

  • Closed as program error.

Error description

  • The pfs-validate tool compares the nodes that are declared in
    the discovery.zen.ping.unicast.hosts IBM Process Federation
    Server configuration property with what the ElasticSearch API
    GET /_nodes/stats returns. If the Process Federation Server
    machine has more than one network interface, the configuration
    and the output of the GET request might differ, which causes the
     ElasticSearch validation in the pfs-validate tool to fail.
    
    Although this failure doesn't introduce functional issues with
    Process Federation Server, the error message is something like
    the following examples:
    
    The following Elasticsearch node configured in the
    discovery.zen.ping.unicast.hosts attribute has not joined the
    cluster: Host name:terence2 Port:9300
    *** If the node is running, check the system logs for connection
    issues.
    *** Check the SSL setting, the cluster name, and the passphrase
    definitions for this Elasticsearch node.
    
    The following Elasticsearch node configured in the
    discovery.zen.ping.unicast.hosts attribute has not joined the
    cluster: Host name:terence3 Port:9301
    *** If the node is running, check the system logs for connection
    issues.
    *** Check the SSL setting, the cluster name, and the passphrase
    definitions for this Elasticsearch node.
    
    The following Elasticsearch node configured in the
    discovery.zen.ping.unicast.hosts attribute has not joined the
    cluster: Host name:terence3 Port:9302
    *** If the node is running, check the system logs for connection
    issues.
    *** Check the SSL setting, the cluster name, and the passphrase
    definitions for this Elasticsearch node.
    
    PRODUCTS AFFECTED
    IBM Process Federation Server
    

Local fix

Problem summary

  • No additional information is available.
    

Problem conclusion

  • A fix is available or will be available that indicates you can
    ignore such errors.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR62824

  • Reported component name

    BUS AUTO WORKFL

  • Reported component ID

    5737H4100

  • Reported release

    J00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-09-18

  • Closed date

    2020-10-29

  • Last modified date

    2020-10-29

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    BUS AUTO WORKFL

  • Fixed component ID

    5737H4100

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"19.0.0.1"}]

Document Information

Modified date:
14 December 2020