IBM Support

PI43012: AGENT DOES NOT SHUT DOWN GRACEFULLY IF AGENT CANNOT RESOLVE HOSTNAMES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using the "agent stop" command on Unix systems, the stop
    script will attempt to call the "netstat" command in order to
    log out messages. The netstat command attempts to resolve
    hostnames. On certain systems where this functionality is not
    available, the command will hang forever, requiring the user to
    manually kill the agent process in order to completely shut down
    the agent.
    
    As a workaround, remove this line from the "agent" script to
    allow the agent to shut down:
    
    netstat | grep tcp > $AGENT_HOME/var/log/netstat.out
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When using the "agent stop" command on Unix systems, the     *
    * stop                                                         *
    * script will attempt to call the "netstat" command in order   *
    * to                                                           *
    * log out messages. The netstat command attempts to resolve    *
    * hostnames. On certain systems where this functionality is    *
    * not                                                          *
    * available, the command will hang forever, requiring the user *
    * to                                                           *
    * manually kill the agent process in order to completely shut  *
    * down                                                         *
    * the agent.                                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to UCD version 6.1.1.7                               *
    ****************************************************************
    

Problem conclusion

  • Fixed in UCD version 6.1.1.7
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI43012

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-06-15

  • Closed date

    2015-07-30

  • Last modified date

    2015-07-30

  • 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

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels

  • R600 PSN

       UP

  • R600 PSY

       UP

  • R601 PSN

       UP

  • R601 PSY

       UP

  • R610 PSN

       UP

  • R610 PSY

       UP

  • R611 PSN

       UP

  • R611 PSY

       UP

  • R612 PSN

       UP

  • R612 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"610","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 October 2021