ORIGINAL: player The IPS engine is killing the fw, how can i kill the process?
If you' ve not interested in IPS, disable it completely with CLI: diagnose ips global all status disable ' killing' daemon processes could cause unstabilities in your box
ips signatures are not active - not used in any protection profile that' s the issue the ipsengine process is running with 89% ... how do i locate the signal of this process or the pid ? the sys top is only showing the cpu%
if i show with diag sys top i get (in this case MR6P2): ----- Run Time: 0 days, 15 hours and 3 minutes 1U, 1S, 96I; 250T, 125F, 55KF newcli 425 R 0.9 2.1 thttp 52 S 0.0 7.9 ipsengine 185 S < 0.0 6.1 ipsengine 186 S < 0.0 5.9 cmdbsvr 17 S 0.0 3.9 pop3 47 S 0.0 3.8 httpsd 78 S 0.0 3.7 httpsd 64 S 0.0 3.7 httpsd 40 S 0.0 2.8 scanunitd 423 S < 0.0 2.7 scanunitd 422 S < 0.0 2.2 miglogd 38 S 0.0 2.2 newcli 411 S 0.0 2.1 iked 62 S 0.0 2.1 merged_daemons 49 S 0.0 2.1 updated 63 S 0.0 2.0 imd 56 S 0.0 1.9 urlfilter 55 S 0.0 1.9 nsmon 74 S 0.0 1.9 nsm 33 S 0.0 1.9 haproxy 73 S 0.0 1.9 sshd 410 S 0.0 1.8 fdsmgmtd 65 S 0.0 1.8 authd 59 S 0.0 1.8 smtp 46 S 0.0 1.7 ftpd 53 S 0.0 1.7 fgfmd 75 S 0.0 1.7 dhcpd 67 S 0.0 1.7 snmpd 66 S 0.0 1.7 sshd 69 S 0.0 1.7 forticron 50 S 0.0 1.7 zebos_launcher 31 S 0.0 1.7 quard 71 S 0.0 1.6 imapd 51 S 0.0 1.6 nntpd 60 S 0.0 1.6 ntpd 68 S < 0.0 1.6 ipsmonitor 184 S 0.0 1.6 miglogd 39 S 0.0 1.6 getty 45 S < 0.0 1.6 uploadd 37 S 0.0 1.6 alertmail 72 S 0.0 1.5 telnetd 70 S 0.0 1.5 httpclid 61 S 0.0 1.5 imi 54 S 0.0 1.0 bgpd 36 S 0.0 0.9 pimd 41 S 0.0 0.8 ospfd 35 S 0.0 0.8 ripd 34 S 0.0 0.8 pdmd 42 S 0.0 0.7 proxyd 43 S 0.0 0.7 initXXXXXXXXXXX 1 S 0.0 0.6 pid 185/186 are the ipsengine diag sys kill 9 pid (in this case 185 and next 186) i kill them . Michael
sound like you never use a UNIX/Linux Box. The 9 or maybe 1-15 cames from the UNIX Command kill see also: http://www.decf.berkeley.edu/help/unix/kill.html and also: http://kc.forticare.com/default.asp?id=1655&Lang=1