Hi Phil,
No it shouldn’t, but keep in mind that the zone it is configured for should be ‘in the lead’.
So it does make a difference in which order you group them.
Regards,
I get the feeling that there’s been a regression with recent versions of Ropieee. At one time, grouped zones were no problem, the display and controls worked perfectly. However, ever since the beginning of October, I’ve had problems with display issues when the display zone is in a group…
It doesn’t matter which zone is in the lead. It doesn’t work either way…
Phil
ok. can you send me feedback?
just to be clear: with a single zone it works, but as soon as you group it it does not respond to commands.
and you’ve tried typing the command on the command line?
Thanks,
Yes. Here is the feedback.
014f7d33c7456e98
Also look at the feedback from last night…
Phil
Thanks.
Weird though. The command is being sent to Roon, but Roon Core complains it does not know the zone…
Hi @Phil_Kemp,
There’s something strange going on: NTP is not working. This makes the Pi not running with the correct date/time. Now, I’m not sure if this messes up the communication with Core, but this is definitely not ok.
Did something change in your infrastructure? Both logs show NTP not working.
Would you be willing to login and check a few things?
Othing changed on the infrastructure.sure. What do u want me to check?
Phil
Can you run the following:
systemctl stop ntpd
/usr/bin/ntpd -q -n -4 -g -u ntp:ntp
And paste me the results?
Here ya go…
Last login: Thu Jul 5 13:28:55 2018 from 192.168.2.132
[root@ropieee ~]# systemctl stop ntpd
[root@ropieee ~]# /usr/bin/ntpd -q -n -4 -g -u ntp:ntp
6 Jul 16:08:00 ntpd[24264]: ntpd 4.2.8p11@1.3728-o Sun May 20 16:15:32 UTC 2018 (1): Starting
6 Jul 16:08:00 ntpd[24264]: Command line: /usr/bin/ntpd -q -n -4 -g -u ntp:ntp
6 Jul 16:08:00 ntpd[24264]: proto: precision = 0.677 usec (-20)
6 Jul 16:08:00 ntpd[24264]: Listen and drop on 0 v4wildcard 0.0.0.0:123
6 Jul 16:08:00 ntpd[24264]: Listen normally on 1 lo 127.0.0.1:123
6 Jul 16:08:00 ntpd[24264]: Listen normally on 2 eth0 192.168.2.63:123
6 Jul 16:08:00 ntpd[24264]: Listening on routing socket on fd #19 for interface updates
^Z
[1]+ Stopped /usr/bin/ntpd -q -n -4 -g -u ntp:ntp
[root@ropieee ~]# bg
[1]+ /usr/bin/ntpd -q -n -4 -g -u ntp:ntp &
[root@ropieee ~]# date
Fri Jul 6 16:08:39 PDT 2018
[root@ropieee ~]#
oh you put it to the background. that was not my intention. I wanted to have a look how long it dit take before it would get a proper fix. Which it obviously didn’t (looking at the date). Can you try again and just leave it running in the foreground please?
One at least of my displays seems to have returned to normal. I did have a full power outage yesterday that even drained the UPS’s so will monitor the setup…not yet resumes with grouped zones tho.
[root@ropieee ~]# /usr/bin/ntpd -q -n -4 -g -u ntp:ntp
7 Jul 05:09:44 ntpd[11935]: ntpd 4.2.8p11@1.3728-o Sun May 20 16:15:32 UTC 2018 (1): Starting
7 Jul 05:09:44 ntpd[11935]: Command line: /usr/bin/ntpd -q -n -4 -g -u ntp:ntp
7 Jul 05:09:44 ntpd[11935]: proto: precision = 0.677 usec (-20)
7 Jul 05:09:44 ntpd[11935]: Listen and drop on 0 v4wildcard 0.0.0.0:123
7 Jul 05:09:44 ntpd[11935]: Listen normally on 1 lo 127.0.0.1:123
7 Jul 05:09:44 ntpd[11935]: Listen normally on 2 eth0 192.168.2.63:123
7 Jul 05:09:44 ntpd[11935]: Listening on routing socket on fd #19 for interface updates
7 Jul 05:33:06 ntpd[11935]: Deleting interface #2 eth0, 192.168.2.63#123, interface stats: received=0, sent=60, dropped=0, active_time=1402 secs
7 Jul 05:33:06 ntpd[11935]: 192.73.242.152 local addr 192.168.2.63 ->
7 Jul 05:33:06 ntpd[11935]: 107.181.191.189 local addr 192.168.2.63 ->
7 Jul 05:33:06 ntpd[11935]: 192.73.244.251 local addr 192.168.2.63 ->
7 Jul 05:33:06 ntpd[11935]: 173.230.152.251 local addr 192.168.2.63 ->
7 Jul 05:33:09 ntpd[11935]: Listen normally on 3 eth0 192.168.2.63:123
7 Jul 05:33:09 ntpd[11935]: new interface(s) found: waking up resolver
19 Nov 18:04:22 ntpd[11935]: ntpd: time set +11697854.638064 s
ntpd: time set +11697854.638064s
[root@ropieee ~]# date
Mon Nov 19 20:29:19 PST 2018
[root@ropieee ~]#
Wow. that’s really strange. Look at those times. It’s taking almost 25 minutes!
I know… i wonder why?
PK
Very strange. Can you show me:
cat /etc/ntp.conf
And do the following:
pacman -Syu chrony
chronyd -q -t 30 'pool pool.ntp.org iburst'step one
[root@ropieee ~]# cat /etc/ntp.conf
Please consider joining the pool:
http://www.pool.ntp.org/join.html
For additional information see:
- https://wiki.archlinux.org/index.php/Network_Time_Protocol_daemon
- http://support.ntp.org/bin/view/Support/GettingStarted
- the ntp.conf man page
Associate to Arch’s NTP pool
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org
server 3.pool.ntp.org
By default, the server allows:
- all queries from the local host
- only time queries from remote hosts, protected by rate limiting and kod
restrict default kod limited nomodify nopeer noquery notrap
restrict 127.0.0.1
restrict ::1
RoPieee: location of drift file is on ramdisk
driftfile /var/tmp/ntp/ntp.drift
[root@ropieee ~]#
step 2
[root@ropieee ~]# pacman -Syu chrony
:: Synchronizing package databases…
ropieee-stable 4.5 KiB 0.00B/s 00:00 [###################################] 100%
core is up to date
extra is up to date
community is up to date
alarm is up to date
:: Starting full system upgrade…
resolving dependencies…
looking for conflicting packages…
Packages (6) nspr-4.19-1 nss-3.38-1 ropieee-20181118-2 ropieee-version-226-1 ropieee-web-20181118-3
chrony-3.3-1
Total Download Size: 4.86 MiB
Total Installed Size: 31.50 MiB
Net Upgrade Size: 8.44 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages…
ropieee-version-226-1-any 4.3 KiB 0.00B/s 00:00 [###################################] 100%
ropieee-20181118-2-any 40.5 KiB 238K/s 00:00 [###################################] 100%
ropieee-web-20181118-3-any 3.2 MiB 2.92M/s 00:01 [###################################] 100%
nspr-4.19-1-armv7h 168.7 KiB 337K/s 00:01 [###################################] 100%
nss-3.38-1-armv7h 1263.9 KiB 2.81M/s 00:00 [###################################] 100%
chrony-3.3-1-armv7h 231.3 KiB 7.53M/s 00:00 [###################################] 100%
(6/6) checking keys in keyring [###################################] 100%
(6/6) checking package integrity [###################################] 100%
(6/6) loading package files [###################################] 100%
(6/6) checking for file conflicts [###################################] 100%
:: Processing package changes…
(1/6) installing nspr [###################################] 100%
(2/6) installing nss [###################################] 100%
(3/6) installing chrony [###################################] 100%
(4/6) upgrading ropieee-version [###################################] 100%
Warning: The unit file, source configuration file or drop-ins of avahi-daemon.service changed on disk. Run ‘systemctl daemon-reload’ to reload units.
__ pre_upgrade() __
Failed to disable unit: Unit file ropieee1-led.service does not exist.
(5/6) upgrading ropieee [###################################] 100%
__ _post_ugprade() __
__ _copy_config_files() __
configure [05_timezone]
*** setting up timezone: US/Pacific
configure [06_hostname]
configure [15_config_txt]
configure [17_repositories]
*** setting up repositories for channel: stable
*** setting up ArchLinux repository with base: 201808_00
configure [18_audio]
*** setting up audio for: ropieee-no-hat
*** enabling USB audio
configure [20_touchscreen]
configure [25_update]
*** setting update scenario to on_boot
configure [30_network_wired]
*** setting up wired network
configure [31_network_wireless]
configure [75_remote_control]
*** enabling remote control Flirc
configure [99_error_test]
configure: 99_error_test FAILED:
— BEGIN
/opt/RoPieee/config.d/99_error_test: line 8: [: missing `]’
— END
(6/6) upgrading ropieee-web [###################################] 100%
:: Running post-transaction hooks…
(1/4) Reloading system manager configuration…
(2/4) Creating system user accounts…
(3/4) Creating temporary files…
(4/4) Arming ConditionNeedsUpdate…
[root@ropieee ~]#
[root@ropieee ~]#
step 3
[root@ropieee ~]# chronyd -q -t 30 ‘pool pool.ntp.org iburst’
2018-11-20T18:52:11Z chronyd version 3.3 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 -DEBUG)
2018-11-20T18:52:16Z System clock wrong by -0.199078 seconds (step)
2018-11-20T18:52:16Z chronyd exiting
[root@ropieee ~]#
hope that helps
Phil
Thanks.
That last command returned very quickly.
Could you reboot, wait 5 minutes, and run that last command again?
Thanks
[root@ropieee ~]# chronyd -q -t 30 ‘pool pool.ntp.org iburst’
2018-07-05T20:03:19Z chronyd version 3.3 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 -DEBUG)
2018-07-05T20:03:24Z System clock wrong by 11933246.019264 seconds (step)
2018-11-20T22:50:50Z chronyd exiting
[root@ropieee ~]# date
Tue Nov 20 14:51:00 PST 2018
[root@ropieee ~]#
there ya go…
Phil