"load on module failed - wrong filter type" error message when installing policy

[BG_Hwang]

Hi,

There is an issue of policy installation failure. 

After a failed installation, reinstalling will install it.

I saw the error message "load on module failed wrong filter type" when installing the policy, but I couldn't find any related sk documentation or information.

If you have any experience, can you share?

It seems to be a memory problem, but the error message doesn't show a memory problem, so I'm a bit suspicious.

---------

MGMT : R80.40 T196 smart-1 410 memory: 32G

FW : R80.40 T196 5900 memory : 8G

-----------

Thank you.

[Tal_Paz-Fridman]

I suggest opening an SR with TAC. I found that this is an issue that has occurred in the past (although rarely) and handled by TAC.

Do you happen to have IOC Indicators configured?  

[BG_Hwang]

The IOC indicator is not configured.

Only firewall, application control, urlfiltering, IPS blades are in use.

[Shira]

Hi,

What resolved your issue? we are having similar issue at our end.

WR

[the_rock]

Hey @Shira ,

Does your failure message look exactly the same as what @BG_Hwang posted?

Andy

[Tal_Paz-Fridman]

Can you please share additional information:

• Copy and paste the full message.
• Version you are running.

[Shira]

Hi,

- Full HA running on R81.10 Take 95.

- traditional antivirus is disabled.

- gateway object showing red cross with error : antibot : failed to fetch TP policy.

- no high cpu or memory consumption seen.

- install_policy.elg has error "Threat Prevention Policy installation failed for:&ANTIMALWARE_CURRENTVERCMP"

- nothing relevent in messages file.

- we are not able to install policy at all from last 2 week.

Any suggestions.

WR

-

[the_rock]

Is the issue there if you disable traditional AV?

Andy

[Tal_Paz-Fridman]

Hi Shira,

It seems there two separate failures - one for Access Control and one for Threat Prevention

Can you please try to install each one separately and say if it makes a difference?

In case you haven't please open an SR with TAC. 

[the_rock]

Also, forgot to add this in my last response...literally, 9 times out of 10, whenever I used to see this message in the past, gateway reboot would fix it. Mind you, that was probably more "applicable" in R77 and before, probably does not work as well in R80+ versions, as database is totally different.

Andy

[the_rock]

I see in your screenshot its complaining about topology. How many interfaces do you have configured? Are you able to successfully "get interfaces WITHOUT topology"?

Andy