Difference between revisions of "Cloud Sync No longer works, owner changed"

From rbachwiki
Jump to navigation Jump to search
Line 6: Line 6:
<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>
<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>
<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>
<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>
<li>You can do this by running <code class="yellowbackground">id -u new_user_name</code> and <code>id -g new_user_name</code>. lets assume these return 1033 and 100</li>
<li>You can do this by running <code class="yellowbackground">id -u new_user_name</code> and <code class="yellowbackground">id -g new_user_name</code>. lets assume these return 1033 and 100</li>
<li>now we can run an sqlite shalle for the config database by doing <code>sqlite3 config.sqlite</code></li>
<li>now we can run an sqlite shalle for the config database by doing <code class="yellowbackground">sqlite3 config.sqlite</code></li>
<li>To see all the existing connections you can do a `select * from connection_table;`</li>
<li>To see all the existing connections you can do a <code class="yellowbackground">select * from connection_table;</code></li>
<li>Note down the ids of the configurations that need a change. This is the first number in each row.</li>
<li>Note down the ids of the configurations that need a change. This is the first number in each row.</li>
<li>The actual update is then done similar to this command using the right user id and local user name</li>
<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> <code class="yellowbackground"> update connection_table set uid=1030, gid=100, local_user_name="new_username" where id=1;</code> the last id will indicate in which row you want to update this</li>
<li>.quit to exit</li>
<li>.quit to exit</li>
<li>start your cloudsynch package again</li>
<li>start your cloudsynch package again</li>
</ul>
</ul>

Revision as of 15:06, 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=1030, gid=100, local_user_name="new_username" where id=1; the last id will indicate in which row you want to update this
  • .quit to exit
  • start your cloudsynch package again
Retrieved from "https://www.r512.com/index.php?title=Cloud_Sync_No_longer_works,_owner_changed&oldid=2754"