Apr 27 19:11:09 company-fw init: low_mem_signal_processes: send signal 16 to routing Apr 27
19:11:09 company-fw /kernel: KERNEL_MEMORY_CRITICAL: System low on free memory, notifying
init (#4).
Apr 27 19:11:09 company-fw rpd[1268]: Processing low memory signal
Apr 27 19:11:09 company-fw init: low_mem_signal_processes: send signal 16 to idp-policy
Apr 27 19:11:09 company-fw idpd[1295]: Processing low memory signal
Apr 27 19:11:10 company-fw idpd[1987]: IDP_SECURITY_INSTALL_RESULT: security package
install result Done;Install aborted due to system reaching low memory condition!)
You are troubleshooting a problem where the IDP signature database update on your Junos device
has failed. Which action will resolve this problem?

[edit security utm]
user@host# show
custom-objects {
url-pattern {
blocklist {
value [ http://badsite.com http://blocksite.com ];
}
acceptlist {
value http://juniper.net;
}}
custom-url-category {
blacklist {
value blocklist;
}
whitelist {
value acceptlist;

}}}
feature-profile {
web-filtering {
url-whitelist whitelist;
url-blacklist blacklist;
type juniper-local;
juniper-local {
profile web-filter {
custom-block-message “Site is not allowed”;
fallback-settings {
default log-and-permit;
}}}}}
utm-policy utm1 {
web-filtering {
http-profile web-filter;
}}
You set up Web filtering to allow employees to only access your internal website. You notice that
employees are still able to reach websites outside of the blacklists. Which parameter must be
changed?

user@host> show configuration security utm
custom-objects {
url-pattern {
block-juniper {
value *.spammer.com;
}}
custom-url-category {
blacklist {
value block-juniper;
}

}}
feature-profile {
anti-spam {
address-blacklist block-juniper;
sbl {
profile myprofile {
no-sbl-default-server;
spam-action block;
}}}}
utm-policy wildcard-policy {
anti-spam {
smtp-profile myprofile;
}}
You added a blacklist to your antispam policy to block any e-mails from the spammer.com domain.
However, your users are complaining that they are still receiving spam e-mails from that domain.
You run the utm test-string test and confirm that the blacklist is not working. What is causing this
problem?