On Sun, Jul 16, 2017 at 01:04:33PM +0200, Vincent Blut wrote:
On Sat, Jul 15, 2017 at 05:02:57PM -0700, John Eikenberry wrote:Package: chrony Version: 3.0-4 Severity: normalDear Maintainer,Hello John,After upgrading to stretch I noticed my network was not registering correctly.By this I mean that even though the network (eth0) came up and worked, it didn't have an entry in /run/network/ifstate (the ifstate file was empty). This is using ifupdown + ifplugd in a setup that worked fine on jessie and works fine now after removing chrony.I’m sad to hear that upgrading to Stretch caused you some troubles!It took me a while to nail down the problem, but I finally noticed this kept showing up in my log. run-parts: /etc/network/if-up.d/chrony exited with return code 1 When I put an 'exit 0' at the top of that script my networking came up fine and was added to /run/network/ifstate. So by exiting with an error that script was preventing ifup from completing the ifstate registration.I will try to reproduce this issue by setting up a similar network environment.
Before digging through that issue, that would be awesome if you could reinstall chrony and edit the line where “chronyc” is called by:
chronyc online > /dev/null 2>&1 (i.e. removing “-m” and “'burst 4/10'”) Could you please report back if you are willing to test that of course? Cheers, Vincent
signature.asc
Description: PGP signature

