Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
migacz
New Contributor III

emergency the killed daemon is

after upgrade firmware v5 build147 to build0179 (GA Patch 2) i receive such e-mails
 Message meets Alert condition
 The following critical firewall event was detected: Critical Event.
 date=2013-04-11 time=04:26:32 devname=FortiGate devid=FG100C3G08601537 logid=0100020000 type=event subtype=system level=emergency the killed daemon is /bin/scanunitd: status=0xf00
 
and status=0x9 where is problem? Should I be worried?
1 REPLY 1
RH2
New Contributor II

I opened a ticket about this and it is a " feature" now. When your fortigate gets an a/v database update it has to restart the scanunit daemon, so that creates a log entry that the scanunitd process was killed. The really annoying thing is that the entry for an av update is not " critical" so you don' t see an alert for that action so you can ignore the scanunitd notice.
Labels
Top Kudoed Authors