I have RNE 7.0 installed on RH Lynux. I've found 2 errors - is it bug or my problems - I don't know. Please help if someone have experience with such problems. Note: I have also RNE on Win2K Prof whith the same policy and the same advanced properties. It's working properly w/o problems.
1. I syslog a GREAT number of events, such as: ........................................................... application bug: issDaemon(25342) has SIGCHLD set to SIG_IGN but calls wait (). (see the NOTES section of 'man 2 wait'). Workaround activated. application bug: issDaemon(25342) has SIGCHLD set to SIG_IGN but calls wait (). (see the NOTES section of 'man 2 wait'). Workaround activated. application bug: issDaemon(25342) has SIGCHLD set to SIG_IGN but calls wait (). (see the NOTES section of 'man 2 wait'). Workaround activated. application bug: issDaemon(25342) has SIGCHLD set to SIG_IGN but calls wait (). (see the NOTES section of 'man 2 wait'). Workaround activated. application bug: issDaemon(25342) has SIGCHLD set to SIG_IGN but calls wait (). (see the NOTES section of 'man 2 wait'). Workaround activated. application bug: issDaemon(25342) has SIGCHLD set to SIG_IGN but calls wait (). (see the NOTES section of 'man 2 wait'). Workaround activated. application bug: issDaemon(25342) has SIGCHLD set to SIG_IGN but calls wait (). (see the NOTES section of 'man 2 wait'). Workaround activated. application bug: issDaemon(25342) has SIGCHLD set to SIG_IGN but calls wait (). (see the NOTES section of 'man 2 wait'). Workaround activated. application bug: issDaemon(25342) has SIGCHLD set to SIG_IGN but calls wait (). (see the NOTES section of 'man 2 wait'). Workaround activated. application bug: issDaemon(25342) has SIGCHLD set to SIG_IGN but calls wait (). (see the NOTES section of 'man 2 wait'). Workaround activated. application bug: issDaemon(25342) has SIGCHLD set to SIG_IGN but calls wait (). (see the NOTES section of 'man 2 wait'). Workaround activated. application bug: issDaemon(25342) has SIGCHLD set to SIG_IGN but calls wait (). (see the NOTES section of 'man 2 wait'). Workaround activated. application bug: issDaemon(25342) has SIGCHLD set to SIG_IGN but calls wait (). (see the NOTES section of 'man 2 wait'). Workaround activated. application bug: issDaemon(25342) has SIGCHLD set to SIG_IGN but calls wait (). (see the NOTES section of 'man 2 wait'). Workaround activated. application bug: issDaemon(25342) has SIGCHLD set to SIG_IGN but calls wait (). ................................................... But sensor still seems to be working good. Is this problem serious or I may forget about this and don't pay attention on it? 2. I decided to adjust pam.smb.password.guesses and set it to string such as: 111111,222222,123456,qwerty,555555. On windows sensor all was applayed well and now is working properly. But on Lynux I've got a error: Date/Time 2004-06-28 12:51:56 MSD Tag Name Sensor_Error Alert Name Sensor_Error Severity High Tag Brief Description Observance Type Informational Only Combined Event Count 1 Cleared Flag false Target DNS Name RNE1 Target IP Address Target Object Name No Object Found Target Object Type No Object Found Target Service Source DNS Name RNE1 Source IP Address SourcePort Name 0 Sensor DNS Name RNE1 Sensor IP Address 192.168.11.16 Sensor Name network_sensor_1 User Name :EventType Detector_Event Code c0000065 Message (network_sensor_1) - Exception detected inside PAM: internalError. The sensor is shutting down. And the sensor status becomes 'Stopped'. After I've removed pam.smb.password.guesses parameter from policy, and have reapplyed policy to sensors, sensors started to work well. What's the matter? Is it bug or something wrong with my sensors? Thanks very much. --- Best regards, Sergey V. Soldatov. tel/fax +7 095 745 89 50 (2663) _______________________________________________ ISSForum mailing list [EMAIL PROTECTED] TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo/issforum To contact the ISSForum Moderator, send email to [EMAIL PROTECTED] The ISSForum mailing list is hosted and managed by Internet Security Systems, 6303 Barfield Road, Atlanta, Georgia, USA 30328.
