Re: [chrony-users] 506 Cannot talk to daemon

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-users Archives ]

To: chrony-users@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [chrony-users] 506 Cannot talk to daemon
From: Benjamin Schnieders <benjamin.schnieders@xxxxxxxxx>
Date: Thu, 27 Apr 2017 22:18:48 +0100
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=IgG1Lrt0rB3wBBYkuPIPdob2j2kEBO9On/QYpmVOsTo=; b=pGmlQd2BgmwgqZbpayWoM4/RwBauiRFkIK3BzFiRYZ+XhjvdJNtiHNXHu5ZL3JSYIq QFU0p1R/AsfDw+CesrymXpAw14iJov04ljmYmTUMachSJIf0gHJvRyG3ZAh/aqKMsRuD 58U1ybuHQ7ObYvDoK7NK3uHcDvWxTUcX3YDItcd+qWQyPXXDuu6NbeuVm8reBE5KhkwW MQ2rtFe8b1C0YwXJQHpCGwS4ZPFTOlDNt0wUXmUzLoxjvWan372+1kOpeoH9I2gHSkLg jnPu60R1so8DfIEee0LeFnPaglzjC2c+Hg56Nm3pPXme7gbi0GeRep/gf5rJEKaMduYL mQUQ==

But you could have installed a new chronyc and chronyd, but not then restarted
chronyd, so it is still an old version of chronyd running.

The chrony install was fresh, also, removing the packet definitely also kills the process.

Funny thing I just saw on my home machine: here, chronyd is running as "_chrony" user, and as far as I remember, on the work computer it's run as root. Could that be a potential error?

Follow-Ups:
- Re: [chrony-users] 506 Cannot talk to daemon
  - From: Bill Unruh

References:
- [chrony-users] 506 Cannot talk to daemon
  - From: Benjamin Schnieders
- Re: [chrony-users] 506 Cannot talk to daemon
  - From: Miroslav Lichvar
- Re: [chrony-users] 506 Cannot talk to daemon
  - From: Benjamin Schnieders
- Re: [chrony-users] 506 Cannot talk to daemon
  - From: Bill Unruh

Messages sorted by: [ date | thread ]
Prev by Date: Re: [chrony-users] 506 Cannot talk to daemon
Next by Date: Re: [chrony-users] 506 Cannot talk to daemon
Previous by thread: Re: [chrony-users] 506 Cannot talk to daemon
Next by thread: Re: [chrony-users] 506 Cannot talk to daemon

Mail converted by MHonArc 2.6.19+

http://listengine.tuxfamily.org/