Module Update (WSUS) is unavailable after enabling AES protection for update catalogs
Applies to: Update Module (WSUS)
Version: Medulla 5.5 and later
Environment: On-Premise
Category: Update / WSUS
Background
After enabling AES protection on Medulla update repositories, the Update (WSUS) module may become inaccessible, or no updates may be available in the interface.
This issue is typically caused by a corrupted or incomplete SQL file that was downloaded before encryption was enabled.
Symptoms
The Update module does not display any updates or appears empty.
In the following log file:
/tmp/Medulla-generate-winupdate-packages.log
You may find errors similar to the following:
[2026-05-31 01:30:02 AM] Checksum changed. Downloading https://updates.medulla-tech.io/updates_protected/20260426-184934-dumptable_update_data.sql
[2026-05-31 01:30:02 AM] Error downloading https://updates.medulla-tech.io/updates_protected/20260426-184934-dumptable_update_data.sql
Diagnosis
1. Check the downloaded file
Navigate to the following directory:
/var/lib/pulse2/downloads
Look for the following files:
*.sql
If an SQL file is present, open it with the following command:
head -50 filename.sql
or:
less filename.sql
2. Check the file's contents
If the file contains an HTML error message, an authentication page, or any other content other than SQL statements, then the download failed.
Important:
The file must begin with valid SQL statements. If you see HTML, an error message, or inconsistent content, the file must be deleted.
Resolution
1. Delete the corrupted SQL file
rm -f /var/lib/pulse2/downloads/*.sql
2. Regenerate the Update module tables
Manually run the following command:
/usr/sbin/medulla-generate-winupdate-packages 2>&1 | tee -a /tmp/medulla-generate-winupdate-packages.log
This command will:
- Download the latest WSUS metadata
- Rebuild the update tables
- Reindex the catalogs required by the Update module
Alternative
If you do not wish to run the command manually, the process is launched automatically every night at:
1:30 a.m.
In that case, simply delete the corrupted SQL file and wait for the next scheduled run.
Verification
Once the script has finished, verify that the log file no longer contains any errors:
tail -100 /tmp/medulla-generate-winupdate-packages.log
Then log back into the Medulla interface and open:
Updates → WSUS Catalog
Microsoft updates should now be visible and available again.
Common Errors
The SQL file reappears with an error
- Check the Medulla server’s Internet connection.
- Check HTTPS traffic to updates.medulla-tech.io.
- Verify that no proxy or security device is interfering with the download.
The script completes without errors, but no updates appear
- Wait a few minutes for indexing to complete.
- Check the Update module logs.
- Run the generation command a second time.
Default values
| Element | Value |
|---|---|
| Generation script | /usr/sbin/Medulla-generate-winupdate-packages |
| Download directory | /var/lib/pulse2/downloads |
| Log file | /tmp/Medulla-generate-winupdate-packages.log |
| Automatic execution | 1:30 AM |
| Affected versions | Medulla 5.5 and later |
| Affected module | Update / WSUS |