EDIT: My fault! I modified the model and code of my Rockstor instance which probably caused this error.
Brief description of the problem
After clean reinstall, data disk/pool import and configuration restore, it says “There are no Rock-ons installed currently”, even though the docker instances are running and working!
Detailed step by step instructions to reproduce the problem
I upgraded from 4.6.0.0 to 5.1.0.0 following the official rockstor docs. I used the clean, reinstall option.
After installation I updated the distro packages, rebooted, imported disks, then restored configuration. After that I didn’t reboot anymore.
My issue is similar to Rock-ons missing in Web-GUI after reinstallation, but I used the restore configuration feature.
The upgrade/reinstall process overall was otherwise quick and painless. Taking about 5 minutes!
So… is there a way to make them visible in the Rock-Ons page again?
Thanks!
EDIT: I’ve tried the docker prune command and restarted rockstor services, but no luck!
Then I’ve noticed that after loading the Rock-Ons page, this line appears in the Rockstor logs:
[27/Sep/2025 23:07:16] ERROR [smart_manager.data_collector:1017] Failed to update disk state.. exception: Exception while setting access_token for url(http://127.0.0.1:8000): HTTPConnectionPool(host='127.0.0.1', port=8000): Read timed out. (read timeout=2). content: None
Gunicorn log:
127.0.0.1 - - [27/Sep/2025:23:07:16 +0200] "GET /api/rockons?page=1&format=json&page_size=32000&count= HTTP/1.0" 200 80743 "https://192.168.0.103:1443/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:143.0) Gecko/20100101 Firefox/143.0" **2341ms**
127.0.0.1 - - [27/Sep/2025:23:07:16 +0200] "GET /api/rockons?page=1&format=json&page_size=32000&count= HTTP/1.0" 200 80743 "https://192.168.0.103:1443/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:143.0) Gecko/20100101 Firefox/143.0" **2335ms**
It looks like the request needed more than 2 seconds to reply, which triggered the 2-second timeout set in rockstor-core/src/rockstor/cli/api_wrapper.py at 5fbf1dd102ac10a95db44baecde5be95fcf52ae6 · rockstor/rockstor-core · GitHub
When increasing the timeout, the error doesn’t appear anymore in the logs, but the main problem remains, unfortunately.