tried stopping firewalld and then running chronyc sources but it just exits with 0 like always. dang.
--Matthew Wilkinson
From: Burton, John [mailto:jburton@xxxxxxxx]
Sent: Thursday, April 19, 2018 14:17
To: chrony-users@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [chrony-users] chronyc always exits 0 without any output
[This is an external email. Be cautious with links, attachments and responses.]
I had an issue something like that with a different distribution of Linux, but I recall it taking longer to return - like it was timing out on something. Try temporarily disabling the firewall on the computer and see if that changes the
behavior. If that works, then maybe you need to open the port in the firewall?
On Thu, Apr 19, 2018 at 2:57 PM, Wilkinson, Matthew <MatthewWilkinson@xxxxxxxxxxxxxxxxx> wrote:
This bit is interesting:
from strace:
unlink("/var/run/chrony/chronyc.11490.sock") = -1 ENOENT (No such file or directory)
bind(3, {sa_family=AF_LOCAL, sun_path="/var/run/chrony/chronyc.11490.sock"}, 110) = 0
chmod("/var/run/chrony/chronyc.11490.sock", 0666) = 0
connect(3, {sa_family=AF_LOCAL, sun_path="/var/run/chrony/chronyd.sock"}, 110) = 0
fstat(0, {st_mode=S_IFCHR|0666, st_rdev=makedev(1, 3), ...}) = 0
ioctl(0, TCGETS, 0x7fffeb781dc0) = -1 ENOTTY (Inappropriate ioctl for device)
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f7f8cca7000
read(0, "", 4096) = 0
getsockname(3, {sa_family=AF_LOCAL, sun_path="/var/run/chrony/chronyc.11490.sock"}, [37]) = 0
--Matthew Wilkinson
-----Original Message-----
From: Bill Unruh [mailto:unruh@xxxxxxxxxxxxxx]
Sent: Thursday, April 19, 2018 13:34
To: chrony-users@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [chrony-users] chronyc always exits 0 without any output
[This is an external email. Be cautious with links, attachments and responses.]
**********************************************************************
On Thu, 19 Apr 2018, Wilkinson, Matthew wrote:
>
> I recently installed an Oracle Linux 7.5 servers with Chrony 3.2. The
> chronyd will start up, read the config, and synchronize just fine (according to the syslogs).
Is chronyd actually running?
ps auxww|grep chronyd |grep -v grep
>
>
>
> However, when I run chronyc, no matter what options I give it (even
> -d) and even if I give it no options, it just exits with return 0 and no output.
That is very strange. Even if chronyd is not running it should start up.
>
>
> Anyone run into this before or know of a way I can find out why it’s
> doing this? I’ve ran an strace on it, and it just quickly runs through some calls and exits 0.
"some calls" is a bit vague.
Does
chronyc -d
give you any hints?
>
>
>
> Thanks,
>
>
>
> Matthew Wilkinson
>
>
>
>
>
--
To unsubscribe email
chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email
chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email
listmaster@xxxxxxxxxxxxxxxxxxxx.
--
John Burton, Ph.D.
MTEQ, Inc.
10440 Furnace Rd., Suite 204 Office: 540-658-2720 x1407
Lorton, VA 22079-2630 Mobile: 757-508-6208
jburton@xxxxxxxx Fax: 540-288-2515
Please note that the contents of this email including all attachments may be privileged or confidential in nature and are intended solely for the named recipients. If you have received this message in error, please contact
the sender immediately and be aware that the use, copying, or dissemination of this information is prohibited.
|