Forum Discussion
Can not install any application
We have AD but I haven't configured the ReadyNAS yet, is still using local authentications (I've a post about it here). It doesn't matter if I use our domain controller (192.168.1.220) as the NTP server or any other from ntp.org, neither will stay.
It's obviously something regarding the Timeserver = [ ] portion of the config. Perhaps editing it manually? I'm not really sure.
All,
Well, I solved it on my end. I don't think it will apply to EKroboter, though. In my case, it was a combination of my incompetence and the bad NETGEAR ReadyNAS UI.
Somehow I missed it before, but I finally saw in systemd-journal.log an entry for ntpdate, reporting that no suitable server was found, timestamped right at the moment I tried to save the setting in the UI. And a NETGEAR support rep told me the UI will just quietly not save the address of any server it can't sync with when you add it in the UI. So I looked again at my NTP server. As I mentioned, my ReadyNAS syncs to a local NTP server I set up for it, since the ReadyNAS is isolated and has no route to the Internet. Now I noticed my NTP server was reporting stratum 16, because... well, because I just set it up wrong. Derp. Once I fixed that (it's now stratum 5), I entered the address back into the ReadyNAS interface, and I saw the clock step to the correct time, and the settings have finally stuck.
EKroboter, you've said repeatedly that your ReadyNAS does its initial sync, so it doesn't seem like the fault in my network would apply to yours. But, you never know. Maybe this will get you to look more closely and get to the cause in your case.
The reason I said part of the problem was the NETGEAR UI is because it would be nice if there was a pop-up that informed me that it couldn't sync with the specified server, instead just annoyingly making me wonder if there's a bug in the UI because of its obtuse behavior.
Jeffrey Fox
Jeffrey, I really appreciate your thoroughness on this. Unfortunatelly as you very well point out, this does not apply to my case. I've tried both internal (DC) and external (npt.org, netgear) NTP servers and none of them stick. The clock syncs, but the setting is not persistent across reboots and the setting is somehow lost everytime I click the gear icon and the modal window appears. This is one of the reasons Im hoilding back on integrating our ReadyNAS to our Active Directory domain, since time sync errors can bring up issues with authentication.
I do believe there is a way to edit the settings manually. Hopefully someone from Netgear sees this and is kind enough to point out where the setting is actually stored.
I'll keep investigating.
Did you try what I suggested?
I have. Clear all caches, history and cookies. Re-opwn the browser and go to the admin page and enter NTP settings. Re-open again and delete all history and caches once more. Open up Frontview and the same thing happens: In a split second the box is uncheked and the ntp servers are gone from the list.
Still no resolution to this issue.
Hi EKroboter,
Might be best if you can send your logs for further checking.
How do I add my ReadyNAS OS 6 storage system to my ReadyCLOUD Account?
Regards,
Logs sent.
Hi EKroboter,
Thanks. Let me inquire about your case.
Regards,
EKroboter, it looks like the last NTP interaction was too long ago, and is no longer in your logs. Can you do a fresh reboot, then try enabling NTP again from the GUI, and send in your logs immediately after that? Alternatively, you can just enable Secure Diagnostic Mode, and PM me the 5-digit code so we can investigate directly.
I'll try to reboot tonight after the backup jobs run, enable NTP and download the logs. Thanks for your help.
Great, now can you do one more reboot, then wait 20 minutes and send in one last set of logs?
There are definitely some issues with NTP and clock settings in general in 6.6.x. It should all be fixed in 6.7.0, which is currently available as a public beta. However, even on 6.6.x, it should all work normally after a reboot once you have it configured.
Oh, I'll try again tonight. Can't right now since we have three servers using iSCSI targets and all are being used. Were you able to see anything wrong in the logs I sent?
Based on the logs you sent, the system appears to be configured properly, but in a state where periodic NTP updates won't kick in until after a reboot (or a restart of the connman service).
Hmm, I see. I´ll try to do multiple reboots whenever I get a chance. Hopefully this will be fiex in the next update.
Yes, it should all be fixed in 6.7.0, which is currently available as a public beta.
Yes! 6.7.1 fixed it for me, and still works after 6.7.4. Rebooted a couple of times and the NTP settings are saved.
Thank you.
