IBM Support

IC89342: SCP LOG TARGET MAY CAUSE SYSTEM HANG IF SCP SERVER IS UNRESPONSIVE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • SCP log target may cause system hang if the SCP server is
    unresponsive during time of file upload.
    
    The appliance may remain in a hung/wait state for up to 130
    seconds before it recovers and resumes processing.
    The log may show successive inactivity errors during the time
    of the hang:
    
    system,error,,,0,,0x80400025,,,"Watchdog system detects no
    activity for at least 49 seconds"
    
    system,critic,,,0,,0x80400025,,,"Watchdog system detects no
    activity for at least 50 seconds"
    
    
    Also, once the appliance recovers, the following log target
    errors may be seen at the end of the inactivity errors:
    
    [system][error] logging target(scp-log): tid(415730367): File
    not found.
    
    [system][error] logging target(scp-log): tid(415730367): Log
    upload of target scp-log failed.
    

Local fix

  • Use Syslog log target instead.
    

Problem summary

  • Affected are users of all firmware releases up to and including
    version 5.0.0.x using log targets with SCP or SFTP upload
    method.
    
    SCP/SFTP log target may cause system halt if the the
    target SCP/SFTP server is unresponsive during time of file
    upload.
    
    The appliance may remain in a wait state for up to 130
    seconds before it recovers and resumes processing.
    
    Fix will be provided in a next major release. No formal fix is
    planned for the current releases.
    

Problem conclusion

Temporary fix

  • The safest workaround for the problem is to use upload method
    other than SCP or SFTP.
    

Comments

APAR Information

  • APAR number

    IC89342

  • Reported component name

    DATAPOWER BLAD

  • Reported component ID

    DPBLADE01

  • Reported release

    382

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-04

  • Closed date

    2013-01-17

  • Last modified date

    2013-02-19

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

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

Fix information

Applicable component levels

  • R195 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFGB5","label":"WebSphere DataPower Integration Blade XI50B"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.8.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
19 February 2013