You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have encountered a persistent disk I/O error when attempting to start the hbbs service. Despite extensive troubleshooting, the issue remains unresolved. The service fails with the following error message:
Error: An error occurred while creating a new object: error returned from database: disk I/O error
Steps Taken to Troubleshoot:
Permissions and Ownership:
Verified and ensured correct permissions and ownership for the database file:
Despite these efforts, the hbbs service continues to fail with the same disk I/O error. Any insights, suggestions, or guidance from the community would be greatly appreciated.
Thank you for your assistance!
How to Reproduce
How to Reproduce
Setup the Environment:
Install Ubuntu 24.04.1 LTS (noble).
Ensure you have the RustDesk version 1.1.12 installed.
By following these steps, you should be able to reproduce the disk I/O error observed when starting the hbbs service.
Expected Behavior
Expected Behavior
The hbbs service should start successfully without encountering any errors. Specifically, it should be able to create new objects in the SQLite database located at /mnt/rustdesk-test/db_v2.sqlite3 without generating a disk I/O error. The service should run smoothly, allowing RustDesk to function correctly for managing connections and providing the necessary ID services.
Operating system(s) on local (controlling) side and remote (controlled) side
Ubuntu 24.04.1 LTS
RustDesk Version(s) on local (controlling) side and remote (controlled) side
1.1.12
Screenshots
N/A as operating in a console environment
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Bug Description
System Information:
hbbs
(RustDesk ID Server)/mnt/rustdesk-test/db_v2.sqlite3
Problem Description:
I have encountered a persistent
disk I/O error
when attempting to start thehbbs
service. Despite extensive troubleshooting, the issue remains unresolved. The service fails with the following error message:Steps Taken to Troubleshoot:
Permissions and Ownership:
Write Access:
www-data
user:sudo -u www-data sqlite3 /mnt/rustdesk-test/db_v2.sqlite3 "CREATE TABLE test5 (id INTEGER PRIMARY KEY);"
Filesystem Health:
AppArmor:
Service Configuration:
hbbs
service to use thewww-data
user and pointed to the new database location:Dependencies and Environment:
hbbs
binary is not corrupted:Logs and Errors:
sudo dmesg | grep -i error sudo journalctl -xe
Disk I/O Test:
Despite these efforts, the
hbbs
service continues to fail with the samedisk I/O error
. Any insights, suggestions, or guidance from the community would be greatly appreciated.Thank you for your assistance!
How to Reproduce
How to Reproduce
Setup the Environment:
Create the Database Directory:
Create the SQLite Database File:
sudo sqlite3 /mnt/rustdesk-test/db_v2.sqlite3 "CREATE TABLE init (id INTEGER PRIMARY KEY);" sudo chown www-data:www-data /mnt/rustdesk-test/db_v2.sqlite3 sudo chmod 777 /mnt/rustdesk-test/db_v2.sqlite3
Configure the
hbbs
Service:Create or edit the
hbbs
service file to use the new database location:Ensure the
ExecStart
line is:Restart the
hbbs
Service:hbbs
service:Monitor for Errors:
By following these steps, you should be able to reproduce the
disk I/O error
observed when starting thehbbs
service.Expected Behavior
Expected Behavior
The hbbs service should start successfully without encountering any errors. Specifically, it should be able to create new objects in the SQLite database located at /mnt/rustdesk-test/db_v2.sqlite3 without generating a disk I/O error. The service should run smoothly, allowing RustDesk to function correctly for managing connections and providing the necessary ID services.
Operating system(s) on local (controlling) side and remote (controlled) side
Ubuntu 24.04.1 LTS
RustDesk Version(s) on local (controlling) side and remote (controlled) side
1.1.12
Screenshots
N/A as operating in a console environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: