Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
Based on the logs you’ve shared, the message “Current versions in storage and reported by OSTree do not match” is not an error but rather an informational statement(1). This message appears when Aktualizr’s SQL storage contains different version information than what OSTree reports, which can happen in several scenarios(1).
Understanding the Log Message
The message occurs because Aktualizr stores version information only if it came from an update(1). If you’ve never performed an OS/OSTree update through Aktualizr, the storage would be empty while OSTree reports the current version(1). This mismatch is expected and not inherently problematic(1).
Troubleshooting Your Stuck Update
Since your logs show “No updates available” but you mention the update is stuck at “Update in progress,” there may be a disconnect between the Torizon Cloud interface and the actual device state. Here are steps to investigate:
1. Check OSTree Status
To understand your current OSTree deployment status, you can examine the OSTree state directly. OSTree manages multiple bootable filesystem versions and handles atomic updates(2).
2. Review Complete Aktualizr Logs
Your current logs only show the polling activity. To get a complete picture, check the full Aktualizr logs around the time the update was initiated:
sudo journalctl -u aktualizr* --since "1 hour ago"
3. Verify Update Configuration
Aktualizr is configured via .toml files in /usr/lib/sota/conf.d/ and /etc/sota/conf.d/(3). The default polling frequency is every 5 minutes(3), which matches your log timestamps.
4. Check for Pending Reboots
Torizon OS is configured to automatically reboot after successful OS updates(3). If automatic reboot is disabled, the update process might appear stuck. Check if there’s a pending reboot:
systemctl status ostree-pending-reboot.path
Next Steps
-
Restart Aktualizr: Try restarting the Aktualizr service to refresh its state:
sudo systemctl restart aktualizr-torizon -
Check Device Status: Verify your device’s connection status in the Torizon Cloud interface to ensure it’s properly communicating with the server.
-
Review Full Logs: Examine the complete Aktualizr logs from when the update was initiated to identify any error messages or status changes that might not appear in the current polling logs.
The “Current versions in storage and reported by OSTree do not match” message itself is not the cause of your stuck update - it’s a normal informational message(1).
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.