Freezing 66 command

Lijsterbes

I've run into something that appears to be a bug.

In switching from openntpd to chronyd, I've run into problems.
First off, installing chronyd was no problem, neither was stopping, disabling and removing openntpd.
Enabling chronyd was no problem either.
Then the command sudo 66 start chronyd gives trouble. And the strange thing is, it doesn't always give trouble in the same way. Most of the time I just don't get any feedback and I don't get my prompt back until I ^C, but rarely the command will perform its function, but after that either only the chronyd logger or both the logger and the daemon will show status as down.

Some terminal output as illustration:
`lijster@lijsterbes [130] [SSH] ~ % sudo 66 status
[sudo] password for lijster:
In tree: global
\
├─dhcpcd-log (pid=978, state=Enabled, type=classic, tree=global)
├─rclite (pid=up, state=Enabled, type=oneshot, tree=global)
├─wpa_supplicant-log (pid=0, state=Disabled, type=classic, tree=global)
├─sshd-log (pid=980, state=Enabled, type=classic, tree=global)
├─nohang-log (pid=981, state=Enabled, type=classic, tree=global)
├─chronyd-log (pid=0, state=Enabled, type=classic, tree=global)
├─dhcpcd (pid=995, state=Enabled, type=classic, tree=global)
├─wpa_supplicant (pid=0, state=Disabled, type=classic, tree=global)
├─sshd (pid=998, state=Enabled, type=classic, tree=global)
├─nohang (pid=6560, state=Enabled, type=classic, tree=global)
└─chronyd (pid=0, state=Enabled, type=classic, tree=global)

In tree: boot
\
├─boot@system:system-hostname (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:mount-run (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:mount-tmp (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:mount-proc (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:system-sysctl (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:udevd-log (pid=449, state=Enabled, type=classic, tree=boot)
├─boot@system:tty-earlier@tty12 (pid=373, state=Enabled, type=classic, tree=boot)
├─boot@system (pid=up, state=Enabled, type=module, tree=boot)
├─boot@system:populate-run (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:populate-tmp (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:mount-sys (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:populate-sys (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:mount-dev (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:mount-pts (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:mount-shm (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:populate-dev (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:mount-cgroups (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:mount-branch (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:system-hwclock (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:modules-kernel (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:system-random (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:modules-system (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:udevd (pid=634, state=Enabled, type=classic, tree=boot)
├─boot@system:udevadm (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:system-fontnkey (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:system-fsck (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:mount-fstab (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:system-branch (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:mount-rw (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:local-loop (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:local-sethostname (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:local-time (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:local-authfiles (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:local-tmpfiles (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:local-dmesg (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:mount-swap (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:mount-netfs (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:local-branch (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:runtime-branch (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:canopy (pid=up, state=Enabled, type=oneshot, tree=boot)
├─boot@system:tty-rc@tty1 (pid=1033, state=Enabled, type=classic, tree=boot)
└─boot@system:tty-rc@tty2 (pid=1032, state=Enabled, type=classic, tree=boot)
lijster@lijsterbes [SSH] ~ % sudo 66 status chronyd
Name : chronyd
Version : 0.8.0
In tree : global
Status : enabled, down (exitcode 0) 42910 seconds, ready 42910 seconds
Type : classic
Description : ntp client/server
Part of : None
Notify : 0
Max death : 5
Earlier : 0
Source : /usr/share/66/service/chronyd
Live : /run/66/scandir/0/chronyd
Dependencies : chronyd-log
Required by : None
Optional dependencies : None
Start script :
#!/usr/bin/execlineb -P
/usr/bin/execl-cmdline -s { /usr/bin/chronyd ${Args} }
Stop script :
None
Environment source : /etc/66/conf/chronyd/0.8.0
Environment file : environment variables from: /etc/66/conf/chronyd/0.8.0/.chronyd
Args=!-d -u chrony

Environment ImportFile : None
StdIn : s6log:/run/66/scandir/0/fdholder
StdOut : s6log:/var/log/66/chronyd
StdErr : inherit:/var/log/66/chronyd
Logger name : chronyd-log
Logger file : unable to find the log file

lijster@lijsterbes [SSH] ~ % sudo 66 status chronyd-log
Name : chronyd-log
Version : 0.8.0
In tree : global
Status : enabled, down (exitcode 111) 0 seconds, want up, ready 0 seconds
Type : classic
Description : chronyd logger
Part of : None
Notify : 3
Max death : 5
Earlier : 0
Source : /usr/share/66/service/chronyd
Live : /run/66/scandir/0/chronyd-log
Dependencies : None
Required by : chronyd
Optional dependencies : None
Start script :
#!/usr/bin/execlineb -P
s6-log -d3 n3 s1000000 /var/log/66/chronyd
Stop script :
None
Environment source : None
Environment file : None
Environment ImportFile : None
StdIn : s6log:/run/66/scandir/0/fdholder
StdOut : s6log:/var/log/66/chronyd
StdErr : inherit:/var/log/66/chronyd
Logger name : None
Logger file : None

lijster@lijsterbes [SSH] ~ % sudo 66 start chronyd
^Csignal: warning: received SIGINT, aborting transaction
signal: warning: unable to start service: chronyd-log -- exited with signal: 2
signal: fatal: unable to send notif to: chronyd: Broken pipe

lijster@lijsterbes [130] [SSH] ~ % sudo chronyd -d -u chrony
2026-08-16T10:00:59Z chronyd version 4.8 starting (+CMDMON +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +NTS +SECHASH +IPV6 -DEBUG)
2026-08-16T10:00:59Z Using leap second list /usr/share/zoneinfo/leap-seconds.list
2026-08-16T10:00:59Z Frequency 9.291 +/- 6.035 ppm read from /var/lib/chrony/drift
2026-08-16T10:01:04Z Selected source 185.71.60.123 (2.arch.pool.ntp.org)
2026-08-16T10:01:04Z System clock TAI offset set to 37 seconds
2026-08-16T10:01:06Z Selected source 162.159.200.123 (time.cloudflare.com)
^C2026-08-16T10:02:10Z chronyd exiting
lijster@lijsterbes [SSH] ~ % `

eric

The logger cannot start, as chronyd depends on its logger it don't start too. This is expected.

Maybe you have some wrong permissions at /var/log/66. Default on Obarun is s6log:log. Check each sub directory inside it. Or:

# chown s6log:log /var/log/66

You can also try to remove the service, this will cleanup any files belongs to the service, 66 remove chronyd. Then try to start it again.

Lijsterbes

Changing permissions fixed it. Thank you!

It stumped me that there was no error message pointing me into the direction. And maybe the 66 start command should time out after failing, because I had to end it with a ^C after five minutes every time.