Hello,
Great app, which I really appreciate.
My issue: I'm running GeneralSync for PC v 1.0.2.1 in Linux Mint 19.3 (64 bit Cinnamon). I'm fairly sure that in the past GeneralSync has updated automatically at boot when a newer version is available (it started at v 0.2.2.1b). Yesterday it didn't offer to update to v 1.0.3.0 at boot, so I downloaded that version and installed it manually, and it's running ok.
The only possible oddity with the PC is that it auto-boots before I'm awake, logs-in to my user account, and starts GeneralSync. If it notices a GeneralSync update is available, should it install it automatically, or does it require a human to ok the update?
Martin Whitehead
If it notices a GeneralSync update is available, should it install it automatically, or does it require a human to ok the update?
The PC version of GeneralSync checks for updates whenever it is started; as GeneralSync is a background service tied to your user session that should happen whenever you log in. Currently, it will always ask the user before upgrading.
That being said, there is no time limit or anything on the update dialog; if GeneralSync starts before you get to the PC you should thus still see the question.
I don't know your situation in detail, but one potential issue could be your PC's real time clock: maybe your PC starts with a wrong date/time, and fixes that using a time server a few seconds/minutes after GeneralSync searched for updates? Multiple parts of the update process rely on the update server and your PC agreeing on the current time. If the times differ by a large margin, your PC will not be able to verify the server's cryptographic signatures – GeneralSync will then consider the update tampered and do not offer to install it.
But I don't know for sure what's going on. Maybe enable the creation of log files in the configuration ("Troubleshooting" section) and do a reboot, then look at the first few messages (logs are in ~/.local/share/GeneralSync)? Is there anything update-related?
Thanks, DS.
Enabled logging, rebooted, and here's the whole log up to 'no updates found':
Package: generalsync-pc-java
Release: 1.0.3.0
Versions: e143e186eb, JVM: OpenJDK 64-Bit Server VM 25.282-b08 by Private Build, OS: Linux 5.4.0-66-generic
Logging started 1615886706277.
1615886706278: AutosyncService (0)
Create and start a new thread
1615886706278: GUIService @655b011f (0)
GUIService starting GUI
1615886706281: ServerService (TCP) (0)
Create and start a new thread
1615886706285: ServerService (UDP) (0)
Create and start a new thread
1615886706285: ServerService (TCP) (0)
Starting up
1615886706285: AutosyncService (0)
Started AutosyncService.
1615886706296: AutosyncService (0)
Starting periodic sync of c2a66cde-3e66-42b5-893e-76033a7d47a5
1615886706297: ServerService (UDP) (0)
Starting up
1615886706315: (none) (0)
Checking for updates
1615886706325: AutosyncService (0)
Starting periodic sync of 74376164-ca19-4ecc-8106-134fa4ce92fb
1615886706326: AutosyncService (0)
Starting periodic sync of 01eaf101-e81a-4a33-8162-7333280fa232
1615886706327: AutosyncService (0)
Starting periodic sync of 7fe13bf7-ee5a-44ba-8223-a96289812b50
1615886706328: AutosyncService (0)
Starting periodic sync of 799b51c2-24c8-49c9-b8dc-dfc7a1bc1421
1615886706328: AutosyncService (0)
Starting periodic sync of 12a86db6-38a5-4b60-9dca-20bb8775bc64
1615886706334: (none) (1)
SyncConnectionEvent for c2a66cde-3e66-42b5-893e-76033a7d47a5: start
1615886706334: (none) (1)
NetworkProtectionEvent: busy
1615886706335: (none) (1)
SyncConnectionEvent for 01eaf101-e81a-4a33-8162-7333280fa232: start
1615886706335: (none) (1)
SyncConnectionEvent for 7fe13bf7-ee5a-44ba-8223-a96289812b50: start
1615886706337: (none) (1)
SyncConnectionEvent for 799b51c2-24c8-49c9-b8dc-dfc7a1bc1421: start
1615886706341: (none) (1)
SyncConnectionEvent for 12a86db6-38a5-4b60-9dca-20bb8775bc64: start
1615886706584: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706586: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706587: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706587: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706588: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706588: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706589: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706590: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706590: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706590: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706718: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706719: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706719: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706720: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706722: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706723: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706723: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706724: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706968: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706968: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706969: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706970: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706970: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706970: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706975: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886706975: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886707481: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886707481: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886707482: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886707483: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886707483: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886707483: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886707488: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886707488: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886708483: (none) (0)
Start sync for 12a86db6-38a5-4b60-9dca-20bb8775bc64
1615886708506: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886708507: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886708508: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886708508: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886708508: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886708508: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886708513: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886708513: ServerService (UDP) (0)
Started handling a client connection: Whois
1615886708620: (none) (0)
No update found
1615886709597: (none) (1)
DeviceEvent (creation)Does this suggest the update process is now working ok? But no newer version is available to download, hence "no update found"?
Should I leave logging enabled
Martin
Last edited by ds (2021-03-16 16:42:14)
Thanks for the logs! I re-formatted your post a tiny bit in order to separate them from your text.
Does this suggest the update process is now working ok? But no newer version is available to download, hence "no update found"?
Yes, the parts of the update process that did run seem to work as intended. There are some additional parts that would only trigger if an update is found, of course, but for now things seem fine.
It is possible that this issue is not triggered on reboots (for example the time issue I suggested could depend on the PC being started for the first time after being disconnected from the power grid), so it would make sense to also have a look at logs at some later time, though.
Should I leave logging enabled
You can either do that, or re-enable it in case the next update is not found (before installing the update manually). The advantage of the latter solution is that you don't have to remember to disable logs if the update should work as intended. 
I re-formatted your post a tiny bit in order to separate them from your text.
Thanks! I couldn't figure out the how to do that.
You can either do that, or re-enable it in case the next update is not found (before installing the update manually). The advantage of the latter solution is that you don't have to remember to disable logs if the update should work as intended.
Good point - have turned-off logging.