Cannot log into NAS with Qsync

[Ankemiel]

I try to follow steps 1 to 7.
It turns out that in the directory "/etc/init.d/ the file "qbox.sh" is missing.
Well, I can find the file "mariadb.sh".

How can I fix this?

Emiel Koestal

[Ankemiel]

I try to follow steps 1 to 7.
It turns out that in the directory "/etc/init.d/ the file "qbox.sh" is missing.
Well, I can find the file "mariadb.sh".

How can I fix this?

Emiel Koestal

[hofumbau]

Hi Michel

you are the men - it works for me on TS-219 PII. Now it´s syncing well

Thx a lot
Matthias

I got the following reply, posting it tested.
On my box, I got SSH certificate errors (ignore) and had to find out what is the correct name for $def_vol. That refers to a drive name, I had to ls -a to find it out.

Michel

___
Could you please try to clean the database of qsync :


Please follow this procedure :

Connect the NAS by SSH port 22, login as admin password admin

download here http://the.earth.li/~sgtatham/putty/lat ... /putty.exe

(you can right click you mouse to paste commands in putty)



NAS DB Fixed Step.
1. backup qsync db
/etc/init.d/qbox.sh backup_db /share/Public/qbox.db

2. stop mysql
/etc/init.d/mariadb.sh stop

3. remove mysql data
rm -r /share/$def_vol/.system/data

4. start mysql
/etc/init.d/mariadb.sh start

5. start qsync service
/etc/init.d/qbox.sh restart

6. restore qsync db
/etc/init.d/qbox.sh restore_db /share/Public/qbox.db (doesnt work yet so use next line till then )

/etc/init.d/qbox.sh clean_all_db

7. restart qsync service
/etc/init.d/qbox.sh restart

[treefiddy]

Thank you so much michelv. This fixed it for me. This should be a sticky! THANKS!

I got the following reply, posting it tested.
On my box, I got SSH certificate errors (ignore) and had to find out what is the correct name for $def_vol. That refers to a drive name, I had to ls -a to find it out.

Michel

___
Could you please try to clean the database of qsync :


Please follow this procedure :

Connect the NAS by SSH port 22, login as admin password admin

download here http://the.earth.li/~sgtatham/putty/lat ... /putty.exe

(you can right click you mouse to paste commands in putty)



NAS DB Fixed Step.
1. backup qsync db
/etc/init.d/qbox.sh backup_db /share/Public/qbox.db

2. stop mysql
/etc/init.d/mariadb.sh stop

3. remove mysql data
rm -r /share/$def_vol/.system/data

4. start mysql
/etc/init.d/mariadb.sh start

5. start qsync service
/etc/init.d/qbox.sh restart

6. restore qsync db
/etc/init.d/qbox.sh restore_db /share/Public/qbox.db (doesnt work yet so use next line till then )

/etc/init.d/qbox.sh clean_all_db

7. restart qsync service
/etc/init.d/qbox.sh restart

[keeztha]

Hi,

i upgraded the firmware '4.2.1 build 20160601' -> '4.2.2 build 20161021' (TS-220).
Qsync client works well on the newest firmware version.

[whosnext]

Not working with Qsync on 4.2.1 and 4.2.2 and windows 10.

also tried cleanup database also without any succes

[ldebernardini]

I had the same problem and tried to follow the db reset procedure. Anytime I was trying to execute the command "/etc/init.d/qbox.sh backup_db /share/Public/qbox.db" I got the error
"Found option without preceding group in config file: /etc/my.cnf at line: 2
Fatal error in defaults handling. Program aborted"
After some investigation I was able to solve the problem with the following steps:
1. connect to the NAS using Cyberduck (I'm on a MAC) through SFTP;
2. navigate to folder /etc
3. edit file "my.cnf"
4. add "[mysqld]" as the first line of the file
5. Disable "Qsync Central Station" on NAS
6. Enable "Qsync Central Station" on NAS

After these steps I was able to login QSYNC and it worked perfectly.

Hope this helps.
Luigi

[michelv]

Well, after some more issues, and getting lost in the slow responses and very slow updates in QSync, I decided to ditch it for something more modern.
Now I have Resilio Sync running (not open source) and the open source and slightly less convenient Syncthing. Both have quick apps for Android and similar available.
Both work enormously fast and reliable, and work outside your NAS network as well. Syncthing also can be adjusted to keep older versions.

So if you don't need a full "previous versions" system: upgrade to modern technology.

[reddxx]

I had the same problem and tried to follow the db reset procedure. Anytime I was trying to execute the command "/etc/init.d/qbox.sh backup_db /share/Public/qbox.db" I got the error
"Found option without preceding group in config file: /etc/my.cnf at line: 2
Fatal error in defaults handling. Program aborted"
After some investigation I was able to solve the problem with the following steps:
1. connect to the NAS using Cyberduck (I'm on a MAC) through SFTP;
2. navigate to folder /etc
3. edit file "my.cnf"
4. add "[mysqld]" as the first line of the file
5. Disable "Qsync Central Station" on NAS
6. Enable "Qsync Central Station" on NAS

After these steps I was able to login QSYNC and it worked perfectly.

Hope this helps.
Luigi

it worked for me like a charm!
thaks you all!!!

[Snaxmuppet]

Had the same issue, ran through these steps and it fixed it!

I got the following reply, posting it tested.
On my box, I got SSH certificate errors (ignore) and had to find out what is the correct name for $def_vol. That refers to a drive name, I had to ls -a to find it out.

Michel

___
Could you please try to clean the database of qsync :


Please follow this procedure :

Connect the NAS by SSH port 22, login as admin password admin

download here http://the.earth.li/~sgtatham/putty/lat ... /putty.exe

(you can right click you mouse to paste commands in putty)



NAS DB Fixed Step.
1. backup qsync db
/etc/init.d/qbox.sh backup_db /share/Public/qbox.db

2. stop mysql
/etc/init.d/mariadb.sh stop

3. remove mysql data
rm -r /share/$def_vol/.system/data

4. start mysql
/etc/init.d/mariadb.sh start

5. start qsync service
/etc/init.d/qbox.sh restart

6. restore qsync db
/etc/init.d/qbox.sh restore_db /share/Public/qbox.db (doesnt work yet so use next line till then )

/etc/init.d/qbox.sh clean_all_db

7. restart qsync service
/etc/init.d/qbox.sh restart

[Anton1984]

MySQL reset commands

[~] # /usr/local/mariadb/bin/mysqldump -S /tmp/mysql_qbox.sock --user=root --password=qnapqnap qbox > /share/Public/qsync_backup.db
[~] # /etc/init.d/qbox.sh stop
[~] # /etc/init.d/mariadb.sh stop
[~] # mv /share/CACHEDEV1_DATA/.qbox/mysql/data /share/CACHEDEV1_DATA/.qbox/mysql/data_old
[~] # /etc/init.d/qbox.sh start
[~] # /etc/init.d/mariadb.sh start
[~] # /usr/local/mariadb/bin/mysql -S /tmp/mysql_qbox.sock --user=root --password=qnapqnap qbox < /share/Public/qsync_backup.db

Best regards.

[raysvq]

I followed the Putty and the Duck instructions above (once I worked out how to follow them) - but still no go. I can't logon onto Qsync.
I had to rebuild my NAS after 2 more disks failed (thankfully I had all my data backed up separately) and I decided to start using some of the features - Qsync being one of them. But Qsync doesn't want to play the game, so I guess it is either try to get on to tech support or just forget about it.

I am using a 4 bay TS-459 Pro II with 4TB WD reds in Raid 6 (although after 6 drive failures in 12 months I am switching to Seagate drives)
My QTS is v4.2.6 (2017/07/29)

[raysvq]

I followed the Putty and the Duck instructions above (once I worked out how to follow them) - but still no go. I can't logon onto Qsync.
I had to rebuild my NAS after 2 more disks failed (thankfully I had all my data backed up separately) and I decided to start using some of the features - Qsync being one of them. But Qsync doesn't want to play the game, so I guess it is either try to get on to tech support or just forget about it.

I am using a 4 bay TS-459 Pro II with 4TB WD reds in Raid 6 (although after 6 drive failures in 12 months I am switching to Seagate drives)
My QTS is v4.2.6 (2017/07/29)

Just a quick update - I am waiting on support to do a remote access, I will let you know what the result was.

[raysvq]

I followed the Putty and the Duck instructions above (once I worked out how to follow them) - but still no go. I can't logon onto Qsync.
I had to rebuild my NAS after 2 more disks failed (thankfully I had all my data backed up separately) and I decided to start using some of the features - Qsync being one of them. But Qsync doesn't want to play the game, so I guess it is either try to get on to tech support or just forget about it.

I am using a 4 bay TS-459 Pro II with 4TB WD reds in Raid 6 (although after 6 drive failures in 12 months I am switching to Seagate drives)
My QTS is v4.2.6 (2017/07/29)

Just a quick update - I am waiting on support to do a remote access, I will let you know what the result was.

Well no success so far.
So I think I shall wait for my new TS-453A and 4 x new hard drives and do a clean build and see what happens then.

[raysvq]

I followed the Putty and the Duck instructions above (once I worked out how to follow them) - but still no go. I can't logon onto Qsync.
I had to rebuild my NAS after 2 more disks failed (thankfully I had all my data backed up separately) and I decided to start using some of the features - Qsync being one of them. But Qsync doesn't want to play the game, so I guess it is either try to get on to tech support or just forget about it.

I am using a 4 bay TS-459 Pro II with 4TB WD reds in Raid 6 (although after 6 drive failures in 12 months I am switching to Seagate drives)
My QTS is v4.2.6 (2017/07/29)

Just a quick update - I am waiting on support to do a remote access, I will let you know what the result was.

Well no success so far.
So I think I shall wait for my new TS-453A and 4 x new hard drives and do a clean build and see what happens then.

Just another update - I received my new TS-453A and new seagate harddrives (bloody noisey harddrives) and the Qsync works perfectly