v1.2.1-rc.2 not reopening St after upgrade

Support
1

All my remote Syncthing instances have not auto restarted after the rc2 upgrade.

2

What do you mean? Can you describe the problem? What happened what you expect to happen?

3

So in the past, when any type of update has been applied (RC or full version), Syncthing will restart. However in all my instances Syncthing was not running / closed completely so I had to go to each device and open Syncthing.

4

Just found this in synctrazors logs (may or may not be relevant)…

[RTF25] 19:57:31 INFO: Automatic upgrade (current “v1.2.1-rc.1” < latest “v1.2.1-rc.2”) [RTF25] 19:57:33 INFO: Connection to xxxxxxxxxxxx closed: Syncthing is being stopped [RTF25] 19:57:34 WARNING: Automatically upgraded to version “v1.2.1-rc.2”. Restarting in 1 minute. [RTF25] 19:57:50 INFO: Connection to xxxxxxxxxxxx closed: Syncthing is being stopped [RTF25] 19:58:11 INFO: Connection to xxxxxxxxxxxx closed: Syncthing is being stopped [RTF25] 19:58:34 INFO: QUIC listener ([::]:22000) shutting down [RTF25] 19:58:34 INFO: Connection to xxxxxxxxxxxx closed: Syncthing is being stopped [RTF25] 19:58:34 INFO: Connection to xxxxxxxxxxxx closed: Syncthing is being stopped [RTF25] 19:58:34 INFO: Connection to xxxxxxxxxxxx closed: Syncthing is being stopped [RTF25] 19:58:34 INFO: Connection to xxxxxxxxxxxx closed: Syncthing is being stopped [RTF25] 19:58:34 INFO: Connection to xxxxxxxxxxxx closed: Syncthing is being stopped [RTF25] 19:58:35 INFO: TCP listener ([::]:22000) shutting down [RTF25] 19:58:44 INFO: connections.Service: Service &util.service{serve:(func(chan struct {}) error)(0x8c82a0), stop:(chan struct {})(0xc0002d3080), stopped:(chan struct {})(0xc0002d30e0), err:error(nil), mut:(*sync.Mutex)(0xc000249ff8)} failed to terminate in a timely manner 2019/07/17 19:58:44 Supervisor discover.cachingMux: discover.cachingMux: Service IPv6 local failed to terminate in a timely manner 2019/07/17 19:58:44 Supervisor local: local: Service multicastBeacon failed to terminate in a timely manner [RTF25] 19:58:44 INFO: Exiting

5

I am not sure its relevant, but you should open a github issue never the less.

6

Is a lib/syncthing issue, PR ready for review.

7

Does this cover it not starting back up?

8

Does this cover it not starting back up?

9

Yes, it’s entirely about that.

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.