IJ45076: ON TADDM FP8 (1) APACHE SENSOR DISCOVERY FAILS DUE TO NPE (2) APACHE DISCOVERED DETAILS HAVING WRONG PROCESS POOL INFORMATION(NO

APAR status

• Closed as program error.

Error description

• On TADDM FP8,
  (1)Apache target discovery is failing due to
  NullPointerException.
  There was issue in parsing logic on the Listen directives from
  config file(httpd.conf), and port was set as "NULL"; resulting
  in NullPointerException.
  
  ----log snippet----
   ApacheServerScriptSensor-<IP> DEBUG
  sensor.ApacheASDConfigHelper - buildListenList: Directive:
  Listen 8420
   ApacheServerScriptSensor-<IP> DEBUG
  sensor.ApacheBaseConfigHelper - Error getting IntValue
  :java.lang.NullPointerException
   ApacheServerScriptSensor-<IP> DEBUG
  sensor.ApacheASDConfigHelper - buildListenList: Port=0
  ------------------
  
  (2) Apache targets that were discovered successfully, on DMP
  "RUNTIME" tab the details populated had wrong processpool
  information. It should have ROOT/parent process and it's details
  whereas it had information of child process.
  ---------log snippet which having ROOT PID------------
  PARAMS:13284 ApacheServerScriptSensor
  PARAMS:13912 ApacheServerScriptSensor
  PARAMS:14253 ApacheServerScriptSensor
  
  These are the parent PIDs in  ApacheServerScriptSensor
  
  Apache IHS instances discovered but ProcessPool were created
  with child PIDs, this is wrong.
  We can see in below logs evidence of other/child process details
  instead of ROOT process:
  ---------
  Trying to find RuntimeProcess for ip:port = 0.0.0.0 [(IP]:20443
  --- PID 14295 associated
  Trying to find RuntimeProcess for ip:port = 0.0.0.0 [(IP)]:20444
  --- PID 14293 associated
  Trying to find RuntimeProcess for ip:port = 0.0.0.0 [(IP)]:20445
  --- PID 13303 associated
  ---------
  
  In order to resolve above discussed issues
  (1)We need to modify/add the code with the required parsing
  logics for different configurations of Apache Listen directive,
  so that the port returned is correct.
  (2)We need to debug the code logic, to know how runtime process
  details are getting processed while creating ApacheServerSensor
  seed and which runtime process details were set during the
  discovery of Apache instances.
  

Local fix

• N/A
  

Problem summary

•  With TADDM 7.3.0.8 discovery of Apache target
  is failing due to a null pointer. On DMP "Runtime" tab it is
  populated with incorrect processPool infromation.
  

Problem conclusion

•  Analysis identified that Apache targets
  with Listen directive (in httpd.conf file) where hitting a
  NullPointerException during parsing of the Listen directive.
  Apache sensor code was updated to correct parsing of the LISTEN
  directive.
  The fix for this APAR is contained in maintenance package:
   | Fix Pack| 7.3.0-TIV-ITADDM-FP0011
  

Temporary fix

•  n/a
  

Comments

APAR Information

• 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

  APP DEPENDENCY

• Fixed component ID

  5724N5500

Applicable component levels