Knowledge Base
v5.15.0
Search this version
Knowledge Base
Knowledge Base
Configuration and Settings
Errors and Troubleshooting
Features and Functionality
Feedback and Support
Licensing, Setup and Deployment
Updates, Patches and Bug Fixes
Version Upgrades
Title
Message
Create new category
What is the title of your new category?
Edit page index title
What is the title of the page index?
Edit category
What is the new title of your category?
Edit link
What is the new title and URL of your link?
What do I do when licensed engines are not detected despite active licenses?
Copy Markdown
Open in ChatGPT
Open in Claude
This article applies to all MetaDefender Core V4 and V5 releases deployed on Windows and Linux systems
If you're seeing the error message "No active licensed engines found" in MetaDefender Core, follow the steps below to identify and resolve the issue:
1. Check License Configuration
- Confirm that the activated license key includes the necessary scanning engines.
- MetaDefender Core downloads and enables engines based on your license key.
- If the required engines are not included, you may need a different license key.
- Contact the OPSWAT support team for help with licensing validation or replacement.
2. Verify Engine Activation in the Console
- Open the MetaDefender Core console.
- Navigate to: Inventory > Modules > Metascan.
- Look for any activation or installation errors related to the engines.
- If you see issues, check the logs in the MetaDefender Core pod for more detail.
3. Ensure Sufficient System Resources
Verify that your system meets the minimum resource requirements:
- CPU: Sufficient cores for all licensed engines.
- Memory: At least 3 GB available.
- Disk Space: At least 5 GB available.
Inadequate resources can prevent engines from initializing properly.
4. Check Internet Connection (if using online updates)
- A stable internet connection is required to download engine packages.
- Network interruptions or timeouts can result in incomplete or corrupted downloads.
5. Re-enable or Reinstall Engines
- Try disabling and then re-enabling the affected engines.
- If the issue persists, try the following steps:
- Remove the engine and its associated database.
- Deactivate the license, then reactivate it.
- Navigate to the Inventory tab > Modules, and click the Update All button.
6. IKARUS Engine Specific Configuration
- If using the IKARUS engine, it requires shared memory configuration to function properly.
- For Docker, add the following flag:
Docker
1
1
1
--shm-size=1gbFor Kubernetes (K8s) deployments, include this in your YAML:
YAML
9
9
1
spec:2
volumes:3
- name: dshm4
emptyDir:5
medium: Memory6
containers:7
- volumeMounts:8
- mountPath: /dev/shm9
name: dshmIf Further Assistance is required, please proceed to log a support case or chatting with our support engineer.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Last updated on
Was this page helpful?
Discard Changes
Do you want to discard your current changes and overwrite with the template?
Archive Synced Block
Message
Create new Template
What is this template's title?
Delete Template
Message
On This Page
What do I do when licensed engines are not detected despite active licenses?1. Check License Configuration2. Verify Engine Activation in the Console3. Ensure Sufficient System Resources4. Check Internet Connection (if using online updates)5. Re-enable or Reinstall Engines6. IKARUS Engine Specific Configuration
