TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------

I think we had the attachment stripped out of the Forum. Here is the detail
for everyone:

#############################################

RealSecure: RSfN 6.5 patch to address SIGCHLD errors  
  
ISS RealSecure for Nokia,   
for version: 6.5 Only
 
  
date modified: 05/17/2002  

This patch addresses issues where communication between the Event Collector
and RealSecure sensor stops and the sensor must be restarted. This is caused
by a memory leak issue which results in the following SIGCHLD error

"ISS[25140]: (network_sensor_name) - The Application received unexpected
SIGCHLD signal 20. The engine will exit."


Please Note: XPU 4.3 must be applied to the network sensor before applying
the patch.

 
SOLUTION  

To install the patch use the following guidelines:

1) Start with a fresh install of RealSecure Network Sensor ver. 6.5 on IPSO
3.4.1-FCS10

a) If an uninstall was performed beforehand, please remove the /opt/ISS
directory before installing the RSfN 6.5 package. (rm -R /opt/ISS)

b) You may wish to backup the .PubKey files to save you from having to
re-copy those up after the install. 
(Located under /opt/ISS/RealSecure6_5/Keys/CerticomNRA).

2) Apply XPU 4.3 to the sensor.

3) Once your RSNS6.5 install is completed, you will want to shutdown the
issdaemon (
/opt/ISS/issDaemon/issd -stop)

4) Make backups of the following files located in the /opt/ISS/RealSecure6_5
directory that will be replaced.

* issCSF
* libNetworkSensor.so
* CmnRspnses.so
* NSRspnses.so
* rsDisplay.so

5) Copy the files contained in the ipso_patch.tar.gz you download up to the
/opt/ISS/RealSecure6_5 directory.

6) Reboot the sensor.

Note: If you have dual sensors running on the Nokia Appliance you have to
apply the patch to the second sensor files located in the
/opt/ISS/network_sensor_2 directory


Downloads
ipso_patch.tar.gz [GZ - 3.4 MB]
MD5 459c3eaa9cff90d67b759bd9e323a496
 

-----Original Message-----
From: Williams, Ken [mailto:[EMAIL PROTECTED]]
Sent: 06 June 2002 17:12
To: 'Joy, Chris'; Williams, Ken
Cc: '[EMAIL PROTECTED]'
Subject: RE: Nokia Sensor 6.5


Yah This appears to be the same issue, which I've been encountering for
roughly a month now, we'll see if this patch works properly.

-----Original Message-----
From: Joy, Chris [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 06, 2002 7:43 AM
To: 'Williams, Ken'
Cc: '[EMAIL PROTECTED]'
Subject: RE: Nokia Sensor 6.5


Could be this known issue that I found on the Nokia support site.

I guess ISS can provide the patch too.

Chris

Dr Chris Joy
VP, OI Netcomms
Dresdner Kleinwort Wasserstein



-----Original Message-----
From: Williams, Ken [mailto:[EMAIL PROTECTED]]
Sent: 05 June 2002 23:51
To: '[EMAIL PROTECTED]'
Subject: Nokia Sensor 6.5



TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any
problems!
----------------------------------------------------------------------------

Hey has anyone encountered the nokia sensor crashing arbitrarily, (i'm aware
of the dhcp issue that signature is turned off in my policy). Here is the
information I receive from the logfile:

Jun  3 11:08:18 sentinel [LOG_ERR] ISS[2703]: (network_sensor_1) - The
Application received unexpected SIGCHLD signal 20. The engine will exit.

-Ken




----------------------------------------------------------------------
If you have received this e-mail in error or wish to read our e-mail 
disclaimer statement and monitoring policy, please refer to 
http://www.drkw.com/disc/email/ or contact the sender.
----------------------------------------------------------------------


----------------------------------------------------------------------
If you have received this e-mail in error or wish to read our e-mail 
disclaimer statement and monitoring policy, please refer to 
http://www.drkw.com/disc/email/ or contact the sender.
----------------------------------------------------------------------



Reply via email to