I have some cams that the time drifts on and would like to run a local NTP server so this sounded great to me.
I went to install and hit start, but…it seems to fail every time.
Running HassIO on generic linux install.
Every time I hit the start button it acts like it is doing something and then stops, but the addon isn’t started. I go to logs and hit refresh and there is nothing there at all.
I installed at version 1.0.0 then upgraded to 1.0.1 and now 1.0.2, but it does the same each time.
I hope I’m just missing something in the directions, but all I see is Install, Start, Check logs and there is nothing there.
Anyone have any ideas?
Thanks
Up to Hassio 0.101 and tried again with chrony 1.0.4 and no changes.
Still won’t start and no logs.
Anyone else use this?
I do, as well I put it together 
Would be good to see the logs and supervisor log, you may also want to jump onto the Community Addons Discord so we can help you out more.
Thanks for dropping in!
I have tried to look at the built in logs, but there is never anything there after hitting refresh.
I have also tried to add "log_level":debug, trace, or anything
The config box just stays red and won’t let me save so either I’m doing it wrong (most probably since I’m not a programmer) or something is not working right.
I know your github says don’t copy your config, but I can’t get anything else to let me hit the save button or there is no difference if I do.
There are no log entries that I can find in homeassistant pertaining to chrony.
Thoughts?
Thanks again for replying.
You should be able to leave the config as default, I would be interested to see what the Supervisor Log says, under Hassio/System/System Log
I never looked at logs there before…I always used the developer tools.
So at least I learned something today!
So I had it uninstalled because I couldn’t get it to work and just installed it again and the logs show:
19-11-10 15:52:53 INFO (MainThread) [hassio.addons] Create Home Assistant add-on data folder /data/addons/data/a0d7b954_chrony
19-11-10 15:52:53 INFO (SyncWorker_7) [hassio.docker.interface] Pull image hassioaddons/chrony-amd64 tag 1.0.4.
19-11-10 15:52:55 INFO (MainThread) [hassio.addons] Add-on 'a0d7b954_chrony' successfully installed
19-11-10 15:52:59 ERROR (SyncWorker_2) [hassio.docker] Can't start addon_a0d7b954_chrony: 500 Server Error: Internal Server Error ("driver failed programming external connectivity on endpoint addon_a0d7b954_chrony (7e822d7e2591368c536fc0247ce45283992eec755ceab6342e17979a5400ed87): Error starting userland proxy: listen udp 0.0.0.0:123: bind: address already in use")
I run hassio on a generic linux install so since I couldn’t get chrony to work I just installed a NTP server in linux mint which is what I’m running on the host machine. I’m pretty sure this is why the already in use is there, but I installed it after my second post in this thread so it wasn’t keeping it from working before.
I’m trying to think if I stop the NTP daemon will it make a difference because of the rule in iptables or would I need to clear the rule also? I’m not a linux expert so I’m not sure.
Any thoughts?
So the addon by default will listen on the host network on 123 for NTP, which as it is in use it can’t start. If you remove the local NTP server it will be able to start, or you can start it on a different port (but obviously that has an impact to your clients). It’s configured under the Network section.
So I changed the port to 1234 and it started right up and showed logs after hitting refresh at the bottom of the page.
I wonder why it wouldn’t work before I installed that NTP server a week ago though?? Strange.
The non standard port isn’t an issue since I have to manually configure my clients anyway.
I’m glad to have this working as I plan to upgrade the host machine soon so it will be nice to have it all inside hassio.
Thanks for helping!