Hi Bigfoot65,
Looking at the logs, do you think the date could be wrong?
For example:
200219-112931-901425: waking up and doing a full sync
Does 200219 mean 20th Feb 2019? Or 19th Feb 2020?
I checked the date on the HDA:
[steve@localhost ~]$ date
Thu 19 Mar 12:31:05 CET 2020
[steve@localhost ~]$
Kind regards,
Steve
CLOSED: Amahi Sync problem
-
- Posts: 38
- Joined: Tue Jan 19, 2010 11:41 am
- Location: Spain
-
- Posts: 38
- Joined: Tue Jan 19, 2010 11:41 am
- Location: Spain
Re: Amahi Sync problem
What I mean is, if the date /is/ wrong, could that be why it's not synchronising?
Steve
Steve
Re: Amahi Sync problem
The date is correct. It's displayed with year first.
Have you done reset permissions on the share? Go to the Shares tab in the dashboard and select the Public share and reset the permissions.
Then restart it again.
If that does not work, will need to check other areas.
Also please provide the URL for:
Have you done reset permissions on the share? Go to the Shares tab in the dashboard and select the Public share and reset the permissions.
Then restart it again.
If that does not work, will need to check other areas.
Also please provide the URL for:
Code: Select all
apaste --sysinfo
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
-
- Posts: 38
- Joined: Tue Jan 19, 2010 11:41 am
- Location: Spain
Re: Amahi Sync problem
Hi Bigfoot
I reset the permissions on the share, then restarted the amahi-sync service. That made no difference. So I restarted the HDA. Still the same, unfortunately, with the same errors logged as previously.
I ran the command as advised and got:
[steve@localhost ~]$ apaste --sysinfo
Gathering system info ............................Uploading (16.7KiB)...
Error: Server did not return a correct JSON response
[steve@localhost ~]$
I tried again with sudo in front of the command but got the same result.
Presumably that information is stored locally on the HDA somewhere? Could I upload it manually to somewhere safe where you can see it?
By the way, I don't know if this has any relevance, but I believe the date is incorrect. The year is displayed first, but the month shown is 02 not 03 as it should be.
Kind regards,
Steve
I reset the permissions on the share, then restarted the amahi-sync service. That made no difference. So I restarted the HDA. Still the same, unfortunately, with the same errors logged as previously.
I ran the command as advised and got:
[steve@localhost ~]$ apaste --sysinfo
Gathering system info ............................Uploading (16.7KiB)...
Error: Server did not return a correct JSON response
[steve@localhost ~]$
I tried again with sudo in front of the command but got the same result.
Presumably that information is stored locally on the HDA somewhere? Could I upload it manually to somewhere safe where you can see it?
By the way, I don't know if this has any relevance, but I believe the date is incorrect. The year is displayed first, but the month shown is 02 not 03 as it should be.
Kind regards,
Steve
Re: Amahi Sync problem
Have you done OS updates?
That could have something to do with your issue.
That could have something to do with your issue.
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
-
- Posts: 38
- Joined: Tue Jan 19, 2010 11:41 am
- Location: Spain
Re: Amahi Sync problem
Hi,
I don't think I have, but I did have to do a Fedora 27 Server DVD Install. The Express CD gave problems with a blank screen due to a display driver, I think. I followed the instructions in the Wiki.
Is there a way to check if I have updated the OS?
Thanks,
Steve
I don't think I have, but I did have to do a Fedora 27 Server DVD Install. The Express CD gave problems with a blank screen due to a display driver, I think. I followed the instructions in the Wiki.
Is there a way to check if I have updated the OS?
Thanks,
Steve
Re: Amahi Sync problem
Do:
We recommend using Minimal Install CD vs DVD, but should be ok.
Code: Select all
sudo dnf update
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
-
- Posts: 38
- Joined: Tue Jan 19, 2010 11:41 am
- Location: Spain
Re: Amahi Sync problem
Hi,
I ran the command. There were 766 updates!
All ran through quite quickly without errors.
I rebooted the HDA and checked the amahi-sync log. Unfortunately it's still the same. The only difference is the line which says:
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]
now has [sender=3.1.3]
I ran the apaste --sysinfo command but got the same result - an incorrect JSON response.
By the way, although I said it was a DVD install, I think I did a minimal install CD installation, but it was 3 months ago!
Is there anything else to try, or should I be planning a reinstall?
Thanks for your help,
Steve
I ran the command. There were 766 updates!
All ran through quite quickly without errors.
I rebooted the HDA and checked the amahi-sync log. Unfortunately it's still the same. The only difference is the line which says:
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]
now has [sender=3.1.3]
I ran the apaste --sysinfo command but got the same result - an incorrect JSON response.
By the way, although I said it was a DVD install, I think I did a minimal install CD installation, but it was 3 months ago!
Is there anything else to try, or should I be planning a reinstall?
Thanks for your help,
Steve
Re: Amahi Sync problem
Not sure what is causing your issues.
Please verify the path in the dashboard to the Public share is /var/hda/files/Public.
The directory structure should look like:
drwxrwxrwx 14 adminuser users 4096 Mar 17 00:31 Public
The adminuser = your first admin user.
Also verify that rsync is installed:
If those are correct, then I see two options:
Please verify the path in the dashboard to the Public share is /var/hda/files/Public.
The directory structure should look like:
drwxrwxrwx 14 adminuser users 4096 Mar 17 00:31 Public
The adminuser = your first admin user.
Also verify that rsync is installed:
Code: Select all
sudo dnf install rsync
- Submit a bug report
- Do a fresh install
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
-
- Posts: 38
- Joined: Tue Jan 19, 2010 11:41 am
- Location: Spain
Re: Amahi Sync problem
Hi Bigfoot,
Here is what is in my Dashboard, Setup, Shares, Details Tab, Public, Location: /var/hda/files/Public
Here's a copy of my Public directory structure as shown by a ls -la command: drwxrwxrwx 20 steve users 4096 Mar 18 12:27 Public
By the way, when I ran that command from the /var/hda/files folder, all the subfolders names were in blue text with a black background, except for the Public folder, which was in blue text on a green background. Is that any clue?
I ran the sudo dnf install rsync command and it told me that the dependencies were resolved and there was nothing to do, rsync was already installed.
So something else occurred to me that may be of value. My device has two network ports. I have only ever used one, because I read on the Wiki that two are not supported. Only one is connected. I ran a systemctl status command on the network.service and got this:
[steve@localhost files]$ systemctl status network.service
● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network; generated; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2020-03-23 14:20:23 CET; 3h 48min ago
Docs: man:systemd-sysv-generator(8)
Process: 765 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
Mar 23 14:20:22 localhost.localdomain systemd[1]: Starting LSB: Bring up/down networking...
Mar 23 14:20:23 localhost.localdomain network[765]: Bringing up loopback interface: [ OK ]
Mar 23 14:20:23 localhost.localdomain network[765]: Bringing up interface enp1s0: [ OK ]
Mar 23 14:20:23 localhost.localdomain network[765]: Bringing up interface enp2s0: Error: Connection activation failed: No suitable device found for this connection.
Mar 23 14:20:23 localhost.localdomain network[765]: [FAILED]
Mar 23 14:20:23 localhost.localdomain systemd[1]: network.service: Control process exited, code=exited status=1
Mar 23 14:20:23 localhost.localdomain systemd[1]: Failed to start LSB: Bring up/down networking.
Mar 23 14:20:23 localhost.localdomain systemd[1]: network.service: Unit entered failed state.
Mar 23 14:20:23 localhost.localdomain systemd[1]: network.service: Failed with result 'exit-code'.
[steve@localhost files]$
Please note the time is incorrect here. I ran that command at 18:10 CET.
Thanks for your help. If the Public folder name having a green background and the network.service error above are not problems, then I'll submit a bug report.
Steve
Here is what is in my Dashboard, Setup, Shares, Details Tab, Public, Location: /var/hda/files/Public
Here's a copy of my Public directory structure as shown by a ls -la command: drwxrwxrwx 20 steve users 4096 Mar 18 12:27 Public
By the way, when I ran that command from the /var/hda/files folder, all the subfolders names were in blue text with a black background, except for the Public folder, which was in blue text on a green background. Is that any clue?
I ran the sudo dnf install rsync command and it told me that the dependencies were resolved and there was nothing to do, rsync was already installed.
So something else occurred to me that may be of value. My device has two network ports. I have only ever used one, because I read on the Wiki that two are not supported. Only one is connected. I ran a systemctl status command on the network.service and got this:
[steve@localhost files]$ systemctl status network.service
● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network; generated; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2020-03-23 14:20:23 CET; 3h 48min ago
Docs: man:systemd-sysv-generator(8)
Process: 765 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
Mar 23 14:20:22 localhost.localdomain systemd[1]: Starting LSB: Bring up/down networking...
Mar 23 14:20:23 localhost.localdomain network[765]: Bringing up loopback interface: [ OK ]
Mar 23 14:20:23 localhost.localdomain network[765]: Bringing up interface enp1s0: [ OK ]
Mar 23 14:20:23 localhost.localdomain network[765]: Bringing up interface enp2s0: Error: Connection activation failed: No suitable device found for this connection.
Mar 23 14:20:23 localhost.localdomain network[765]: [FAILED]
Mar 23 14:20:23 localhost.localdomain systemd[1]: network.service: Control process exited, code=exited status=1
Mar 23 14:20:23 localhost.localdomain systemd[1]: Failed to start LSB: Bring up/down networking.
Mar 23 14:20:23 localhost.localdomain systemd[1]: network.service: Unit entered failed state.
Mar 23 14:20:23 localhost.localdomain systemd[1]: network.service: Failed with result 'exit-code'.
[steve@localhost files]$
Please note the time is incorrect here. I ran that command at 18:10 CET.
Thanks for your help. If the Public folder name having a green background and the network.service error above are not problems, then I'll submit a bug report.
Steve
Who is online
Users browsing this forum: No registered users and 1 guest