Policy Manager Alerts tab shows an alert with the Severity\u00a0Security\u00a0<\/b>and the description "Databases are old" for a host. How to troubleshoot why Malware definitions or engines are shown as outdated?<\/p>\nResolution:<\/h3>\n
WithSecure Policy Manager receives the updates through our guts2\u00a0<\/a>delivery and stores them in C:\\ProgramData\\WithSecure\\NS\\Policy Manager\\Policy Manager Server\\data\\guts2 folder.<\/p>\n WithSecure Policy Manager Server checks for new update versions every 10 minutes, other checks (headers, diffs) are requested by clients.<\/p>\n What do I do if clients are alerting about Virus definitions being x\u00a0days old?<\/b><\/p>\n –\u00a0\u00a0 \u00a0Check for latest policy under status Note: <\/b>You might be using http proxy and therefore Policy Manager might not be reachable in case traffic to Policy Manager is routed through the HTTP proxy.<\/p>\n \u2022\u00a0\u00a0 \u00a0You can define your http proxy by opening settings in your WithSecure Policy Manager console, expand Centralized management and scroll down to Internet connections. http:\/\/[user[:password]@]host:port, for example: or<\/p>\n domain\\user is considered domain%5cuser. 2.\u00a0\u00a0 \u00a0From your local Policy Manager host, you can check if there are any problems with updates:<\/p>\n And in overall, it is recommended to check point 2 first, client log might already explain all reasons even without Policy Manager connectivity checks. Even probably client to Policy Manager check is needed only if AUA log says client is pinging fake address instead of the Policy Manager address in policies.<\/p><\/div>\n When should I apply FSAUA-reset Tool?<\/b><\/div>\n In case of Policy Manager Server for Linux,\u00a0 check if there is sufficient storage space. The proxy server may have enough storage however, but if you have multiple Logical Volumes and the Logical Volumes\u00a0 for \/var\/opt\/ wasn\u2019t big enough, Policy Manager will be showing the error \u201cDatabases are old\u201d. To resolve this, extended the Logical Volume size.<\/p>\n \u00a0<\/p><\/div>\n","protected":false},"excerpt":{"rendered":" Virus definitions are shows as outdated<\/p>\n","protected":false},"template":"","support_article_product":[106],"class_list":["post-4134","support_article","type-support_article","status-publish","hentry"],"acf":{"source_foreign_id":"000013450","source_version":3,"source_system":"salesforce","source_date_updated":"2026-06-08 15:01:00","import_hash":"b1a99376c5a36105381f38d2d766a93bcb705b41","vanilla_article_id":29348,"vanilla_url":"https:\/\/community.withsecure.com\/en\/kb\/articles\/29348-policy-manager-alerts-tab-shows-databases-are-old-for-a-host","vanilla_kb_id":30,"vanilla_category_id":103,"machine_translated":false,"reactions_helpful_yes":0,"reactions_helpful_no":0},"_links":{"self":[{"href":"https:\/\/support.withsecure.com\/fr\/wp-json\/wp\/v2\/support_article\/4134","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/support.withsecure.com\/fr\/wp-json\/wp\/v2\/support_article"}],"about":[{"href":"https:\/\/support.withsecure.com\/fr\/wp-json\/wp\/v2\/types\/support_article"}],"wp:attachment":[{"href":"https:\/\/support.withsecure.com\/fr\/wp-json\/wp\/v2\/media?parent=4134"}],"wp:term":[{"taxonomy":"support_article_product","embeddable":true,"href":"https:\/\/support.withsecure.com\/fr\/wp-json\/wp\/v2\/support_article_product?post=4134"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
–\u00a0\u00a0 \u00a0Check Automatic updates under Status
–\u00a0\u00a0 \u00a0Verify your WithSecure Policy Manager HTTP and HTTPS address are reachable from client, by opening example http:\/\/10.0.0.50:80 and https:\/\/10.0.0.50:443 in Browser. Successful connection will show you\u00a0 "WithSecure Policy Manager Server is installed and is working fine", if not, make sure your https and https Ports defined in your WithSecure Policy Manager are opened for the clients.<\/p>\n
\u2022\u00a0\u00a0 \u00a0Custom HTTP proxy address – this is used when "Use HTTP proxy" is set to "Custom". It can be defined as follows:<\/p>\n
http:\/\/myproxy.com
http:\/\/myproxy.com:8080
http:\/\/<http-encoded-user-name>:<http-encoded-password>@host:port<\/p>\n
Our support for authenticated proxies is limited to SIMPLE and NTLM authentication and should be the same as
FsHttpRequest's.<\/p>\n\n
\n
\n
\n
\n