If there are no web filter logs, the below are the checks which needs to be done :
1) Make sure that the web filter profile has been applied in the LAN to WAN policy and Deep Inspection is applied in policy.
2) Logging is enabled as All Session.
3) The Severity of the logging is set as Information depending on where the logging is enabled Memory/Disk
If logging is enabled on Memory :
# config log memory filterset severity informationend
If logging is enabled on Disk:# config log disk filterNow, refresh the GUI and check whether the web filter logs are visible.
set severity information
end
If not:
4) Restart the logging process.
- Check the logging process ID:# diag sys top 5 99The highlighted are the logging process with the process ID.
- To restart the process:#diag sys kill 11 16822Here, only 2 processes are seen.
#diag sys kill 11 16820
However this process are seen multiple times with different process ID.
Note them and kill those process ID’s too.
Here, killing the process itself means restarting the processes.
Now, refresh the GUI and check for the Web filter logs.
The Test logs can be generated to check the status :# diag log testIf the issue is still present, create a ticket in the support portal for the further troubleshooting.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.