Network Scan causes engine panic.
- This topic has 13 replies, 6 voices, and was last updated 13 years, 9 months ago by
.
-
Topic
-
Last Thursday our compliance group had an outside company performing a vulnerability scan on our network. The scan was at the ‘port scanning’ stage when all three of our engines panic’d and went down: [cmd :cmd :INFO/0:fr_starCLO_cmd] Receiving a command
PANIC: “str != ((char *) 0)”
PANIC: Calling “pti” for thread fr_starCLO_cmd
Scheduler State
Thread Events State Priority Runnable PT Msgs
0 0 SCHED_RUNNING 0 0 0,0,0
1 1 SCHED_IDLE 0 1 0,0,0
2 1 SCHED_IDLE 0 1 0,0,0
3 1 SCHED_IDLE 0 1 0,0,0
4 1 SCHED_IDLE 0 1 0,0,0
5 1 SCHED_IDLE 0 1 0,0,0
6 1 SCHED_IDLE 0 1 0,0,0
7 1 SCHED_IDLE 0 1 0,0,0
8 1 SCHED_IDLE 0 1 0,0,0
end of log:
PANIC: Calling “dbi shutdown” for thread fr_starCLO_cmd
PANIC: Calling “dbi shutdown” for thread fr_starCLO_xlate
PANIC: Calling “dbi shutdown” for thread ib_xp6
PANIC: Calling “dbi shutdown” for thread ob_ishelfadt
PANIC: Calling “dbi shutdown” for thread ob_maclab
PANIC: Calling “dbi shutdown” for thread ob_muse
PANIC: Calling “dbi shutdown” for thread ob_pacs
PANIC: Calling “dbi shutdown” for thread ob_sm
PANIC: Calling “dbi shutdown” for thread ob_sq
PANIC: Calling “dbi shutdown” for thread ob_maclab
03/27/2008 12:58:17
[dbi :dbi :WARN/0: ob_maclab] NULL DTD when closing DBI
PANIC: Calling “dbi shutdown” for thread ob_maclab
03/27/2008 12:58:17
[dbi :dbi :WARN/0: ob_maclab] NULL DTD when closing DBI
PANIC: Thread panic—engine going down
PANIC: assertion ‘str != ((char *) 0)’ failed at str.cpp/36
We’re on 5.3 rev3 on Windows 2003. Everyone is now very concerned that we have a ‘major’ vulnerability on our interface engines. Can anyone comment on this?
Thank you very much for any insight you may have.
- The forum ‘Cloverleaf’ is closed to new topics and replies.
