Difference between revisions of "Cloud Sync No longer works, owner changed"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
The settings are stored in an SQLite database and can be modified there. I took the following steps. | The settings are stored in an SQLite database and can be modified there. I took the following steps. | ||
< | <ul> | ||
Connect through ssh to your diskstation or open a terminal console window | <li>Stop the cloud sync service from the package manager</li> | ||
go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db` | <li>Connect through ssh to your diskstation or open a terminal console window</li> | ||
before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. You can do this by running `id -u new_user_name` and `id -g new_user_name`. lets assume these return 1033 and 100 | <li>go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`</li> | ||
now we can run an sqlite shalle for the config database by doing `sqlite3 config.sqlite` | <li>before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. </li> | ||
To see all the existing connections you can do a `select * from connection_table;` | <li>You can do this by running `id -u new_user_name` and `id -g new_user_name`. lets assume these return 1033 and 100</li> | ||
Note down the ids of the configurations that need a change. This is the first number in each row. | <li>now we can run an sqlite shalle for the config database by doing `sqlite3 config.sqlite`</li> | ||
The actual update is then done similar to this command using the right user id and local user name ` update connection_table set uid=1033, gid=100, local_user_name="new_user_name" where id=3;` the last id will indicate in which row you want to update this | <li>To see all the existing connections you can do a `select * from connection_table;`</li> | ||
<li>Note down the ids of the configurations that need a change. This is the first number in each row.</li> | |||
start your cloudsynch package again | <li>The actual update is then done similar to this command using the right user id and local user name</li> | ||
<li> ` update connection_table set uid=1033, gid=100, local_user_name="new_user_name" where id=3;` the last id will indicate in which row you want to update this</li> | |||
<li>.quit to exit</li> | |||
<li>start your cloudsynch package again</li> | |||
</ul> | |||
Revision as of 14:57, 25 April 2024
The settings are stored in an SQLite database and can be modified there. I took the following steps.
- Stop the cloud sync service from the package manager
- Connect through ssh to your diskstation or open a terminal console window
- go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`
- before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be.
- You can do this by running `id -u new_user_name` and `id -g new_user_name`. lets assume these return 1033 and 100
- now we can run an sqlite shalle for the config database by doing `sqlite3 config.sqlite`
- To see all the existing connections you can do a `select * from connection_table;`
- Note down the ids of the configurations that need a change. This is the first number in each row.
- The actual update is then done similar to this command using the right user id and local user name
- ` update connection_table set uid=1033, gid=100, local_user_name="new_user_name" where id=3;` the last id will indicate in which row you want to update this
- .quit to exit
- start your cloudsynch package again